1 |
On Thu, 02 Aug 2012 11:21:40 -0700 |
2 |
Diego Elio Pettenò <flameeyes@×××××××××.eu> wrote: |
3 |
|
4 |
> On 01/08/2012 23:42, Fabian Groffen wrote: |
5 |
> > Honestly, if some asian person has whatever charset that I often |
6 |
> > find in spam messages, but is not UTF-8, are you then going to tell |
7 |
> > that person to switch to UTF-8 to get those python packages |
8 |
> > emerged? I hope not. |
9 |
> |
10 |
> Tell that to the Python team I guess. My tinderbox _has_ utf8 locales |
11 |
> available, but doesn't set in by default -> Python stuff fails to |
12 |
> build or test -> not going to be fixed with "change your locale" |
13 |
> reasoning. |
14 |
|
15 |
not that it is hard to set LC_ALL=sth before running the failing |
16 |
command, or make the pm do it... we already fix regexp bugs with other |
17 |
locales (or workaround them by setting LC_ALL=C), it falls under the |
18 |
same category. |
19 |
you just need to teach people, and maybe mandate an utf8 locale to be |
20 |
present; the same way they do not consider estonian alphabet ordering |
21 |
'broken' they would not consider not having an utf8 locale 'broken', |
22 |
esp. when said utf8 is far from being optimal in terms of size for asian |
23 |
languages. |
24 |
|
25 |
A. |