Bug 247872

Summary: Amarok skips or refuses to play songs with accented characters
Product: [Applications] amarok Reporter: raffo.he
Component: PlaylistAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nhn, teo
Priority: NOR    
Version: 2.3.0   
Target Milestone: 2.3.2   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Amarok in debug mode trying to play a track with accented characters.

Description raffo.he 2010-08-14 19:08:27 UTC
Created attachment 50557 [details]
Amarok in debug mode trying to play a track with accented characters.

Version:           2.3.0 (using KDE 4.4.4) 
OS:                Linux

When I add to the playlist a song that contains accented characters either in the path or filename it does not play and Amarok skips to the next song.

The songs are correctly listed in the collection with the accents.

Reproducible: Always

Steps to Reproduce:
Add a track with accented characters in the path or filename

Actual Results:  
Track does not play, skips to next song.

Expected Results:  
Play the track I added.
Comment 1 raffo.he 2010-08-14 19:09:34 UTC
I've had this problem since Amarok 2 came out.
Comment 2 Myriam Schweingruber 2010-08-14 19:13:17 UTC
Which phonon backend do you use?
Comment 3 raffo.he 2010-08-14 19:21:03 UTC
This is on an opensuse 11.3 distribution. The phonon is Xine, ver. 0.2.60.
Comment 4 Myriam Schweingruber 2010-08-15 09:55:09 UTC
To workaround this problem, make sure your LOCALE is set to UTF-8 or UTF-16 and that your tags are in UTF as well. Easytag or kid3 allow you to mass-retag your tracks if necessary.

*** This bug has been marked as a duplicate of bug 242168 ***
Comment 5 raffo.he 2010-08-15 21:24:18 UTC
This may be redundant, but I'd place my experience in converting the encoding of the file names in my collection. After converting them, all the files were visible to Amarok. (This may be useful to other people when searching this archive, since I didn't find the solution clearly described.)

Just converting the LOCALE to utf-8 does not fix the problem, it just makes all the ISO-8859 characters look wrong. The rest of the solution is as follows:

First, I switched my locale setting "LANG=en_US.utf-8" in my .profile

Second, I run this command:   convmv -r -f ISO-8859-1 -t UTF-8 *
this will do a dry run conversion of the file names, recursively through directories.

If all looks good then run:  convmv -r -f ISO-8859-1 -t UTF-8 * --notest

The only caveat appears to be that if one of the subdirectories in the tree has also non UTF-8 characters in them, then convmv will not convert it. What I did was to convert the directory name first and then run the recursive convmv command above.