JEP proposed to target JDK 18: 400: UTF-8 by Default

[Simon Nash]

How should someone who is not a JDK Project Committer or Reviewer provide input to this proposal? The principle is good but I am concerned about the 
compatibility implications.

Simon

On 18/08/2021 17:20, mark.reinhold at oracle.com wrote:
> The following JEP is proposed to target JDK 18:
>
>    400: UTF-8 by Default
>         https://openjdk.java.net/jeps/400
>
>    Summary: Specify UTF-8 as the default charset of the standard Java
>    APIs.  With this change, APIs that depend upon the default charset
>    will behave consistently across all implementations, operating systems,
>    locales, and configurations.
>
> Feedback on this proposal from JDK Project Committers and Reviewers [1]
> is more than welcome, as are reasoned objections.  If no such objections
> are raised by 23:59 UTC on Wednesday, 25 August, or if they’re raised
> and then satisfactorily answered, then per the JEP 2.0 process proposal
> [2] I’ll target this JEP to JDK 18.
>
> - Mark
>
>
> [1] https://openjdk.java.net/census#jdk
> [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html
>