[bug #4624] NSString does not handle codepoints greater than 65535

[nobody]

=================== BUG #4624: FULL BUG SNAPSHOT ===================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4624&group_id=99

Submitted by: minusbat                Project: GNUstep                      
Submitted on: Mon 08/04/2003 at 21:03
Category:  Base/Foundation            Severity:  5 - Major                  
Bug Group:  Bug                       Resolution:  None                     
Assigned to:  None                    Status:  Open                         

Summary:  NSString does not handle codepoints greater than 65535

Original Submission:  Under OSX an NSString handles codepoints greater than 16 
bits
by converting them into paired surrogates - i.e. the unichars
stored in the string appear to be UTF-16. This does not work
under GNUstep.

Example - initialise a string with the UTF8 hex bytes of
0xc2, 0xa3, 0xf0, 0x90, 0x80, 0x81, 0xc2, 0xa3, 0x00
which is the encoding for three characters - 0xa3, 0x10001, 0xa3

Doing this under OSX yields a string of length '4'. Printing the 4
unichars in the string gives: 0xa3, 0xd800, 0xdc01, 0xa3 which is
the correct UTF-16 format for the string.

Under GNUstep the method stringWithUTF8String: return nil
when presented with the same daata. Taking out the over 16 bit
enccoding sequence results in the correct unichars.




No Followups Have Been Posted


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4624&group_id=99

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/