Question about ASCII and nl_langinfo (locale work)
Garrett Cooper
yaneurabeya at gmail.com
Tue Nov 17 16:46:30 UTC 2015
> On Nov 17, 2015, at 00:22, John Marino (FreeBSD) <freebsd.contact at marino.st> wrote:
>
>> On 11/16/2015 10:51 PM, Andrey Chernov wrote:
>>> On 17.11.2015 0:06, Baptiste Daroussin wrote:
>>> locales the IANA way and are unhappy because that does not work. The first plan
>>> in the collation branch was to introduce the IANA syntax via an alias but in the
>>> end I removed it, because there was already to many changes.
>> For ISO case we don't need aliases and can keep our internal names
>> hierarchy honoring POLA. All we need is:
>> 1) Convert "ISO-" and "ISO_" to "ISO" for setlocale(3) input.
>> 2) Convert from "ISO" to "ISO-" for setlocale(3), nl_langinfo(3) and
>> locale(1) output.
>
> A huge patch just went into GCC libstdc++ testsuite to change all the
> locale names to "ISO8859-" because it works for both Linux and *BSD.
>
> This is a change for changes sake.
>
> Locale -m lists the encodings.
> Locale -a lists the available locales
>
> This is true on Linux as well.
> Nobody is getting POLA'D here.
>
> Moveover, there is significant work to implement this. We brought up
> the possibility of hyphen- and case- sensitivity on DragonFly and the
> idea was shot down. The reasons were solid enough.
>
> There is no standard for encoding, period. Using one source is as valid
> another another. I say leave it alone.
Windows is probably the closest thing to a standard here. What does it use -- dashes or underscores?
Thanks,
-NGie
More information about the freebsd-arch
mailing list