On Tue, 2004-01-27 at 19:54, Kenshi Muto wrote: > At 27 Jan 04 21:18:30 GMT, > Joey Hess wrote: > > - better i18n in the second stage > > > > I don't know what the status is. Perhaps Kenshi Muto knows? > > Probably mandatory for next release. > > I believe Chinese, Japanese, Korean and Greek will be displayed correctly. > > My TODO: > - - test, hack, test, hack... :-) I'll do this weekend. > Has anyone cool CD image build script from d-i/base-config CVS? :-) > - - UTF-8: I think to use jfbterm for this encoding rather than simple > console. > - - validlocale seems a little wrong (#225870). I and Ishikawa will try > to fix this. JoeyH, if you can fix easily, please tell us before we > start to do it :-) > - - FB check routine should be more brushed up. Debconf db on 1st stage > has whether user use FB or not, so it looks good to use this variable. > I need to check other arch (mainly PPC) also about FB. > > QUESTION: > - - Will be debconf style around langchooser changed? If so I need to > follow it. base-config simply uses 'debian-installer/locale' for LANG. > > HELP: > - - Russian: console-cyrillic is already installed by base-installer on > 1st stage. But I don't know how to setup this. > - KOI8-U > - - I don't know how to treat following encodings (some of these include > non-supported language by debian-installer). > > - CP1251 > - CP1255 > - EUC-TW (jfbterm?) > - GB18030 (jfbterm?) > - GBK (jfbterm?) > - ISO-8859-6 > - ISO-8859-9 > - ISO-8859-14 > - KOI8-T > - TCVN5712-1 > - TIS-620 Can't all encodings be converted to UTF-8 using iconv(1)? That would certainly simplify things.
Attachment:
signature.asc
Description: This is a digitally signed message part