Locale problem updating 10.3 to 11.1

[Brandon Allbery]

Sorry, it's a bit trickier than that. I said "touching", not "using" as in
"UTF-8 locale".

Any locale system needs a common base to build locale descriptions from.
Unicode, or something functionally equivalent to it -- but given that we
need to support Unicode locales anyway, it makes the most sense ---
provides that common base.

So anything that affects Unicode handling implicitly affects the entire
locale system. LANG=C is the exception, because by the locale specification
it is the null mapping / what you would get if there were no locale system
at all.

On Wed, Feb 21, 2018 at 3:14 AM, <sthaug at nethelp.no> wrote:

> > > However, since it was mentioned in a note starting with
> > > "Add support for unicode collation" I most likely didn't even read it
> > > since I'll never touch unicode.
> > >
> >
> > If you ever use anything other than LANG=C, you *are* touching Unicode.
>
> % echo $LANG
> LANG: Undefined variable.
>
> % echo $LC_CTYPE
> nb_NO.ISO8859-1
>
> Works for me.
>
> But I did use a while to figure out what had happened between 10.3 and
> 11.1, since my Norwegian æøå suddenly stopped working (before changing
> LC_CTYPE to nb_NO.ISO8859-1).
>
> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
>



-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net