刚才又试了一把 修改 tag，也没什么问题啊，至少在 amarok 中看没什么问题
你真是懒，把修改后的文件在 kaffeine 或者 bmp 里播放看看，mp3tag 一定乱码。而且还有很多地方不支持中文，只是你不够细，测试不充分。
不要这样“人身攻击”吧
我的机器上只装了 amarok，你说的那俩都没有：我觉得有一个好用的就够了，不想 emerge 其他的...
我明白了，amarok 应该以设置的 encoding 来保存 tag，而不是 utf-8，有人向他们开发者反映过这个问题了吗？
kaffeine 是全能播放器，而 amarok 仅仅是音频播放器。另外使用 beep 的 xine 插件，也可以播放视频。
Ok, I submitted a patch modified from the original one
http://bugs.kde.org/show_bug.cgi?id=89747#c26
What's more: I chatted with the developers, and the patch has been committed into CVS HEAD. They promised that this will be included in all future releases, say it 1.2.4 or 1.3.0
So from now on, we do not need to patch amarok everytime it releases a new version
thanks to the original patch maker ;)
Forgot to mention:
the new patch is a clean version of the original one which have much more chances to be accepted, but what it does is the same as before ;)
我早就提交过了。你做了什么？
我们的国家标准是 gb18030 而不是 utf-8 你那样改如何保证在 gb18030 local 下使用！！！
你能保证在 gb18030 local 下不经任何设置就能正确显示中文吗？？？
?? If the original patch can do that, why do you think mine can not? Did you look at the patch I submitted? Or did you compare it with the original patch?
As I said, the modified patch basically is the same as the one before.
If you state you have submitted it, could you give me any evidences? like a comment in bugzilla or an email in their mailing list?
What I did is not so important. I admit that I did not investigate much time, rather I choose to base the patch on the existing one.
I asked is there anybody submitted this patch? no one answered, so I tried to push it into upstream: I chatted with the developers via IRC.
你能保证在 gb18030 local 下不经任何设置就能正确显示中文吗？？？
I just discovered that: if you specify a custom decoding charset, then it is not working at all. However, if you leave that unchecked, all is fine with the patch.
So, as long as you have gb18030 set up correctly, you do not need to (in fact, you should not) set anything in the configure dialog in order to display Chinese correctly
你能保证在 gb18030 local 下不经任何设置就能正确显示中文吗？？？
Yes, I can not guarantee that. However, I just tested under GB18030, and it works as expected!
of course, if anyone have any comments on the patch, you are welcome
KDE: I does not feel quite comfortable with your manner of speaking... you are a bit aggresive...
or maybe I am too sensitive... ?
Do you mind hear a suggestion from me? Could you please give more details on a topic, for example: when you say
> 我们的国家标准是 gb18030 而不是 utf-8 你那样改如何保证在 gb18030 local 下使用！！！
Could you please also state what your concern is? Or what you think is wrong?
thanks.
我唯一担心的是是否符合国标，否则补丁只会引来更大的麻烦。最基本的，为了消除大家的疑虑，你应该在 gb18030 的 local 下做一张打补丁后的软件截图。否则别人如何就凭你的几句话就相信你？否则就必须花费很多时间去编译，而我的机器非常慢，ML 开发组成员的机器也没有几个是新的。
请时刻谨记，西方人不会为亚洲语言的支持操心，因为他们的字符集只能用 tiny 来形容，根本感受不到中国人的苦。他们可以使 utf-8，而我们不行，因为现在中国是个 gb2312/ANSI 的环境，将来是 gb18030 的环境。UTF-8 没有考虑我们的少数民族文字编码，这是具有歧视性的！我们要时刻绷紧这根弦！中国是一个拥有 13 亿人口的大国，这样一个世界 1/4 人口的大国，恐怕没有一个中国人希望我们的标准由西方国家操纵和强加！
正是因为你使用了最近国外发行版流行的 UTF-8 编码，所以才使我高度担心。任何测试都应该以 gb18030 为基准，兼顾其他标准。正是因为 utf-8 满足不了中日韩语言文字的需要，所以各国才要基于 iso 标准制定自己的国标。
引用中国汉化同盟的一句纲领：中国人，说中国话，写中国字！