Bug#225870: [PATCH] Re: validlocale can not handle language_territory.codeset style locale
Here is a patch to fix this. --- base-config-2.08/validlocale~ 2004-01-28 11:45:26.0 +0900 +++ base-config-2.08/validlocale2004-01-28 11:45:29.0 +0900 @@ -35,11 +35,15 @@ # Hm, if charset is missing, how to we pick the correct one to # use? Fetching the value from /usr/share/i18n/SUPPORTED should # work on Debian. -$charset = get_default_charset($locale$modifier) - unless (defined $charset); +my $codeset = ; +if (defined $charset) { + $codeset = '.' . $charset; +} else { + $charset = get_default_charset($locale$modifier); +} # print L: $locale C: $charset M: $modifier\n; -print $locale$modifier $charset\n; +print $locale$codeset$modifier $charset\n; exit 1; } else { -- ISHIKAWA Mutsumi [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: goals for next release
Hi, In [EMAIL PROTECTED] Kenshi Muto [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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: - - 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 :-) I've just posted a patch to fix this. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=225870 It is needed to support CJK locales, for example Japanese usually use ja_JP.EUC-JP locale but current validlocale can not handle the locale correctly. -- ISHIKAWA Mutsumi [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#225870: validlocale can not handle language_territory.codeset style locale
Package: base-config Version: 2.04 Severity: normal validlocale can not handle language_territory.codeset style locale, if the locale is not available. For example: $ /usr/sbin/validlocale en_US.UTF-8 locale 'en_US.UTF-8' not available en_US UTF-8 validlocale returns `en_US UTF-8' for locale-gen. I think it should be `en_US.UTF-8 UTF-8'. -- ISHIKAWA Mutsumi [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]