Bug 83821 - in mp3 files, id3 tags with non-ASCII characters are not displayed or saved to files correctly
Summary: in mp3 files, id3 tags with non-ASCII characters are not displayed or saved t...
Status: RESOLVED DUPLICATE of bug 81400
Alias: None
Product: kfile-plugins
Classification: Applications
Component: mp3 (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Multimedia Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-22 19:25 UTC by Michał Kosmulski
Modified: 2004-06-23 12:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Kosmulski 2004-06-22 19:25:58 UTC
Version:            (using KDE KDE 3.2.3)
Installed from:    Slackware Packages

When an mp3 file has id3 tags containing non-ASCII characters (Polish accented letters in my case), these are not properly displayed in the file properties dialog or file tooltips (two byte garbage sequences are displayed in place of each non-ASCII character). When editing the tags in the properties dialog and pressing OK, some ASCII stuff is saved instead of the characters that were actually entered. My locale uses UTF-8 and XMMS as well as mpg321 and id3v2 and even id3tool display unicode characters correctly. KDE applications don't.

Interestingly, unicode characters in OGG Vorbis files are displayed correctly and can be edited in the properties dialog without any problems.

Please note that this is not a duplicate of bug 81400 - there the reporter claims that UTF-8 encoding is always used and that's what they don't like. In my case, I would like UTF-8 to be handled properly, which it seems to not be.

This bug affects not only kfile-plugin for mp3, but seems to affect all kde applications, including amarok and juk - the behavior (the string appearing in place of the correct one) is exactly the same.
Comment 1 Scott Wheeler 2004-06-23 12:28:09 UTC
Actually this is a duplicate of #81400 -- please read the responses there.

*** This bug has been marked as a duplicate of 81400 ***