[Python-ideas] RFC: PEP 540 version 3 (Add a new UTF-8 mode)
Oleg Broytman
phd at phdru.name
Thu Jan 12 11:10:01 EST 2017
More information about the Python-ideas mailing list
Thu Jan 12 11:10:01 EST 2017
- Previous message (by thread): [Python-ideas] RFC: PEP 540 version 3 (Add a new UTF-8 mode)
- Next message (by thread): [Python-ideas] RFC: PEP 540 version 3 (Add a new UTF-8 mode)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jan 12, 2017 at 04:25:56PM +0100, Victor Stinner <victor.stinner at gmail.com> wrote: > 2017-01-12 9:45 GMT+01:00 INADA Naoki <songofacandy at gmail.com>: > > When using en_US.UTF-8 as fallback, pleas override only LC_CTYPE, > > instead of LC_ALL. > > As I described in other thread, LC_COLLATE may cause unintentional performance > > regression and behavior changes. > > Does it work to use a locale with encoding A for LC_CTYPE and a locale > with encoding B for LC_MESSAGES (and others)? Is there a risk of It does when B is a subset of A (ascii and koi8; ascii and utf8, e.g.) > mojibake? Or do we expect that the POSIX locale speaks ASCII, and so > it should work for use UTF-8 for LC_CTYPE since UTF-8 is able to > decode messages encoded ASCII? That works for me: $ echo $LC_CTYPE ru_RU.UTF-8 $ echo $LC_COLLATE ru_RU.UTF-8 $ echo $LANG C $ date Thu Jan 12 19:06:13 MSK 2017 > Victor Oleg. -- Oleg Broytman http://phdru.name/ phd at phdru.name Programmers don't die, they just GOSUB without RETURN.
- Previous message (by thread): [Python-ideas] RFC: PEP 540 version 3 (Add a new UTF-8 mode)
- Next message (by thread): [Python-ideas] RFC: PEP 540 version 3 (Add a new UTF-8 mode)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list