bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: nobody
Subject: [bug #4624] NSString does not handle codepoints greater than 65535
Date: Fri, 17 Oct 2003 02:14:04 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030908 Debian/1.4-4

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

Changes by: Richard Frith-Macdonald <address@hidden>
Date: Fri 10/17/03 at 06:14 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
Fixed in CVS ... thanks



=================== BUG #4624: FULL BUG SNAPSHOT ===================


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

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.



Follow-up Comments
*******************

-------------------------------------------------------
Date: Fri 10/17/03 at 06:14         By: CaS
Fixed in CVS ... thanks


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/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]