From: Florian Weimer <fweimer@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: libc-alpha@sourceware.org
Subject: Re: the purpose of locale.alias
Date: Mon, 11 Sep 2023 09:57:29 +0200 [thread overview]
Message-ID: <87cyyp2lcm.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <77018150.VQpxGFKSoK@nimes> (Bruno Haible's message of "Sun, 10 Sep 2023 10:55:44 +0200")
* Bruno Haible:
> * 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.
In addition to what is currently in intl/locale.alias, localedef creates
additional aliases when populating the archive, along those lines.
These aliases are currently missing from “locale -a” output, and some
people have noticed. Without a locale archvie, this seems indeed a use
case for locale.alias.
Thanks,
Florian
next prev parent reply other threads:[~2023-09-11 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 8:55 Bruno Haible
2023-09-11 7:57 ` Florian Weimer [this message]
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=87cyyp2lcm.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=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).