> > framebuffer-enabled terminal (like jfbterm used in 1st stage) for > > Chinese install. So the user will get garbled characters in the 2nd > > stage of installation (the part running base-config), so most Chinese > > users choose to install in English instead. > On Fri, Nov 04, 2005 at 07:26:37AM +0100, Christian Perrier wrote: > *That* is not true. 2nd stage runs fine with CJK languages because > base-config is run under jfbterm. If it does not run fine, this is a > bug.
I stand corrected. Actually I must confess that I've never done an installation in Chinese myself - I've did some test to see if the Chinese characters display correctly, but never finished the install. For my own system I always install in English (and use an English locale, for that matter). I just heard a lot of Chinese users complain that there would be garbled characters "after reboot". So I thought it was the 2nd stage of installation. Sorry for the misleading message. > However, the end system will display garbage *later*, if localized in > CJK languages (or Arabic, Hebrew...) because jfbterm cannot be run as > a login program. There's a discussion about this in localechooser bug > log and no real possible solution. I agree that is quite a hard problem to solve. Ming 2005.11.05 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
