Note, we cannot assume that anything not listed in SUPPORTED works. That's why upstream has a supported list.
----- Forwarded message from Drew Parsons <[EMAIL PROTECTED]> ----- Subject: Bug#154556: locales: en_AU.UTF-8 is not available in standard locale list Reply-To: "Drew Parsons" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Resent-From: "Drew Parsons" <[EMAIL PROTECTED]> Original-Sender: Drew Parsons <[EMAIL PROTECTED]> Resent-To: [email protected] Resent-CC: Ben Collins <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Resent-Date: Sun, 28 Jul 2002 02:03:06 GMT Resent-Message-ID: <[EMAIL PROTECTED]> X-Debian-PR-Message: report 154556 X-Debian-PR-Package: locales X-Debian-PR-Keywords: From: "Drew Parsons" <[EMAIL PROTECTED]> To: "Debian Bug Tracking System" <[EMAIL PROTECTED]> X-OriginalArrivalTime: 28 Jul 2002 02:00:05.0212 (UTC) FILETIME=[7DF499C0:01C235DA] Resent-Sender: Debian BTS <[EMAIL PROTECTED]> Package: locales Version: 2.2.5-12 Severity: normal en_AU is present in the standard locale list (/usr/share/i18n/SUPPORTED) as ISO-8859-1, but en_AU.UTF-8 is not given as an alternative. There is an en_GB.UTF-8 and an en_US.UTF-8, but no en_AU.UTF-8. This makes configuring with debconf a little unsatisfactory, forcing me to edit /etc/locale.gen bu hand. I can't use en_GB.UTF-8 - it'll stuff up LC_MONETARY (pounds not dollars), and I can't use en_US.UTF-8, it'll stuff up LC_TIME (12-25-02 = twelth day of which month?) I think there may be a deeper problem here which needs to be thought about. The UTF-8 character set can effectively apply to *all* locales (i.e. all language_COUNTRY combinations). It seems somewhat frivolous to repeat every single combination that is already present in /usr/share/i18n/SUPPORTED, and merely append a .UTF-8 to it. Perhaps a better approach is to assume that every locale mentioned in /usr/share/i18n/SUPPORTED can be rendered as a .UTF-8 locale. Then /usr/share/i18n/SUPPORTED can be used to define standard default charsets for each locale along with other particular non-UTF-8 variations such as @euro (which is basically what it currently does, except it adds some odd arbitrary .UTF-8 locales). These standard default locales can be selected as at present via debconf, but the main change I envision here is that the current question could be supplemented by an additional similar debconf question, picking out base locales which will be written as .UTF-8 in /etc/locale.gen. That is, you choose en_AU in this second question, and "en_AU.UTF-8 UTF-8" gets written to /etc/locale.gen. What do you think is the best why to make sure all UTF-8 locales are consistently included? Drew -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux strider 2.4.18 #1 Fri Mar 15 02:02:53 EST 2002 i686 Locale: LANG=en_AU, LC_CTYPE=en_AU Versions of packages locales depends on: ii debconf 1.1.18 Debian configuration management sy ii libc6 [glibc-2.2.5-12] 2.2.5-12 GNU C Library: Shared libraries an -- debconf information: * locales/default_environment_locale: en_AU * locales/locales_to_be_generated: en_AU UTF-8, en_AU.ISO-8859-1 ISO-8859-1, en_AU.euro ISO-8859-15, fr_FR ISO-8859-1, [EMAIL PROTECTED] ISO-8859-15, ru_RU KOI8-R ----- End forwarded message ----- -- Debian - http://www.debian.org/ Linux 1394 - http://linux1394.sourceforge.net/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
