Version: (using KDE KDE 3.4.1) Installed from: SuSE RPMs Compiler: gcc version 3.3.4 (pre 3.3.5 20040809) OS: Linux I am using SuSE 9.2 with all YAST updates and KDE 3.4.1. My system locale LANG=de_DE.UTF-8, in konqueror kyrillic characters are displayed correctly. Since KDE 3.4.0 I observed, that some other applications cannot display kyrillic characters. For example: Junk only is displayed for the song titles when I "cddb" some Russian CD (in grip, kscd, k3b). Additional information: dvd::rip cannot display the German umlaute. Google did not help...
Can you give us an example? What font are you using? What do you see: Москва ?
Am Montag, 4. Juli 2005 13:51 schrieb Thiago Macieira: [bugs.kde.org quoted mail] That is ok, I see Moscow. Here an example: DISCID=73099b09 DTITLE=Íåíñè / Äûì Ñèãàðåò Ñ Ìåíòîëîì DYEAR=1995 DGENRE=misc DID3=13 TTITLE0=Äûì Ñèãàðåò Ñ Ìåíòîëîì TTITLE1=Îòåëü TTITLE2=×èñòûé Ëèñò TTITLE3=Ãîëóáîãëàçàÿ TTITLE4=Ñâåòëàíà TTITLE5=Êàê Ëþáèë ß Òåáÿ (remix) TTITLE6=Íå Îáèæàéñÿ Íà Ìåíÿ TTITLE7=Ìóçûêàëüíàÿ Ñêàçêà Äëÿ Âçðîñëûõ "Ìîéø TTITLE7=" TTITLE8=Ïüÿíûé Äåíü Ðîæäåíèÿ (remix)
I think this is the proper place.
Yeah, I see it here too, the problem is that it is encoded in CP1251 which isn't really supported by freedb.org (only iso-8859-1 and utf8 is). I have some code for kscd and kaudiocreator for changing the encoding manually, which I will put in svn soon. I guess I could add something similar to the audiocd ioslave. In that case it would be something like adding "?encoding=CP1251" to the end of the url, so it would still be a bit messy :-(
Richard, was your code integrated into kscd or kaudiocreator?
Yes, it's integrated in both KsCD and KAudiocreator. It's the "Change Encoding" button in the cd-info dialog. It looks like it was integrated from KDE 3.5.0.
What about audiocd ioslave? See bug 142337.
No, nothing for the audiocd ioslave yet, that's why the bug is still open. And I'm not really sure what to do about it since the ioslave doesn't really have an UI to do anything.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.