<i18n dev> RFR: 8277398: javac does not accept encoding name COMPAT [v2]
Alan Bateman
alanb at openjdk.java.net
Wed Nov 24 08:51:10 UTC 2021
On Wed, 24 Nov 2021 04:08:43 GMT, Ichiroh Takiguchi <itakiguchi at openjdk.org> wrote:
>> ncoding name COMPAT was defined for operating system encoding by JEP-400.
>> https://openjdk.java.net/jeps/400
>> But java does not accept "-encoding COMPAT".
>
> Ichiroh Takiguchi has updated the pull request incrementally with one additional commit since the last revision:
>
> 8277398: javac does not accept encoding name COMPAT
I see this PR has been re-purposed to add "COMPAT" as a charset that can be specified to Charset.forName. I don't think we should do that. "COMPAT" is a special value for the file.encoding property, it's not meant to be in the charset tables as proposed here. The system property "native.encoding" was added in Java 17 as a standard way to obtain the encoding, you can pass its value to Charset.forName. I think we need a clear summary as to what the issue is, is -J-Dfile.encoding=COMPAT working or not?
-------------
PR: https://git.openjdk.java.net/jdk/pull/6475
More information about the i18n-dev
mailing list