Bug 197031

Summary: Scanner encoding problem with Greek characters
Product: [Applications] amarok Reporter: snvv101
Component: generalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED FIXED    
Severity: normal CC: ashl1future, mitchell, peterzhoulei
Priority: NOR    
Version: 2.1.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description snvv101 2009-06-18 17:13:31 UTC 
Version:           2.1.1 (using 4.2.4 (KDE 4.2.4), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.30-0.slh.3-sidux-amd64

Hello,


Amarok does not display correctly Greek character.
In my system I use UTF-8.
In my.cnf I have not define utf character set (it should use system wide UTF-8) (* see below)

Now the strange thing:
If I use in EasyTag Charset western (ISO-8859-1) and write the tags from file name then they are displayed in Amarok.
If I modify something (i.e the singer name) then it does not show it in Amarok.
If I use UTF it shows ??????
If I change the mysql  character set ti UTF (* see above) then my old UTF tags are displayed as +-y+- etc. Strange characters.


This problem started with the latest stable version. When i used the last SVN there was no problem at all.

Is something that I can do about it???

It is serious because there are more than 50000 tracks.

Thank you
snvv
Comment 1 Alexey Shildyakov 2009-06-22 23:49:24 UTC 
It seems relaed to this: http://bugs.kde.org/show_bug.cgi?id=189527#c12
Comment 2 Alexey Shildyakov 2009-06-23 01:26:27 UTC 

*** This bug has been marked as a duplicate of bug 189527 ***
Comment 3 Myriam Schweingruber 2009-06-23 20:29:56 UTC 
Alexey: No, it is not a duplicate, read the description of the bug correctly.
Comment 4 Myriam Schweingruber 2009-07-11 15:31:36 UTC 
This should be solved by now in 2.2-SVN. Jeff, any news on this?
Comment 5 Jeff Mitchell 2009-07-11 17:47:14 UTC 
This is one of three problems. Either it's related to the character set encoding in the DB, which should be fixed by upgrading to 2.2-SVN and doing a full rescan; or it's because this is one of the users that for some reason has InnoDB tables instead of MyISAM tables; or this is an issue with the charset detector, in which case Peter should have a look at it.
Comment 6 Peter ZHOU 2009-07-12 01:08:14 UTC 
This has been fixed by my commit during the akademy.