Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 25 Jan 2015 19:23:06 +0300
From:      Slawa Olhovchenkov <slw@zxy.spb.ru>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        "freebsd-arch@freebsd.org" <arch@freebsd.org>, Baptiste Daroussin <bapt@freebsd.org>, Jordan Hubbard <jkh@ixsystems.com>
Subject:   Re: [RFC] Set the default locale to en_US.UTF-8
Message-ID:  <20150125162306.GP3698@zxy.spb.ru>
In-Reply-To: <CAJ-Vmo=RhpxgJ=0s2nim0zRDKr3wACmGc=4RGAXqF%2BFrrZsLHQ@mail.gmail.com>
References:  <20150124143357.GI81001@ivaldir.etoilebsd.net> <20150125143243.GB76051@zxy.spb.ru> <7B1D8345-248B-4C44-9568-079BA29614C2@ixsystems.com> <20150125155000.GD76051@zxy.spb.ru> <CAJ-Vmo=RhpxgJ=0s2nim0zRDKr3wACmGc=4RGAXqF%2BFrrZsLHQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 25, 2015 at 08:11:09AM -0800, Adrian Chadd wrote:

> File bugs file bugs file bug file bugs *sings*
> 
> Yes, file bugs when you come across these issues.

You offer me to submit PR?
I think this is not fixable: locale is UTF-8, historical content is not valid UTF-8,
software wait text in current locale and got crap. No way.

I see only two choise:

1. use locale that accept any byte string
2. strict convert all content to utf-8 and use utf-8. strict convert is required. And this
is can't be done in general case (text string may be any any places).

> On 25 January 2015 at 07:50, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:
> > On Sun, Jan 25, 2015 at 06:58:13AM -0800, Jordan Hubbard wrote:
> >
> >>
> >> > On Jan 25, 2015, at 6:32 AM, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:
> >> >
> >> > NO! Please, NOT!
> >> > Not all bytestring allowed in UTF-8, as result -- unpedicable failed
> >> > execution of sed, grep, vi, ed and etc.
> >>
> >> Huh.  Someone should warn Apple then, since $LANG has been set to en_US.UTF-8 by default in OS X for years now.  I just checked, and sed/grep/vi/ed/etc all still work. :)
> >>
> >> It's a good idea to change it.  We have outgrown ISO-Latin1, and UTF-8 solves a host of ugly I18N interoperability problems when used consistently.
> >
> > I am years use ru_RU.KOI8-R. Now I try use ru_RU.UTF8 and got some
> > issuse (on 10-STABLE). 9.x and OS may have dufferent version of
> > software and don't touch this.
> >
> > vi ~/tips.work
> > /home/slw/tips.work: unmodified: line 1; Conversion error on line 3
> >
> > This is koi8 file in utf8 locale.
> >
> > Other case -- file names in koi8 locale -- this is invalid in utf-8.
> > Change locale from C to utf8 may cause trouble.
> > This is (change from one-byte tu multi-bytes locale) may be do
> > individualy, after inspecting systems. This is may be OK for new
> > install, but not [automatic] for update/upgrade.
> > _______________________________________________
> > freebsd-arch@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150125162306.GP3698>