Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Gentoo: Dev

UTF-8 locale by default

 

 

First page Previous page 1 2 Next page Last page  View All Gentoo dev RSS feed   Index | Next | Previous | View Threaded


michael at orlitzky

Jul 30, 2012, 10:33 AM

Post #26 of 49 (376 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 07/30/12 12:28, Michał Górny wrote:
>
> My point here is that you want the thing to change. So you first try to
> convince people here to change. We practically did a small survey here
> and in the result we didn't agree on doing the change.
>
> So you're saying we should do another survey on another group, hoping
> that this time the result will be on your side.

We didn't do a survey, we asked,

"Is there a reason for not using at least en_US.UTF-8 as a "sane"
default value?"

Unsurprisingly, the responses contained reasons for not using
en_US.UTF-8 as the default.

Don't take my original reply out of context, I don't actually care what
we have as the default.


>
> It depends on who the 'unbiased sample' is. Are you interested only in
> opinion of Gentoo users who visit the website? Who sync once a day?
> Once a week? Who follow Gentoo Planet? Who participate in the forums?
>
> We can create the survey and announce it everywhere. But it still won't
> catch many old-time Gentoo users who can actually have something
> opposite to say. It won't be unbiased.

The technical objection to C.UTF-8 is that it's non-standard, Ok. What
are the technical objections to LC_CTYPE=en_US.UTF-8? If the
alternatives are all improvements, the statistics are irrelevant.


waltdnes at waltdnes

Jul 30, 2012, 12:02 PM

Post #27 of 49 (385 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Mon, Jul 30, 2012 at 01:33:48PM -0400, Michael Orlitzky wrote

> The technical objection to C.UTF-8 is that it's non-standard, Ok.
> What are the technical objections to LC_CTYPE=en_US.UTF-8? If the
> alternatives are all improvements, the statistics are irrelevant.

I ran into a problem several months ago with xfreecell not running.
Turned out the ISO8859-1 fonts were not being generated, just UTF-8.
xfreecell needs ISO8859-1 fonts. And it's not the only package. I
modified xorg-2.eclass so that font packages would build ISO8859-1. See
http://article.gmane.org/gmane.linux.gentoo.user/252316/ for the gory
details. Would forcing UTF-8 cause problems for packages that expect
specific ISO encodings in X fonts?

The important part of the eclass mod was to manually enable iso8859-1
and disable all other encodings...

if grep -q -s "disable-all-encodings" ${ECONF_SOURCE:-.}/configure; then
FONT_OPTIONS+="
--enable-iso8859-1
--disable-iso10646
--disable-iso10646-1
--disable-iso8859-2
--disable-iso8859-3
--disable-iso8859-4
--disable-iso8859-5
--disable-iso8859-6
--disable-iso8859-7
--disable-iso8859-8
--disable-iso8859-9
--disable-iso8859-10
--disable-iso8859-11
--disable-iso8859-12
--disable-iso8859-13
--disable-iso8859-14
--disable-iso8859-15
--disable-iso8859-16
--disable-jisx0201
--disable-koi8-r"
else
FONT_OPTIONS+="
--disable-iso10646
--disable-iso10646-1
--disable-iso8859-2
--disable-iso8859-3
--disable-iso8859-4
--disable-iso8859-5
--disable-iso8859-6
--disable-iso8859-7
--disable-iso8859-8
--disable-iso8859-9
--disable-iso8859-10
--disable-iso8859-11
--disable-iso8859-12
--disable-iso8859-13
--disable-iso8859-14
--disable-iso8859-15
--disable-iso8859-16
--disable-jisx0201
--disable-koi8-r"
fi

--
Walter Dnes <waltdnes [at] waltdnes>


michael at orlitzky

Jul 31, 2012, 8:16 AM

Post #28 of 49 (383 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 07/30/12 15:02, Walter Dnes wrote:
> Would forcing UTF-8 cause problems for packages that expect
> specific ISO encodings in X fonts?

Not that I know of (and setting a default wouldn't force anything).

xfreecell's readme states "Make sure there is a font named 7x14" and
another thread mentions that this is provided by
media-fonts/font-misc-misc so that sounds like a bug in the ebuild to me.


dilfridge at gentoo

Aug 1, 2012, 1:18 PM

Post #29 of 49 (379 views)
Permalink
Re: UTF-8 locale by default [In reply to]

>
> If it turns out that C or POSIX is the most common response, we should
> then default the locale to en_US.UTF-8 if we really want to default to
> a UTF-8 setting. The reason being it makes sense to have the default
> locale set to the country of origin, which in our case is the United
> States.
>

Given the number of Gentoo devs (especially on the desktop side where this
matters most) from other parts of the world, that's not really a valid
argument. In particular in cases as e.g. "Paper size setting", where basically
US stubbornness stands against the rest of the planet.

--

Andreas K. Huettel
Gentoo Linux developer
dilfridge [at] gentoo
http://www.akhuettel.de/
Attachments: signature.asc (0.19 KB)


michael at orlitzky

Aug 1, 2012, 1:29 PM

Post #30 of 49 (372 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 08/01/12 16:18, Andreas K. Huettel wrote:
>
>>
>> If it turns out that C or POSIX is the most common response, we should
>> then default the locale to en_US.UTF-8 if we really want to default to
>> a UTF-8 setting. The reason being it makes sense to have the default
>> locale set to the country of origin, which in our case is the United
>> States.
>>
>
> Given the number of Gentoo devs (especially on the desktop side where this
> matters most) from other parts of the world, that's not really a valid
> argument. In particular in cases as e.g. "Paper size setting", where basically
> US stubbornness stands against the rest of the planet.
>

Every locale is wrong for somebody; the idea was that by taking a
survey, you could make it wrong for the least amount of people (by default).

If the majority of users use a stupid paper size, the best default is
still whatever they use regardless of any personal preferences.


waltdnes at waltdnes

Aug 1, 2012, 5:20 PM

Post #31 of 49 (378 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Wed, Aug 01, 2012 at 04:29:42PM -0400, Michael Orlitzky wrote

> Every locale is wrong for somebody; the idea was that by taking
> a survey, you could make it wrong for the least amount of people
> (by default).

Question... has anybody ever considered that maybe a POSIX locale
is wrong for the least amount of people??? There's also a very damning
statement in the post that started this thread...

On Thu, Jul 19, 2012 at 11:39:59PM +0200, Sascha Cunz wrote
> I recently discovered that I for some reason haven't noticed the
> warning about setting the locale to utf-8 in the gentoo handbook for
> obviously several years; thus i was still running all my systems in
> a POSIX locale since i never cared much about it.
>
> However, since I noticed, I talked to several people about it; all
> of them stating as first response: "Not shipping with a utf-8 locale
> turned on by default nowadays probably is a bug in your distro"

That's right... the poster was running a POSIX locale for several
years ***AND DID NOT HAVE ANY PROBLEMS RELATED TO IT***. Then "several
people said" "Not shipping with a utf-8 locale turned on by default
nowadays probably is a bug in your distro". And suddenly it's a
problem. What's next? Despite running with no problems for many years
with a separate /usr and no initramfs, will we have "several people"
come along and tell us that it's a bug in our distro? Oh... wait...

The fact that "other distros do it" does not constitute justification
for us to do it. If I wanted to run Redhat or Ubuntu, I'd run Redhat or
Ubuntu. We're ignoring a very basic question here... what problems does
shipping with a POSIX locale cause that would be fixed by setting a UTF8
default locale??? I want a real answer. Not something along the lines
of "But daddy, all the other kids are doing it".

--
Walter Dnes <waltdnes [at] waltdnes>


floppym at gentoo

Aug 1, 2012, 6:00 PM

Post #32 of 49 (371 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Wed, Aug 1, 2012 at 8:20 PM, Walter Dnes <waltdnes [at] waltdnes> wrote:
> We're ignoring a very basic question here... what problems does
> shipping with a POSIX locale cause that would be fixed by setting a UTF8
> default locale??? I want a real answer. Not something along the lines
> of "But daddy, all the other kids are doing it".
>

Try reading the rest of the thread before posting a rant.

Diego mentioned the python issue. As well, there are many test suites
that malfunction without a UTF-8 or en_US.UTF-8 locale. If you hunt
through Bugzilla, you can probably dig up other issues.


peter at stuge

Aug 1, 2012, 10:36 PM

Post #33 of 49 (371 views)
Permalink
Re: UTF-8 locale by default [In reply to]

Walter Dnes wrote:
> The fact that "other distros do it" does not constitute
> justification for us to do it.

Unfortunately that exact reason, along with "Fedora is doing it", was
cited by a very active developer as reason to reject technical points
which I tried to make a few times.

But that is off-topic. Let's leave it for later. All I'm saying is
don't underestimate pack mentality.


//Peter


admin at pinkbyte

Aug 1, 2012, 10:43 PM

Post #34 of 49 (371 views)
Permalink
Re: UTF-8 locale by default [In reply to]

02.08.2012 04:20, Walter Dnes wrote:
> That's right... the poster was running a POSIX locale for several
> years ***AND DID NOT HAVE ANY PROBLEMS RELATED TO IT***.
This discussion is very similar with one, that i have seen in Russian
Linux community some years ago about migrating from ru_RU.KOI8-R to
ru_RU.UTF-8. Arguments from "KOI8-R guys" were the same - "Why we should
change something if it works?" and they are also did not notice
fundamental problems with some vitally important packages, which can not
be replaced or need to be heavily patched to work properly. Arguments
from "UTF-8 guys" were not ideal, but locale change brokes only old or
unsupported packages, so they win.

P.S. I do not think that comparison with 'initramfs and separate /usr
problem' is correct in this case. Default locale change is evolution,
not revolution...
Attachments: signature.asc (0.54 KB)


grobian at gentoo

Aug 1, 2012, 11:42 PM

Post #35 of 49 (374 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 01-08-2012 21:00:23 -0400, Mike Gilbert wrote:
> Diego mentioned the python issue.

Honestly, if some asian person has whatever charset that I often find in
spam messages, but is not UTF-8, are you then going to tell that person
to switch to UTF-8 to get those python packages emerged? I hope not.

There is a difference between "there is a UTF-8 locale available on the
system" and "en_US.UTF-8 locale is in effect".

Fabian

--
Fabian Groffen
Gentoo on a different level
Attachments: signature.asc (0.19 KB)


sionescu at cddr

Aug 2, 2012, 2:14 AM

Post #36 of 49 (367 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Thu, 2012-08-02 at 08:42 +0200, Fabian Groffen wrote:
> On 01-08-2012 21:00:23 -0400, Mike Gilbert wrote:
> > Diego mentioned the python issue.
>
> Honestly, if some asian person has whatever charset that I often find in
> spam messages, but is not UTF-8, are you then going to tell that person
> to switch to UTF-8 to get those python packages emerged? I hope not.

Yes.

--
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
http://common-lisp.net/project/iolib
Attachments: signature.asc (0.19 KB)


flameeyes at flameeyes

Aug 2, 2012, 11:21 AM

Post #37 of 49 (367 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 01/08/2012 23:42, Fabian Groffen wrote:
> Honestly, if some asian person has whatever charset that I often find in
> spam messages, but is not UTF-8, are you then going to tell that person
> to switch to UTF-8 to get those python packages emerged? I hope not.

Tell that to the Python team I guess. My tinderbox _has_ utf8 locales
available, but doesn't set in by default -> Python stuff fails to build
or test -> not going to be fixed with "change your locale" reasoning.

Is it mental? Yes.
Would I like that to change? Yes.
Do I care ẃhether that's through the use of cluebyfour on the Python
team or by setting an utf-8 locale by default? Not in the least.

--
Diego Elio Pettenò — Flameeyes
flameeyes [at] flameeyes — http://blog.flameeyes.eu/
Attachments: signature.asc (0.54 KB)


1i5t5.duncan at cox

Aug 2, 2012, 11:22 AM

Post #38 of 49 (363 views)
Permalink
Re: UTF-8 locale by default [In reply to]

Peter Stuge posted on Thu, 02 Aug 2012 07:36:07 +0200 as excerpted:

> Walter Dnes wrote:
>> The fact that "other distros do it" does not constitute justification
>> for us to do it.
>
> Unfortunately that exact reason, along with "Fedora is doing it", was
> cited by a very active developer as reason to reject technical points
> which I tried to make a few times.
>
> But that is off-topic. Let's leave it for later. All I'm saying is don't
> underestimate pack mentality.

I don't know if it applies here, but there's a difference between "other
distros do it", and "that's the way upstream created it". If upstream is
effectively another distro, the first might be true as well, but gentoo
has always had a policy of trying to do it upstream's way unless there's
a good reason not to, and that's quite different than just following the
distro pack. (You likely know this already, but other readers may not,
so I'm emphasizing it.)

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman


floppym at gentoo

Aug 2, 2012, 11:32 AM

Post #39 of 49 (368 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Thu, Aug 2, 2012 at 2:21 PM, Diego Elio Pettenò
<flameeyes [at] flameeyes> wrote:
> On 01/08/2012 23:42, Fabian Groffen wrote:
>> Honestly, if some asian person has whatever charset that I often find in
>> spam messages, but is not UTF-8, are you then going to tell that person
>> to switch to UTF-8 to get those python packages emerged? I hope not.
>
> Tell that to the Python team I guess. My tinderbox _has_ utf8 locales
> available, but doesn't set in by default -> Python stuff fails to build
> or test -> not going to be fixed with "change your locale" reasoning.
>
> Is it mental? Yes.
> Would I like that to change? Yes.
> Do I care ẃhether that's through the use of cluebyfour on the Python
> team or by setting an utf-8 locale by default? Not in the least.
>

Please apply the cluebyfour to the upstream developers of python and
python modules. :-)

I do try to fix unicode problems if I run into them. However,
sometimes it just isn't worth the effort.


aballier at gentoo

Aug 2, 2012, 11:45 AM

Post #40 of 49 (364 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Thu, 02 Aug 2012 11:21:40 -0700
Diego Elio Pettenò <flameeyes [at] flameeyes> wrote:

> On 01/08/2012 23:42, Fabian Groffen wrote:
> > Honestly, if some asian person has whatever charset that I often
> > find in spam messages, but is not UTF-8, are you then going to tell
> > that person to switch to UTF-8 to get those python packages
> > emerged? I hope not.
>
> Tell that to the Python team I guess. My tinderbox _has_ utf8 locales
> available, but doesn't set in by default -> Python stuff fails to
> build or test -> not going to be fixed with "change your locale"
> reasoning.

not that it is hard to set LC_ALL=sth before running the failing
command, or make the pm do it... we already fix regexp bugs with other
locales (or workaround them by setting LC_ALL=C), it falls under the
same category.
you just need to teach people, and maybe mandate an utf8 locale to be
present; the same way they do not consider estonian alphabet ordering
'broken' they would not consider not having an utf8 locale 'broken',
esp. when said utf8 is far from being optimal in terms of size for asian
languages.

A.


kentfredric at gmail

Aug 2, 2012, 2:38 PM

Post #41 of 49 (387 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 31 July 2012 05:33, Michael Orlitzky <michael [at] orlitzky> wrote:
> On 07/30/12 12:28, Michał Górny wrote:
>>
>> My point here is that you want the thing to change. So you first try to
>> convince people here to change. We practically did a small survey here
>> and in the result we didn't agree on doing the change.
>>
>> So you're saying we should do another survey on another group, hoping
>> that this time the result will be on your side.
>
> We didn't do a survey, we asked,
>
> "Is there a reason for not using at least en_US.UTF-8 as a "sane"
> default value?"
>
> Unsurprisingly, the responses contained reasons for not using
> en_US.UTF-8 as the default.
>

I think its a shame that :

1. the current handbook way to change timezone is manually editing a file.
2. the handbook doesn't mention `eselect locale`
3. `eselect locale list` is useless if you have *all* locales available to you.
4. `eselect locale` can only set the LANG variable.
5. that eselect doesn't have an interactive mode yet.

Why? because this problem could be made simpler by providing a way to
use a recommended locale for your timezone, which is likely to yield a
more sane default for that timezone.

It would also make it easier to validate the value the user chooses
for their Timezone value.

Consider:

eselect timezone list
# all level 1 timezones + groups , ie: like ls /usr/share/zoneinfo
eselect timezone list America/
# contents of /usr/share/zoneinfo/America
eselect timezone set America/Chicago
# /etc/timezone is updated to 'America/Chicago'
# /etc/localtime is replaced with /usr/share/zoneinfo/America/Chicago
eselect locale set --all auto
# LANG and LC_* are set using the values defined as "default" for
America/Chicago
eselect locale set --ctype auto
# Only LC_CTYPE is autopopulated.
eselect locale list
# 600 items because you have a vanilla locale.defs
eselect locale list --timezone
# shows a list of LOCALE values for the current TZ, with the one that
would be used as default first/marked up differently
eselect locale list en
# shows english locale options
eselect locale set --ctype en_US.utf8


The benefits of setting these locales this way are obvious to me at
least, you can set locales to a value that is sensible automatically.
You also can validate a users choice of locale and provide feedback,
such as, you can list non-installed locales, and then tell the user if
thy try to use a locale that isn't installed yet they need to update
locales.def

The only way I can suggest something better, would be an interactive
locale setter, something like 'tzselect' , except sets timezone *and*
locale information, with the ability to automatically update
locales.def and add new locale definitions and regenerate the locale
database.

This way, you could have a selection process more like this:

https://gist.github.com/3240866

#? 1

The following information has been given:

United States
Eastern Time

Therefore TZ='America/New_York' will be used.
Local time is now: Thu Aug 2 17:33:17 EDT 2012.
Universal Time is now: Thu Aug 2 21:33:17 UTC 2012.
Is the above information OK?
1) Yes
2) No
#? 1
Your Current locale settings are:

LANG="POSIX"

The recommended settings for your locale are :
LANG="en_US.utf8"
LC_CTYPE="en_US.utf8"

Do you wish to change your locale settings at this time?
1) No
2) Yes - Use recommended settings
3) Yes - Configure locale interactively.

At least this way, the effort required to configure your system into a
very good logical UTF8 default is trivial.

--
Kent

perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"

http://kent-fredric.fox.geek.nz


lu_zero at gentoo

Aug 2, 2012, 10:16 PM

Post #42 of 49 (367 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 07/27/2012 07:24 PM, Mike Frysinger wrote:
> yes, and i'm waiting on the POSIX group to formalize C.UTF-8. that's the only
> real option in my mind for making unicode the default. any other
> amalgamations of various locales is ugly as sin.

When they meet? I'd be fine with a pre-release =P

lu


quantumsummers at gentoo

Aug 3, 2012, 7:59 AM

Post #43 of 49 (379 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Thu, Aug 2, 2012 at 1:32 PM, Mike Gilbert <floppym [at] gentoo> wrote:
> On Thu, Aug 2, 2012 at 2:21 PM, Diego Elio Pettenò
> <flameeyes [at] flameeyes> wrote:
>> On 01/08/2012 23:42, Fabian Groffen wrote:
>>> Honestly, if some asian person has whatever charset that I often find in
>>> spam messages, but is not UTF-8, are you then going to tell that person
>>> to switch to UTF-8 to get those python packages emerged? I hope not.
>>
>> Tell that to the Python team I guess. My tinderbox _has_ utf8 locales
>> available, but doesn't set in by default -> Python stuff fails to build
>> or test -> not going to be fixed with "change your locale" reasoning.
>>
>> Is it mental? Yes.
>> Would I like that to change? Yes.
>> Do I care ẃhether that's through the use of cluebyfour on the Python
>> team or by setting an utf-8 locale by default? Not in the least.
>>
>
> Please apply the cluebyfour to the upstream developers of python and
> python modules. :-)
>
> I do try to fix unicode problems if I run into them. However,
> sometimes it just isn't worth the effort.
>

Python upstream is doing what they think is best in using unicode.

That said, what if we just temporarily set a locale in the ebuild for
running tests and elsewhere? Is this unreasonable or impossible? It
might not be a great solution, this method, since users' stuff will
still break.

Further, I support the use of C.UTF-8 when it is ready. It seems like
the lowest common denominator to me.


--
Matthew W. Summers
Gentoo Foundation Inc.


mgorny at gentoo

Aug 3, 2012, 8:47 AM

Post #44 of 49 (366 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Fri, 3 Aug 2012 09:59:42 -0500
Matthew Summers <quantumsummers [at] gentoo> wrote:

> On Thu, Aug 2, 2012 at 1:32 PM, Mike Gilbert <floppym [at] gentoo>
> wrote:
> > On Thu, Aug 2, 2012 at 2:21 PM, Diego Elio Pettenò
> > <flameeyes [at] flameeyes> wrote:
> >> On 01/08/2012 23:42, Fabian Groffen wrote:
> >>> Honestly, if some asian person has whatever charset that I often
> >>> find in spam messages, but is not UTF-8, are you then going to
> >>> tell that person to switch to UTF-8 to get those python packages
> >>> emerged? I hope not.
> >>
> >> Tell that to the Python team I guess. My tinderbox _has_ utf8
> >> locales available, but doesn't set in by default -> Python stuff
> >> fails to build or test -> not going to be fixed with "change your
> >> locale" reasoning.
> >>
> >> Is it mental? Yes.
> >> Would I like that to change? Yes.
> >> Do I care ẃhether that's through the use of cluebyfour on the
> >> Python team or by setting an utf-8 locale by default? Not in the
> >> least.
> >>
> >
> > Please apply the cluebyfour to the upstream developers of python and
> > python modules. :-)
> >
> > I do try to fix unicode problems if I run into them. However,
> > sometimes it just isn't worth the effort.
> >
>
> Python upstream is doing what they think is best in using unicode.
>
> That said, what if we just temporarily set a locale in the ebuild for
> running tests and elsewhere? Is this unreasonable or impossible? It
> might not be a great solution, this method, since users' stuff will
> still break.

It is impossible because you can't know which locale a particular
system has available. AFAIK there's no 'it-will-always-work' choice;
unless we're going to enforce generating some common locale, or do very
ugly things.

>
> Further, I support the use of C.UTF-8 when it is ready. It seems like
> the lowest common denominator to me.

--
Best regards,
Michał Górny
Attachments: signature.asc (0.31 KB)


aballier at gentoo

Aug 3, 2012, 9:54 AM

Post #45 of 49 (363 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Fri, 3 Aug 2012 17:47:24 +0200
Michał Górny <mgorny [at] gentoo> wrote:
> > Python upstream is doing what they think is best in using unicode.
> >
> > That said, what if we just temporarily set a locale in the ebuild
> > for running tests and elsewhere? Is this unreasonable or
> > impossible? It might not be a great solution, this method, since
> > users' stuff will still break.
>
> It is impossible because you can't know which locale a particular
> system has available. AFAIK there's no 'it-will-always-work' choice;
> unless we're going to enforce generating some common locale, or do
> very ugly things.

I don't think anyone will object to enforcing a given locale to be
present, even en_US.UTF-8; people will object if they have to use that
locale.

Maybe locale-gen can even generate it on-the-fly in $T, I don't know.

A.


flameeyes at flameeyes

Aug 3, 2012, 10:09 AM

Post #46 of 49 (364 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 03/08/2012 09:54, Alexis Ballier wrote:
> I don't think anyone will object to enforcing a given locale to be
> present, even en_US.UTF-8; people will object if they have to use that
> locale.
>
> Maybe locale-gen can even generate it on-the-fly in $T, I don't know.

Agreed. And there _is_ a way to tell which locales are available:
`locale -a`.

--
Diego Elio Pettenò — Flameeyes
flameeyes [at] flameeyes — http://blog.flameeyes.eu/


ormaaj at gmail

Aug 7, 2012, 6:58 PM

Post #47 of 49 (305 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On Friday, August 03, 2012 07:16:45 AM Luca Barbato wrote:
> On 07/27/2012 07:24 PM, Mike Frysinger wrote:
> > yes, and i'm waiting on the POSIX group to formalize C.UTF-8. that's the
only
> > real option in my mind for making unicode the default. any other
> > amalgamations of various locales is ugly as sin.
>
> When they meet? I'd be fine with a pre-release =P
>
> lu
>

2008 TC1 is just finishing up balloting as we speak. If this isn't already in
there you may be in for a long wait. Feel free to subscribe to the austin-
group lists -- It's open to anyone. A calendar with the teleconference
schedule is available.
--
Dan Douglas
Attachments: signature.asc (0.19 KB)


mk at dee

Dec 31, 2012, 9:14 AM

Post #48 of 49 (149 views)
Permalink
Re: UTF-8 locale by default [In reply to]

Hi,

stage3 now includes non-ASCII paths, via app-misc/ca-certificates -- e.g.:
/usr/share/ca-certificates/mozilla/TÜBÝTAK_UEKAE_Kök_Sertifika_Hizmet_Saðlayýcýsý_-_Sürüm_3.crt

Working with those (e.g., backup) probably requires a UTF-8 locale. Is
this considered acceptable? Did anyone notice?

--
Maxim Kammerer
Liberté Linux: http://dee.su/liberte


zmedico at gentoo

Dec 31, 2012, 1:44 PM

Post #49 of 49 (149 views)
Permalink
Re: UTF-8 locale by default [In reply to]

On 12/31/2012 09:14 AM, Maxim Kammerer wrote:
> Hi,
>
> stage3 now includes non-ASCII paths, via app-misc/ca-certificates -- e.g.:
> /usr/share/ca-certificates/mozilla/TÜBÝTAK_UEKAE_Kök_Sertifika_Hizmet_Saðlayýcýsý_-_Sürüm_3.crt
>
> Working with those (e.g., backup) probably requires a UTF-8 locale. Is
> this considered acceptable? Did anyone notice?

It's been that way for a very long time (over a year). Since bug #382199
[1], portage uses a constant UTF-8 encoding for all installed files
regardless of the locale, so at least you can count on portage handling
those UTF-8 names even if you don't have a UTF-8 locale configured.

[1] https://bugs.gentoo.org/show_bug.cgi?id=382199
--
Thanks,
Zac

First page Previous page 1 2 Next page Last page  View All Gentoo dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.