On 2020-07-23 08:02, Harald Dunkel wrote:
> Not yet. Do you have some Posix document, RFC, best practice guideline, etc
> showing that it should be "C.UTF-8" instead of "UTF-8"? Something to present
> to Apple proving  that they are not Posix compliant?
> https://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html
> says
>       "The contents of this string are implementation-defined."

Please have a look at:


It says most notably:

| If the locale value has the form:
|     language[_territory][.codeset]
| it refers to an implementation-provided locale, where settings of
| language, territory, and codeset are implementation-defined.

This format is used in many UNIXes, for instance AIX, Solaris, SCO
UnixWare, HP UX. That said, MacOS has the possibility to use other
format as said below:

| "An implementation may support other formats."

However it should not assume that other systems also support that
implementation specific format.

> I could live with having to run localedef once to define a locale UTF-8
> at installation time, but that is wiped out again and again, see #965323.

Each time the locales package is update, the format might have changed,
or at minimum the locales need to be regenerated to take into in account
possible changes in the locale sources.

> What would you suggest?

You can use the /etc/locale.alias mechanism, it's deprecated, but that
works for now. Just add the following line to that file:

UTF-8           C.UTF-8


Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                 http://www.aurel32.net

Reply via email to