iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

pep-0538: rephrase UTF-8 locale description (#249)

This commit is contained in:
INADA Naoki 2017-05-01 15:26:50 +09:00 committed by Nick Coghlan
parent fcda9a2c8c
commit a5d764f268
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pep-0538.txt
View File

@ -19,7 +19,7 @@ Abstract
An ongoing challenge with Python 3 on \*nix systems is the conflict between
needing to use the configured locale encoding by default for consistency with
other locale-aware components in the same process subprocesses,
other locale-aware components in the same process or subprocesses,
and the fact that the standard C locale (as defined in POSIX:2001) typically
implies a default text encoding of ASCII, which is entirely inadequate for the
development of networked services and client applications in a multilingual
@ -68,7 +68,7 @@ With this change, any \*nix platform that does *not* offer at least one of the
configuration would only be considered a fully supported platform for CPython
3.7+ deployments when either the new ``PYTHONUTF8`` mode defined in PEP 540 is
used, or else a suitable locale other than the default ``C`` locale is
configured explicitly (e.g. `en_AU.UTF-8`, ``zh_CN.gb18030``).
configured explicitly (e.g. ``en_AU.UTF-8``, ``zh_CN.gb18030``).
Redistributors (such as Linux distributions) with a narrower target audience
than the upstream CPython development team may also choose to opt in to this
@ -153,9 +153,9 @@ categories (including ``LC_COLLATE``). It is offered by a number of Linux
distributions (including Debian, Ubuntu, Fedora, Alpine and Android) as an
alternative to the ASCII-based C locale.
Mac OS X and other \*BSD systems have taken a different approach, and instead
of offering a ``C.UTF-8`` locale, instead offer a partial ``UTF-8`` locale that
only defines the ``LC_CTYPE`` category. On such systems, the preferred
Mac OS X and other \*BSD systems have taken a different approach: instead of
offering a ``C.UTF-8`` locale, offer a partial ``UTF-8`` locale that only
defines the ``LC_CTYPE`` category. On such systems, the preferred
environmental locale adjustment is to set ``LC_CTYPE=UTF-8`` rather than to set
``LC_ALL`` or ``LANG``. [17_]