1 |
On Fri, 27 Jul 2012 16:34:01 +0800 |
2 |
Ben de Groot <yngwin@g.o> wrote: |
3 |
|
4 |
> On 27 July 2012 16:06, Dan Douglas <ormaaj@×××××.com> wrote: |
5 |
> > On Friday, July 27, 2012 09:08:36 AM Ulrich Mueller wrote: |
6 |
> >> >>>>> On Fri, 27 Jul 2012, Ben de Groot wrote: |
7 |
> >> |
8 |
> >> > I understand why the council rejected Debian's C.UTF-8 option, |
9 |
> >> > but is there really no better default that we can use? |
10 |
> >> |
11 |
> >> > Without any default locale set, in practically all cases that |
12 |
> >> > means that the user is presented with English, and mostly the |
13 |
> >> > American variant. So, in practice, we are defaulting to en_US, |
14 |
> >> > just not in a unicode environment. Correct me if I'm wrong. |
15 |
> >> |
16 |
> >> See below. We're not defaulting to en_US for things like the number |
17 |
> >> format. |
18 |
> >> |
19 |
> >> > Also, in most other places (such as our website, GLEPs, ebuilds) |
20 |
> >> > we default to en_US.UTF-8. |
21 |
> >> |
22 |
> >> > So let's upgrade to en_US.UTF-8, which is for most users more |
23 |
> >> > desirable than the current situation. Of course we will still |
24 |
> >> > advise them to set their desired locales in /etc/locale.gen. But |
25 |
> >> > at least they will start with a unicode environment, as expected |
26 |
> >> > anno 2012. |
27 |
> >> |
28 |
> >> As I had pointed out before [1], changing from POSIX to an en_US |
29 |
> >> locale will have undesirable side effects, like commas as thousands |
30 |
> >> separators in numbers (because of LC_NUMERIC). Also the defaults of |
31 |
> >> en_US for LC_MEASUREMENT and LC_PAPER are only useful in the U.S. |
32 |
> >> |
33 |
> >> So if we change the default (but I still don't see the need), we |
34 |
> >> should go for a less intrusive setting like: |
35 |
> >> |
36 |
> >> LANG="POSIX" |
37 |
> >> LC_CTYPE="en_US.utf8" |
38 |
> >> |
39 |
> >> Ulrich |
40 |
> >> |
41 |
> > |
42 |
> > You're concerned about the commas breaking things? Given that you |
43 |
> > usually need to specifically ask for them (i.e., printf ' flag), |
44 |
> > and that kind of output is usually going to be for human |
45 |
> > consumption only that seems unlikely. If anything does rely upon |
46 |
> > the format, can't tolerate different locales, and fails to specify |
47 |
> > LC_NUMERIC then it's broken anyway. |
48 |
> > |
49 |
> > LC_MONETARY / LC_MEASUREMENT as en_US are probably slightly more |
50 |
> > annoying defaults for some people. What do users of other distros |
51 |
> > think? Is this really a serious problem for anyone? |
52 |
> > |
53 |
> > LC_CTYPE=en_US.utf8 would be a bare minimum. The important bit is |
54 |
> > getting utf8 by default. I can live with LANG=POSIX. |
55 |
> > -- |
56 |
> > Dan Douglas |
57 |
> |
58 |
> How about the below? |
59 |
> |
60 |
> LANG=en_GB.utf8 |
61 |
> LC_COLLATE=C |
62 |
> LC_CTYPE=en_GB.utf8 |
63 |
> |
64 |
> That will give us A4 paper size and the metric system. If LC_NUMERIC |
65 |
> is really a problem, we can set it to something more desirable. |
66 |
|
67 |
LC_NUMERIC=pl_PL.utf8 |
68 |
|
69 |
-- |
70 |
Best regards, |
71 |
Michał Górny |