Bug 99411

Summary: Tags UTF-8 accentuated character problem
Product: [Applications] amarok Reporter: Yann <yannlieb>
Component: generalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED INTENTIONAL    
Severity: normal    
Priority: NOR    
Version: 1.2   
Target Milestone: ---   
Platform: Mandrake RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Yann 2005-02-14 23:56:57 UTC 
Version:           1.2 (using KDE KDE 3.3.2)
Installed from:    Mandrake RPMs
OS:                Linux

When I created my collection, all songs/albums/artist in the playlist that were containing somme accentuated characters (like Björk, Bénabar, Trêve, ...) were cut two characters before the accentuated character, I mean B for Björk, nothing for bénabar, T for Trêve, ....

Then I tried to re-encode those bad displayed tags, the editor, once opened, show me the correct tag. I had to apply some false modification ans save the tag again to have it appear correctly in the playlist.

My configuration file in Amarok is to encode in UTF-8 (as my locale : LANG=fr_FR.UTF-8).

But now, I restarted Amarok and re-scanned my collection, and the result for the files I modified is a nightmare. I have Björk instead of Björk, Bénabar instead of Bénabar, and so on.

Any idea how to fix this ?
Comment 1 Greg Meyer 2005-03-19 07:00:58 UTC 
Can you please try and reproduce with current cvs or maybe 1.2.2? Thanks.
Comment 2 Alexey A. Kiritchun 2005-03-20 10:33:02 UTC 
Hello.

As far as I know, 1.2.2 fixed the non-latin1 handling, at least my Cyrillic strings show correctly, and can be edited (what a relief ;-) from within Amarok. 

I have a en_US.UTF-8 locale and tag-recoding enabled (to cp1251, so that my iRiver player shows them).
Comment 3 Hubert Hafner 2005-03-25 11:58:07 UTC 
Hi.

Importing songs with german umlauts works fine, but importing songs in a playlist (with german umlauts) leads to broken file links. The reason therefore seams to be the 
.m3u file which is saved in Latin-1. Is there a workaround without reencoding the .m3u files?

e. g. "Nicki - Wenn i träum.mp3"
is shown as "Nicki - Wenn i tr(?)um.mp3"

(using 1.2.2 on KDE 3.3.0, SuSE 9.2, LANG=de_DE.UTF-8)
Comment 4 Hugo Haas 2005-04-08 09:15:32 UTC 
Using Amarok 1.2.3, and despited having played with the encoding setting, my UTF-8 descriptions still seem to be read as UTF-8.

Something worth mentioning though: I use id3v2 only, and the encoding settings in the preferences only has checkboxes for id3v1 and Shoutcast metadata. Maybe it is my issue.
Comment 5 Bas Zoetekouw 2005-04-27 15:04:40 UTC 
Using amarok 1.2.3 and a en_GB.UTF8 locale, I have a similar issue.  Although european accented chars (ö, é, etc) in id3v2 tags work correctly, japanese (kanji) chars, such as 羽, aren't working well.

To reproduce: using amarok, edit the id3 tag and set one of the fields to some kanji character.  Save, and then quit amarok.  When restarting amarok, the kanji char is displayed correctly in the playlist (so the entire playlist handling seems ok). After recreating a playlist from the collection (using the "all collection" smart playlist for example), the kanji chars are broken again in the playlist.  Checking the tags with another program (muine) shows that the actual tag on disk is broken.
Comment 6 Antto Mäkinen 2005-05-04 22:06:35 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 7 shattered 2005-11-22 06:48:18 UTC 
Reporter: you say that "My configuration file in Amarok is to encode in UTF-8" -- are you using the "decode ID3v1 tags as UTF-8" option?
Comment 8 Greg Meyer 2006-03-01 03:17:16 UTC 
This option has been eliminated in 1.4 so I am closing this bug as far as trunk is concerned.