Kaixo! On Sat, Sep 20, 2003 at 02:46:24PM +0800, Victor Roetman wrote:
> When installing in Simplified Chinese, with no other languages, the locale was > zh_CN, and everything seems to work as expected. The problems happen when > using more than one language. ... > My test install was from the 2003 Sept 19 cooker. The installation laguage > was Simplified Chinese. Additional language support was chosen for: > Traditional Chinese, > Korean, > Japanese, > American English. > I did NOT choose "Use Unicode by default" How do you want to be able to support Chinese and some other language without using unicode? The "Use unicode by default" check box is only to force UTF-8 when it is not otherwise used; but when you choose languages that *require* unicode for proper display and cohabitation, then UTF-8 is used regardless of that value of the "Use unicode by default" option. "It's not a bug it's a featuer" :) It is the wanted and expected behaviour, when choosing two (or more) languages using incompatible character sets, the only choices are to use unicode, or to be unable to use those languages together. > Konsole's default font for all these locales (except Japanese) looks terrible, > by the way. It's way too big. It's the same size no matter what size you > choose. To change it you must choose a custom font. It has always been this > way with Chinese locales, by the way. The font used isn't the same as per KDE menus and buttons ? > No .i18n: > Initially, chinput would not input characters into Konsole, kwrite, or kedit, > (Qt apps), but worked with gvim, OpenOffice, gedit. kedit gives the > following error when typing with Chinput: > kdecore (KAccel): WARNING: g_bKillAccelOverride set, but received an event > other than AccelOverride. In ~/.qt/qtrc do you have a section [General] with XIMInputStyle = "Over The Spot" ? (maybe DrakX doesn't create that file when creating a user?) > My uneducated guess is that whatever creates the ~/.qt/ files localedrake does. > is looking at ~/.i18n and not at the environment variables (or > /etc/sysconfig/i18n). if ~/.i18n exists then /etc/sysconfig/i18n is not used. > Openoffice used japanese language localization!! (I what is the output of "locale" command ? OOo follows the value of LC_CTYPE unless a specific OpenOffice language setting is defined > zh_TW.UTF-8: > After using localedrake to change my locale to zh_TW.UTF-8, the Mandrake Linux > initial popup was missing characters. It is probably using a simplified Was fonts-ttf-big5 installed ? > ko_KR.UTF-8: > After using localdrake to change language to Korean (ko_KR.UTF-8), the initial > Mandrake popup screen was still in chinese with missing characters. I am What do you call the "initial popup screen" ? The display manager where you log in? kdm (and mdkkdm) use the language defined in the global config file /usr/share/config/kdm/kdmrc So, you need to change the global language setting (launch localedrake as root), not simply the user setting. > assuming now that it is the same as when I started - simplified Chinese and > doesn't change with the locale. kwrite would not take korean input. kedit > worked, but gave this error when pressing the spacebar using the Ami input > method: That is quite strange; I would have expected all Qt programs to behave the same. (note that a connection with the XIM is done, but it seems the typed flow gets lost) If in qtrc the style is changed to "Over the Spot", then the input is possible, but in blind mode (korean chars aren't seen while typing, only when you press space). Seems a kword specific bug. > Openoffice localized properly to Korean, but gave the following errors when > running oowriter: > /usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or > directory That happens when the locale is not installed. What is the output of "locale" ? (it should be ko_KR or ko_KR.UTF-8 for Korean locale). Is locales-ko installed ? > ja_JP.UTF-8: > still had the same problem. kwrite would not display the proper fonts when > entering japanese with kinput2. It displays boxes for japanese characters. I don't have that problem; what version of kwrite ? > By the way, strange things happen when you choose japanese language, but korea > for a country. I think that kind of problem can be left until later. It sets korean as language... maybe it is because I have kde-i18n-ko and not kde-i18n-ja ? But anyway, it shouldn't. > Running localedrake again, choosing simplified chinese, added the line > ENC=gb > to ~/.i18n > > Upon KDE restart everything worked fine. So I guess this ENC=?? line in > ~/.i18n is pretty important for qt No, it does nothing (it is only used by CJK version of rxvt). the important thing is that localedrak wrote that XIM should be Over the Spot in the ~/.qt/qtrc file (maybe libqt should be patched to make that value the default) > zh_TW: > Using localedrake to change the locale to traditional chinese/taiwan gives > ~/.i18n locale to be zh_TW. I deleted ~/.openoffice to be safe. Upon KDE > restart kwrite still would not display traditional characters. kedit, gedit, > openoffice all worked fine. xcin was the IME. Kwrite seems to use its own display code, different of the rest of KDE, and buged :( > So I deleted ~/.kde, ~/.qt, and ~/.openoffice and restarted KDE. This time > all the KDE menus were missing characters (must be using a simplified font). If you delete ~/.kde/share/config/kdeglobals, you also delete the info on the default font. Apparently Qt/KDE takes the first font with chinese charaters, without doing any distinction between traditional and simpliifed. 50% of chances of being wrong... fontconfig gives information on charset coverage and language coverage for each font; so maybe a future version of Qt could use that info to better choose the fonts (or even better: try to find missing glyphs from other fonts, as gtk does; which would take away the need to provide a default font) > Incidentally, using gbrxvt with zh_CN.UTF-8 does not work well. Indeed, rxvt doesn't support UTF-8 at all. > Chinese (and other language) support has come a long ways, and it is beginning > to look really good. Indeed, the only real CJK-specific problem in all you reported is the bug of kwrite with ami; and the fact that Qt should better default to Over the Spot, to be safer when conection to an XIM without good On the Spot support is done. All the rest is not CJK specific (they are font problems in Qt and kwrite, and lack of proper UTF-8 support on some few old programs) Another, not reported, CJK problem is the fact you cannot switch of input method (other than calling localedrake, login out, and relogging; which is not very user friendly), this is due to an XFree86 limitation. Only "yudit" (a unicode text editor) is able to do it (it allows to connect to various different XIM, and you can switch between them with a menu) > It's very nice to be able to switch between languages > on the same machine. (Perhaps in six months or a year Mandrake can move > completely to Unicode and change IME's on the fly.) The IME switching problem will take more time I'm affraid... (with gtk it would maybe be possible to implement the same behaviour as yudit, as gtk provides a way to develop gtk-specific input methods; for Qt I don't know). > vic -- Ki �a vos v�ye b�n, Pablo Saratxaga http://chanae.walon.org/pablo/ PGP Key available, key ID: 0xD9B85466 [you can write me in Walloon, Spanish, French, English, Italian or Portuguese]
pgp00000.pgp
Description: PGP signature
