X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/e36a8d47a9de1c117d292a2704009e226d77516e..bcdb0eb24c38dbb17f806f411f55c9f8cc7d4429:/linux/glibc/index.html diff --git a/linux/glibc/index.html b/linux/glibc/index.html index 33bc553ce0..4930508f28 100644 --- a/linux/glibc/index.html +++ b/linux/glibc/index.html @@ -53,6 +53,14 @@ all the fixes included in the official releases of the source.

+

Mailing list for discussing locales

+ +

A mailing list for discussing the GNU libc locales have been + created. It is + archived on + the web. Send an email to + libc-locales-subscribe@sources.redhat.com to subscribe.

+

References to documentation and standards

It is currently an open question where the format og locales in @@ -83,25 +91,41 @@ -

To make it easier to compare locales with each other, I - recommend using the same order in all locales. Any order will - do, so I picked a order used in several locales, and decided to - recommend this order:

- -
    -
  1. LC_IDENTIFICATION -
  2. LC_CTYPE -
  3. LC_COLLATE -
  4. LC_MONETARY -
  5. LC_NUMERIC -
  6. LC_TIME -
  7. LC_MESSAGES -
  8. LC_PAPER -
  9. LC_NAME -
  10. LC_ADDRESS -
  11. LC_TELEPHONE -
  12. LC_MEASUREMENT -
+

Changing a locale

+ +

Getting locale fixes past the glibc maintainers is still a + kind of black art to me. This is my first try to document + what I believe is needed to get the glibc maintainers to + accept a change.

+ +

Register the change request in bugzilla, to make sure the + request is not forgotten, and that all relevant info is + collected in one place.

+ +

It is always good to involve the original locale author when + submitting a change request. Getting the original author to + agree to the change increases the chance that the glibc + maintainers will accept it. It is also an idea to involve the + contributors to the locale. This is why I maintain a list of + authors and contributors for each locale. The people listed + there should be emailed as well, and asked for comments. If + the contributors agree as well, the change is less likely to + be controversial, and more likely to be accepted by the glibc + maintainers.

+ +

Give references to official standards and specifications + documenting the correct locale behavoiur. URLs are fine. If + such references are impossible to find, official-looking pages + might have the same effect. Another idea is to show + locale-specific use of dates and other formatting on + country-official web pages and other publications.

+ +

If all of these are present, the change is likely to be + accepted by the glibc maintainer. If some of them are missing + (like the author is unavailable, no standard and + specifications exist, and it is hard to document the correct + format, I do not know how to get the change past the glibc + maintainers.

Locale related problem reports

@@ -181,8 +205,8 @@ nb_NO should be a real locale, not an alias
Same as libc/2931 -
  • #208238: locales: - wrong charset for et_EE +
  • #208238: locales: + wrong charset for et_EE
  • #211607: Bad catalan locale currency format @@ -193,8 +217,8 @@
  • #214414: Incorrect date format in en_NZ -
  • #215466: fi_FI - locale doesn't contain first_weekday +
  • #215466: fi_FI + locale doesn't contain first_weekday @@ -445,20 +469,27 @@ -

    Mailing list for discussing locales

    +

    Related web pages

    -

    A mailing list for discussing the GNU libc locales have been - created. It is - archived on - the web. Send an email to - libc-locales-subscribe@sources.redhat.com to subscribe.

    +
    -
    Petter Reinholdtsen
    +
    Petter Reinholdtsen
    -Last modified: Sat May 15 12:01:01 CEST 2004 +Last modified: Sun Jul 18 10:07:40 CEST 2004