> 2. People would say "then don't install in English, install in > Chinese"! But the problem is that d-i doesn't install a
I'd rather say that using an install in English for later use a Chinese system is very likely to require manual intervention such as the one you describe. This is mor eor less expected behaviour. > 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. *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. 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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
