RFR: 8275007: Java fails to start with null charset if LC_ALL is set to certain locales
Alan Bateman
alanb at openjdk.java.net
Mon Nov 8 09:47:39 UTC 2021
On Sun, 7 Nov 2021 13:03:10 GMT, Ichiroh Takiguchi <itakiguchi at openjdk.org> wrote:
> If this issue is not a part of JEP-400, I think UTF_8 may not be only solution for sun/nio/fs/Util.java.
> Please explain why UTF_8 is better than ISO_8859_1.
Just to add to Naoto's comment. When the JDK starts in unusual/unsupported configurations then it needs a default for the stdout/stderr print streams, for encoding/decoding files paths in java.io, and for encoding/decoding files paths in the java.nio.file implementation. It's important that the latter two are the same, having one be UTF-8 and the other be 8859-1 won't work.
There may be an argument that the JDK should emit a warning at startup.
-------------
PR: https://git.openjdk.java.net/jdk/pull/6282
More information about the core-libs-dev
mailing list