Changes between Version 6 and Version 7 of CharsetSupport

Timestamp:

04/05/10 19:57:41 (15 years ago)

Author:

ehuelsmann

Comment:

Refer to tickets

CharsetSupport

@@ -14 +14 @@
 ABCL inherits its character storage from Java: 16-bit values for characters in the Basic Multilingual Plane (BMP), 32-bit values for Supplemental characters. See the article on [http://java.sun.com/developer/technicalArticles/Intl/Supplementary/ Supplementary characters in the Java platform] for an in-depth coverage of the subject, including considerations for supporting programs.
 
-''ISSUE'': currently, ABCL assumes every 16-bit value to be a full character, thereby effectively ignoring supplemental characters
+''ISSUE'': currently, ABCL assumes every 16-bit value to be a full character, thereby effectively ignoring supplemental characters (this relates to ticket #65)
 
-''ISSUE'': The values of the BMP range from 0x0 to 0xFFFF, excluding 0xD800 to 0xDFFF; there's no check on the validity of of character values when creating them
+''ISSUE'': The values of the BMP range from 0x0 to 0xFFFF, excluding 0xD800 to 0xDFFF; there's no check on the validity of of character values when creating them (this is now ticket #92)
 
 Even though ABCL can represent all Unicode characters, supporting it (as in providing its operations such as case conversion and case insensitive string matching) is a different matter.