[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #25233] unable to create an NSString from the Unicode character 0xF
|
From: |
Richard Frith-Macdonald |
|
Subject: |
[bug #25233] unable to create an NSString from the Unicode character 0xFFFF |
|
Date: |
Sat, 03 Jan 2009 07:30:35 +0000 |
|
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1 |
Update of bug #25233 (project gnustep):
Status: None => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
0xFFFF is a noncharacter (see
http://www.unicode.org/versions/Unicode5.0.0/ch16.pdf section 7).
You can use it in your code, but must not attempt to transfer it to other
code (such as an NSString) as that's specifically disallowed by the unicode
standard.
You should probably raise a bug report with Apple if their implementation
treats a noncharacter as a character, as this is not in conformance with the
unicode standard.
In practical terms, it's a very very good thing for NSString to disallow
noncharacters as this ensures that bad input is detected early on and that
your code does not output bad data or pass bad data to other libraries with
unpredictable results.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25233>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/