This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: proposal: making sure all locales use the same section order
- From: Petter Reinholdtsen <pere at hungry dot com>
- To: libc-alpha at sources dot redhat dot com
- Date: 20 Jun 2003 23:17:35 +0200
- Subject: Re: proposal: making sure all locales use the same section order
- References: <E19SNNt-0005fW-00@minerva.hungry.com><3EEF8080.1070000@redhat.com>
- Reply-by: Tue, 1 Jan 1801 04:37:40 +1000
[Ulrich Drepper]
> Why do you keep referring to this unusable write-up which has no
> approval by anybody and which does not reflect what we have in
> glibc?
I am still wondering which standard document I should be reading to
learn the format of the glibc locale files. Do you have a reference?
Anyway, I got another idea. Lets recommend the section order used by
locales/i18n and locales/en_US. This way, at least some locales do
not need to change. I suggest starting with the following patch to
localedata/README.
--- README.~1.3.~ Thu Jul 20 13:10:29 2000
+++ README Fri Jun 20 23:12:53 2003
@@ -63,6 +63,24 @@
values with are built in the libc binaries as default values when no
legal locale is found or the "C" or "POSIX" locale is selected.
+ Writing locales
+ ###############
+
+It is recommended to use the same order in all locales, and the glibc
+maintainers have decided to recommend the following order:
+
+ LC_IDENTIFICATION
+ LC_CTYPE
+ LC_COLLATE
+ LC_MONETARY
+ LC_NUMERIC
+ LC_TIME
+ LC_MESSAGES
+ LC_PAPER
+ LC_NAME
+ LC_ADDRESS
+ LC_TELEPHONE
+ LC_MEASUREMENT
The collation test suite
########################