From dc175c590291ce530ba8a06232f9889affc2df2b Mon Sep 17 00:00:00 2001 From: Nick Coghlan Date: Fri, 5 May 2017 00:59:53 +1000 Subject: [PATCH] PEP 538: Minor JVM/CLR related clarifications --- pep-0538.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pep-0538.txt b/pep-0538.txt index f87cc99c6..4d2364022 100644 --- a/pep-0538.txt +++ b/pep-0538.txt @@ -180,7 +180,7 @@ solution: arise between CPython and other locale-aware components running in the same process and in subprocesses. This approach aims to make CPython behave less like a locale-aware application, and more like locale-independent language - runtimes like the JVM, .NET CLR, Go, Node.js, and Rust + runtimes like those for Go, Node.js (V8), and Rust * this PEP proposes to override the legacy C locale with a more recently defined locale that uses UTF-8 as its default text encoding. This means that the text encoding override will apply not only to CPython, but also to any @@ -545,7 +545,7 @@ assumes UTF-8 by default (a behaviour inherited from the V8 JavaScript engine) and requires custom build settings to indicate it should use the system locale settings for locale-aware operations. Both the JVM and the .NET CLR use UTF-16-LE as their primary encoding for passing text between applications -and the underlying platform. +and the application runtime (i.e. the JVM/CLR, not the host operating system). The challenge for CPython has been the fact that in addition to being used for network service development, it is also extensively used as an embedded