[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #47838] Confusing "main dialect" statement for $LANGUAGE
From: |
Bruno Haible |
Subject: |
[bug #47838] Confusing "main dialect" statement for $LANGUAGE |
Date: |
Thu, 24 Oct 2024 07:52:28 -0400 (EDT) |
Update of bug #47838 (group gettext):
Status: None => Fixed
Assigned to: None => haible
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
Thanks for the report. Fixed through
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=ee33eefee56f41ba8181f43d5bd7708bdfa71c83
> colord’s MOs are available in both it and it_IT.
It is sufficient to have it installed under 'it', since users will often have
set LANGUAGE=it (per
https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable.html
).
> This description also made me believe that setting LANGUAGE=zh will give
zh_CN.
Good point. I have now added special advice regarding Chinese, since Chinese
is special.
> Which is the "main dialect" of English, en_GB (by history) or en_US (by
population)?
Let's not get into this. Nevertheless your proposed wording with "unspecified"
is not useful to users.
> In BCP 47 the meaning of a primary language subtag unqualified by a region
subtag is simply "the specified language, regional variant not given".
But the glibc locale system is not like BCP 47. The glibc locales are
specified by 1. language, 2. territory, whereas in BCP 47 the script has
higher priority than the territory. Therefore we cannot use BCP 47 in the
documentation.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?47838>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #47838] Confusing "main dialect" statement for $LANGUAGE,
Bruno Haible <=