Hi, From: Petter Reinholdtsen <[EMAIL PROTECTED]> Subject: Re: i18n of tasksel (and cdebconf) Date: Tue, 26 Aug 2003 11:40:24 +0200
> I believe it is OK to limit cdebconf to only handle UTF-8 encoded > templates, but believe it should be able to output using other > charsets as well. We will not need it in d-i, because we decided to > standardize on UTF-8 output, but it might be useful for cdebconf to be > a full debconf replacement. I read debian-installer/doc/i18n.txt and understand why it limits to UTF-8. BTW, I tested (on UTF-8 terminal): LANGUAGE=ja LANG=ja_JP.UTF-8 dpkg-reconfigure -ftext ssh LANGUAGE=ja LANG=ja_JP.UTF-8 dpkg-reconfigure -fncurses ssh LANGUAGE=ja LANG=ja_JP.UTF-8 dpkg-reconfigure -fslang ssh LANGUAGE=ja LANG=ja_JP.UTF-8 dpkg-reconfigure -fnewt ssh but all of them displayed "text" frontend (I guess). I have not tested -fbogl and -fgtk because I am now using PuTTY. Am I forgetting something? > > This problem is not limited to Japanese. Since Korean, Chinese, > > Russian, Greek, and so on are affected by this problem, Japanese- > > specific solution is not very good, I think. > > If you see the language question in the beginning of d-i install, you > should see character for all these langauges. I understand that bogl-bterm and cdebconf is used for the Stage 1. (Are there any other programs than cdebconf which is used for Stage 1 ?) How about the Stage 2 ? Any internationalized terminals? Is the selected language in the Stage 1 also living in the Stage 2 ? Is tasksel used? > BTW: Please check the question text in tools/languagechooser to make > sure the japanese text matches the form of the other questions. I found that Japanese sentense says "Push Enter to configure in Japanese language" which is apparently different from English sentence. Though I cannot read most of languages in the languagelist.l10n file, many languages have "Enter" in the sentence, which implies they are all outdated. --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/
