svn commit: r281129 - head/etc

[Slawa Olhovchenkov]

On Fri, Apr 10, 2015 at 03:02:59AM +0300, Dmitry Marakasov wrote:

> * Slawa Olhovchenkov (slw at zxy.spb.ru) wrote:
> 
> > We don't have any default login class, other then 'dafault' and have
> > locale 'C'. What about you talk?
> 
> I'm talking about having utf-8 locale in 'default' login class.

At this moment many programs still not utf8 capable.
Programs used in scripts -- too.
`tr` for example.
Swithcing 'default' login class to utf8 locale may break scripts, and
custom scripts too.
What benefits from switching to utf8 locale in 'default' login class?

> > Do you this converting? I am do it.
> 
> Didn't quite catch that.
> 
> > What about you talk?
> > Just create new login class, 'russian_utf8', and have fun.
> > This is not windows. This is Unix.
> > Locale is not system-wide.
> > You can have multiple locales together.
> > What problems?
> 
> No problems, you can still use any locale you want. You are free
> to stay on KOI-8 and not do any charset conversion at all.

Best way for this -- adding new login class, not changed existing

> > > > Also, some config files (from ports) have raw 8-bit characters inside.
> > > 
> > > They'll have to be converted based on OSVERSION/option.
> > 
> > You don't understund me.
> > This charters don't have any encodings/locales.
> > This is just octets.
> 
> You're talking of config files which are not utf-8. I say they will be
> converted to utf-8 if that's needed.

...and not utf-8 capable. Imposible convert it to utf8.