public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: libc-alpha@sourceware.org
Subject: the purpose of locale.alias
Date: Sun, 10 Sep 2023 10:55:44 +0200	[thread overview]
Message-ID: <77018150.VQpxGFKSoK@nimes> (raw)

Hi,

What is the purpose of glibc's locale.alias, typically installed as
/usr/share/locale/locale.alias ? (I'm not talking about the X11 locale.alias
here.)

I would like to suggest to improve the comments in it, to clarify its
purpose.

* The comments so far say:
  "
   # Note: This file is obsolete and is kept around for the time being for
   # backward compatibility.  Nobody should rely on the names defined here.
   # Locales should always be specified by their full name.
  "
  And indeed, while nowadays most GNU/Linux users use locales with UTF-8
  encoding, all of the aliases in the current locale.alias file are for
  locales with traditional encodings; they are thus not useful today any more.

* But a valid future use of locale.alias is when a language code changes
  (like in the past: no -> nb, or iw -> he), or when a country code changes
  (like in the past with Yugoslavia or Soviet Union). Such changes can happen
  in the future, and for people who use a rolling-release distribution and
  use locale names in their .profile script, it is useful to be able to
  add a line
     ll_oldCC.UTF-8    ll_newCC.UTF-8
  to the locale.alias file.

* Then there are also people who "want to unify language codes on all
  environments" [1]. This sounds like of minor importance to me. Do you
  think this is a reasonable use-case of locale.alias or not?

Other purposes, that I have missed?

Bruno

[1] https://askubuntu.com/questions/883622/





             reply	other threads:[~2023-09-10  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10  8:55 Bruno Haible [this message]
2023-09-11  7:57 ` Florian Weimer
2023-09-12 18:55   ` Bruno Haible
2023-09-12 19:28     ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=77018150.VQpxGFKSoK@nimes \
    --to=bruno@clisp.org \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).