Comments on: The Evils of java.lang.String.toUpperCase http://www.brosinski.com/stephan/2008/02/09/the-evils-of-javalangstringtouppercase/ Mon, 08 Jun 2009 10:13:18 +0000 hourly 1 http://wordpress.org/?v=3.0.5 By: Thomas Jacob http://www.brosinski.com/stephan/2008/02/09/the-evils-of-javalangstringtouppercase/comment-page-1/#comment-19 Thomas Jacob Sat, 17 May 2008 10:00:00 +0000 http://brosinski.com/stephan/2008/02/09/the-evils-of-javalangstringtouppercase/#comment-19 The whole thing is even worse. length() is not the number of characters, but the number of 16-bit-numbers using the UTF-16 encoding. For most cases, this is the same, but traditional chinese characters sometimes require two UTF-16 numbers. The same holds for charAt etc. You always get the UTF-16 encoding. The other day, there was a long discussion on how to introduce the characters above 64k. How to extend Java. 7 approaches have been dropped due to various reasons. Finally, they chose this one. http://java.sun.com/developer/technicalArticles/Intl/Supplementary/ If you want to have the correct length of a string, use methods like codePointCount(). The whole thing is even worse. length() is not the number of characters, but the number of 16-bit-numbers using the UTF-16 encoding. For most cases, this is the same, but traditional chinese characters sometimes require two UTF-16 numbers. The same holds for charAt etc. You always get the UTF-16 encoding.

The other day, there was a long discussion on how to introduce the characters above 64k. How to extend Java. 7 approaches have been dropped due to various reasons. Finally, they chose this one.

http://java.sun.com/developer/technicalArticles/Intl/Supplementary/

If you want to have the correct length of a string, use methods like codePointCount().

]]>