JEP proposed to target JDK 18: 400: UTF-8 by Default
raffaello.giulietti at gmail.com
Wed Aug 18 19:48:59 UTC 2021
this JEP and its implementation have been discussed in March  and in
July , resp., on the core-libs-dev mailing list (subscribing to that
list is open to anybody).
On 2021-08-18 21:01, Simon Nash wrote:
> 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.
> 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
>> 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
>> locales, and configurations.
>> Feedback on this proposal from JDK Project Committers and Reviewers 
>> 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
>>  I’ll target this JEP to JDK 18.
>> - Mark
>>  https://openjdk.java.net/census#jdk
>>  https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html
More information about the jdk-dev