Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Nov 2015 08:46:26 -0800
From:      Garrett Cooper <yaneurabeya@gmail.com>
To:        marino@freebsd.org
Cc:        Andrey Chernov <ache@freebsd.org>, Baptiste Daroussin <bapt@freebsd.org>, arch@freebsd.org, Ed Schouten <ed@nuxi.nl>
Subject:   Re: Question about ASCII and nl_langinfo (locale work)
Message-ID:  <05BE03FC-365D-46BF-9CB9-A83917784F20@gmail.com>
In-Reply-To: <b4625b7821cba9165921c3838d5177a8@secure.marino.st>
References:  <20151110222636.GN10134@ivaldir.etoilebsd.net> <CABh_MKkAJmfTrT5qMwvcOcFAviD9h8okOnsH7PJ2x7gxFvY5Yw@mail.gmail.com> <564A27CD.7090908@freebsd.org> <20151116210659.GB59189@ivaldir.etoilebsd.net> <564A4FE9.6000403@freebsd.org> <b4625b7821cba9165921c3838d5177a8@secure.marino.st>

next in thread | previous in thread | raw e-mail | index | archive | help

> On Nov 17, 2015, at 00:22, John Marino (FreeBSD) <freebsd.contact@marino.s=
t> wrote:
>=20
>> 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 fir=
st plan
>>> in the collation branch was to introduce the IANA syntax via an alias bu=
t 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.
>=20
> 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.
>=20
> This is a change for changes sake.
>=20
> Locale -m lists the encodings.
> Locale -a lists the available locales
>=20
> This is true on Linux as well.
> Nobody is getting POLA'D here.
>=20
> 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.
>=20
> 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=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05BE03FC-365D-46BF-9CB9-A83917784F20>