<div dir="ltr">Hi Alan,<div><br></div><div>In discussions with others, my thoughts have changed. <br></div><div><br></div><div>I describe the issue in more detail[1] and have a new plan:</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">1. Add new locale insensitive APIs and recommend users to use them in new code.<br><br> I hope this step can be implemented in Java 21.<br><br>2. Add a new system property that allows users to configure the behavior of<br> these two methods.<br><br>3. Gradually clean up the use cases inside JDK.<br><br> Since this involves a dozen modules and hundreds of source files, I need to<br> split them into many PRs, and some of them require CSR. Reviewing them may<br> take a long time, this step will be done slowly in the future.<br><br>4. Deprecate the two methods.<br> <br> This step may take place much later.<br></blockquote><div><br></div><div>I hope to prioritize the first step now, at least introducing a new clean API in Java 21.</div><div>Do you have any opinions on this plan?<br></div><div><br></div><div>Glavo</div><div><br></div><div>[1] <a href="https://mail.openjdk.org/pipermail/core-libs-dev/2023-April/104118.html">https://mail.openjdk.org/pipermail/core-libs-dev/2023-April/104118.html</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 15, 2023 at 3:04 PM Alan Bateman <<a href="mailto:Alan.Bateman@oracle.com">Alan.Bateman@oracle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 13/04/2023 15:58, Glavo wrote:<br>
> :<br>
><br>
> I thought it might be more efficient to discuss after creating a draft PR.<br>
> It seems that it is difficult to attract more experts to participate <br>
> in the<br>
> discussion only on the mailing list. Do you have any suggestions for this?<br>
><br>
<br>
This proposal is not something to be hurried. It could be massively <br>
disruptive change and would need to be looked at in the context of all <br>
APIs that use the default locale. It would also need to be looked at in <br>
the context of new developers starting out and just wanting to get a toy <br>
program working. It might be confusing for new developers to find <br>
themselves using a neutral locale. If a new developer is forced to <br>
choose between Locale.ROOT and Locale.getDefault() during their first <br>
week of coding then it will give a terrible first impression.<br>
<br>
One of your messages lists cleaning up usages in the JDK. Auditing the <br>
usages to identify any cases that should be changed from using the <br>
default locale to Locale.ROOT would be a contribution. So if you have <br>
the energy to do that they it would be useful to start.<br>
<br>
-Alan.<br>
</blockquote></div>