http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/CLJ-945 Clojure <p>When the first unicode code point of a string is supplementary (i.e. requires two 16-bit Java chars to represent in UTF-16), and that first code point is changed by converting it to upper case, clojure.string/capitalize gives the wrong answer.</p> all CLJ-945

clojure.string/capitalize can give wrong result if first char is supplementary

Defect Minor Closed Declined Unassigned Andy Fingerhut Mon, 5 Mar 2012 11:33:02 -0600 Fri, 1 Mar 2013 09:43:19 -0600 Fri, 1 Mar 2013 09:43:19 -0600 Release 1.2 Release 1.3 Release 1.4 Release 1.5 0 1 <p>Isn't this a Java bug?</p> <p>If using UTF-16 to encode Unicode strings, and making every UTF-16 code unit (i.e. Java char) individually indexable as a separate entity in strings, is such a bad design choice that you consider it a bug, then yes, this is a Java bug (and a bug in all the other systems that use UTF-16 in this way).</p> <p>clojure.string/capitalize isn't using some Java capitalization method that has a bug, though. By calling (.toUpperCase (subs s 0 1)) it is not giving enough information to .toUpperCase for <em>any</em> implementation, Java or otherwise, to do the job correctly. It is analogous to calling toupper on the least significant 4 bits of the ASCII encoding of a letter and expecting it to return the correct answer.</p> Approval Not Approved Global Rank Patch Code and Test