<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Sorry Glavo, I cannot support this plan as it appears to be trying to rush #1 and #4 into the current release. <br></blockquote><div><br></div><div>This is not true, I only hope that the first step - two new API methods - can become a part of Java 21.</div><div><br></div><div>The fourth step must be completed after the first and third steps are completed, or perhaps never.<br></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"> As I said in the other mail, it's very disruptive and requires broader consideration and thinking about other locale sensitive APIs.<br></blockquote><div><br></div><div>I don't understand why the first step is disruptive. It just adds two new methods, replacing toLowerCase(ROOT) and toUpperCase(ROOT).</div><div><br></div><div>I've detailed the reasons for introducing a new API earlier, and I hope you'll take a look at it:<br></div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><a href="https://mail.openjdk.org/pipermail/core-libs-dev/2023-April/104118.html" target="_blank">https://mail.openjdk.org/pipermail/core-libs-dev/2023-April/104118.html</a></div></blockquote><div><br></div><div>Best regards,<br></div><div>Glavo</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 15, 2023 at 5:08 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">
<div>
On 15/04/2023 08:50, Glavo wrote:<br>
<blockquote type="cite">
<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>
<br>
</div>
</blockquote>
<br>
Sorry Glavo, I cannot support this plan as it appears to be trying
to rush #1 and #4 into the current release. As I said in the other
mail, it's very disruptive and requires broader consideration and
thinking about other locale sensitive APIs.<br>
<br>
#3 is the only part of this list that make sense right now.<br>
<br>
-Alan<br>
<br>
<br>
</div>
</blockquote></div>