Federico Beffa skribis:
> From my point of view it would be good to include en_US.UTF-8 by
> default for two reasons: (i) we already are at 7 (4+3) packages
> requiring an UTF-8 locale and, I guess, that this number is doomed to
> increase in the following years. (ii) This is another small step i
John Darrington skribis:
> The C locale is the canonical locale. UTF-8 is not the only characater
> encoding in
> the world. English is not the only language in the world, and US English is
> not
> the only dialect of English.
You’re right, of course. For the packages discussed, what matters
John Darrington writes:
> (i) we already are at 7 (4+3) packages requiring an UTF-8 locale
>
> Then that is a bug which should be filed against those pacakges.
I just discovered the problem with the "scipy ecosystem" packages
today and intended to fix them. But, before submitting changes, I w
On Tue, Feb 10, 2015 at 06:36:58PM +0100, Federico Beffa wrote:
On Tue, Feb 10, 2015 at 6:13 PM, Ludovic Courtès wrote:
> Federico Beffa skribis:
>
>> Guile-ncurses was fixed by adding a new phase to generate the
>> "en_US.UTF-8" locale during the generation of the packag
On Tue, Feb 10, 2015 at 6:13 PM, Ludovic Courtès wrote:
> Federico Beffa skribis:
>
>> Guile-ncurses was fixed by adding a new phase to generate the
>> "en_US.UTF-8" locale during the generation of the package, but wouldn't
>> it be better to keep the "en_US.UTF-8" locale? That appears to be the
Federico Beffa skribis:
> Guile-ncurses was fixed by adding a new phase to generate the
> "en_US.UTF-8" locale during the generation of the package, but wouldn't
> it be better to keep the "en_US.UTF-8" locale? That appears to be the
> default used by most packages.
That’s an open question. The
