Red Hat Bugzilla – Bug 52381
latest kpersonaliser uses wrong charset for Russian language
Last modified: 2007-04-18 12:36:19 EDT
Description of Problem:
kdebase-2.2-charset.patch set iso-8859-5 charset for Russian language:
+ else if(lang == "ru")
It's wrong, must be koi8-r (see anaconda's lang-table for Russian).
There is also no any ISO-8859-5 fonts except for fixed that is not enough
Version-Release number of selected component (if applicable):
Fixed in 2.2-7...
The reason I set it to 8859-5 initially is that that's what KDE's locale files
suggest . I'll simply trust you on this one, I don't speak Russian.
I know that you don't speak Russian. But you can trust also anaconda/lang-table.
Here is the line:
Russian ru cyr-sun16 koi8-r ru_RU.koi8r ru
What anaconda claims is not necessarily right for KDE - if iso-8859-5 and
kio8-r are very different, a translated string written for one will not
necessarily display correctly on the other...
So if kde-i18n stuff is written in iso-8859-5 and not properly UTF8 encoded,
it will display garbage even if koi8-r is the correct charset.
However, I'm quite sure all the kde-i18n stuff is UTF8 by now.
Yes, all russian .po files from kde are utf8-encoded. But 1) iso8859-5 fonts are
still needed, 2) encodings are quite different, and if file was created with
console or gnome text editor, it must be convertEd by iconv first to edit it in
[leon@p504 SRPMS]$ xlsfonts | grep -c iso8859-5
[leon@p504 SRPMS]$ xlsfonts | grep -c koi8-r
Actually iso8859-5 live only on Sun Solaris. Most part of Linux and *BSD russian
community uses koi8-r and small part uses microsoft-cp1251. BTW I have packages
with 75dpi fonts for iso8859-5 and cp1251, and they may be sceduled for next Red
Hat Linux release. Bulgarians and Byelorussians will enjoy cp1251 fonts very much.