This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients Arfrever, berker.peksag, lemburg, loewis, python-dev, serhiy.storchaka, vstinner
Date 2014-10-02.09:44:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <61405148.2CY2nBiCRg@raxxla>
On 02.10.2014 11:13, Serhiy Storchaka wrote:
> Serhiy Storchaka added the comment:
>> Test failed due to mismatch between glibc and X11 locale.alias (issue20087).
>> In X11 locale.alias ca_ES is mapped to ca_ES.ISO8859-1, and in glibc 2.19
>> it is mapped to ca_ES.ISO8859-15. ca_ES@valencia exists only in glibc
>> SUPPORTED file and was added in the last commit (due to mismatch with
>> ca_ES).
> Hmm, no, both aliases are from glibc SUPPORTED file:
> ca_ES.UTF-8 UTF-8
> ca_ES ISO-8859-1
> ca_ES@euro ISO-8859-15
> ca_ES.UTF-8@valencia UTF-8
> ca_ES@valencia ISO-8859-15

See the comment in
"The point of having
% a separate locale is only for PO translations, which have a lot of social
% support and are very appreciated by the Valencian-speaking community."

Since it's a new locale, they simply used the Latin-1 version with Euro
symbol to start with, which is a good move. Most of Europe is stuck
with having ISO-8859-1 as default, which does not include the Euro
symbol. Then again: most Unix installations use UTF-8 nowadays anyway.
Date User Action Args
2014-10-02 09:44:40lemburgsetrecipients: + lemburg, loewis, vstinner, Arfrever, python-dev, berker.peksag, serhiy.storchaka
2014-10-02 09:44:40lemburglinkissue20079 messages
2014-10-02 09:44:40lemburgcreate