Version: 1.2.2 (using KDE 3.3.2-1.1.kde, Fedora Core release 3 (Heidelberg)) Compiler: gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3) OS: Linux (i686) release 2.6.9-1.667 The problem like in http://bugs.kde.org/show_bug.cgi?id=99411 I have Russian UTF8 locale and IDv2 UTF8 tags in my mp3 files. This tags are shown correctly in XMMS, but amarok playlist shows me something like this: Àíäðåé - Ïðîùåíèå. I have the same problem in amarok, noatun and JuK.
Created attachment 10253 [details] Amarok 1.2.2 playlist
I think you should use id3v2.4 for v2 tags and there will not appear any problem with encodings in the future: http://www.id3.org/id3v2.4.0-structure.txt: Frames that allow different types of text encoding contains a text encoding description byte. Possible encodings: $00 ISO-8859-1 [ISO-8859-1]. Terminated with $00. $01 UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM. All strings in the same frame SHALL have the same byteorder. Terminated with $00 00. $02 UTF-16BE [UTF-16] encoded Unicode [UNICODE] without BOM. Terminated with $00 00. $03 UTF-8 [UTF-8] encoded Unicode [UNICODE]. Terminated with $00.
I didn't verify this, but was told that XMMS does not handle the 'encoding description byte' at all and it's a coincidence that it renders tags correctly (UTF8 locale is the key). It'd be useful to see a dump of both v1 and v2 tags from offending files (mp3check.py from Py-Tagger can do that).
Is this still a problem?
Well, closing for lack of feedback. PLease reopen if it's still a problem on amaroK 1.3.9.