From: michael.baeuerle@stz-e.de
James Kuyper wrote:
> On 2025-11-18 15:17, Michael Sanders wrote:
> > On Tue, 18 Nov 2025 14:27:53 -0500, James Kuyper wrote:
> > >
> > > Could you identify which document guarantees that every Unicode locale
> > > contains "UTF-8"? Do you know what the domain of applicability of that
> > > document is? It apparently does not cover my Ubuntu Linux system. The
> > > command "locale -a" provides a list of all supported locales. Here's
> > > what it says:
> > >
> > > [...]
> >
> > Hi James, umm 'guarantees'? No no... It does NOT verify:
> >
> > - whether the environment actually supports UTF8 fully
> > - whether multibyte functions are enabled
> > - whether the terminal supports UTF8
> > - whether the C library supports UTF8 normalization
> > (combining characters, etc. but it seems to work well here)
> >
> > To be sure: It's not a UTF-8 capability test. It's only a
> > locale-string check. So it likely misses many valid UTF8
> > locale variants...
>
> If intended for use by anyone other than yourself, you should document
> it's limitations in that regard, either with in-code comments or in user
> documentation.
>
> > Here I'm running any mixture of: Windows/BSD/Linix Mint LMDE.
> >
> > The best I can tell you at this stage is that it works on my end,
> > not a very satisfying reply I'm sure you'd agree. But till I learn
> > more about the issue that's the best I can offer.
> >
> > If you manage an improvement, please do post it here in the group
> > so I can learn more too.
>
> There might be documents specifying locale naming standards, but I'm not
> aware of any. [...]
POSIX.1-2024 documents one for the XSI extension in Section 8.2:
|
| 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.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
