<html><body><div dir="ltr"><div style="">
</div><div style=""><div>
<div dir="ltr">While we are at it, is Locale.ROOT character types guaranteed to only touch ASCII for case conversion, or could it use latin1 ranges, anyway? (Especially if we think compact strings). How about unassigned or illegal Code units?</div><div dir="ltr"><br></div><div dir="ltr">Gruss</div><div dir="ltr">Bernd</div><div id="ms-outlook-mobile-signature"><div style="direction:ltr">-- </div><div style="direction:ltr">http://bernd.eckenfels.net</div></div>
</div>
<div> </div><hr style="display:inline-block;width:98%" tabindex="-1"><div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif"><b>Von:</b> core-libs-dev <core-libs-dev-retn@openjdk.org> im Auftrag von Archie Cobbs <archie.cobbs@gmail.com><br><b>Gesendet:</b> Mittwoch, April 12, 2023 12:33 AM<br><b>An:</b> Glavo <zjx001202@gmail.com><br><b>Cc:</b> Remi Forax <forax@univ-mlv.fr>; core-libs-dev <core-libs-dev@openjdk.org><br><b>Betreff:</b> Re: Draft: Deprecate toLowerCase()/toUpperCase() and provide locale insensitive alternative<div> </div></font></div><div dir="ltr"><div dir="ltr">On Tue, Apr 11, 2023 at 4:52 PM Glavo <<a href="mailto:zjx001202@gmail.com" style="">zjx001202@gmail.com</a>> wrote:</div><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex"><div>i'm not sure that the methods lowercase() and uppercase() are a good addition.</div><div>Their names are too close to toLowerCase/toUpperCase thus too easy to misuse ones for the others.</div></blockquote></blockquote> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex"><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"><span style="font-family: arial, sans-serif; color: rgb(0, 0, 0);"><font size="2">I'm fine with users having to write toLowerCase(Locale.ROOT) or toUpperCase(Locale.Root) because this is already what we teach.</font></span></blockquote><div><span style="font-family: arial, helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0);"><br></span></div><div>This is the current situation, but I don't think it is good.<span style="font-family: arial, helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0);"><br></span></div><div><br></div><div>This idiom forces users to import Locale even in locale-insensitive scenarios. </div></div></blockquote><div><br></div>Possible compromise? How about toUpper() and toLower()?</div><div class="gmail_quote"><br></div><div class="gmail_quote">This would be consistent with the trend whereby newer replacement names tend to be less verbose (e.g., Enumeration.hasMoreElements() -> Iterator.hasNext()), while also being different enough that people shouldn't mistake them for something that already exists, and will understand that they must mean something new.<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">-Archie<br></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Archie L. Cobbs<br></div></div>
</div></div></body></html>