Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness
Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness
- Subject: Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness
- From: JongAm Park <email@hidden>
- Date: Wed, 18 Jun 2008 13:47:07 -0700
Thank you very much for the information.
I even didn't think about the normalization. Wow.. it is quite complicated.
I tried the 4 methods,
-precomposedStringWith*[Canonical/Compatibility]*Mapping and
-decomposedStringWith*[Canonical/Compatibility]*Mapping.
The result was that [NSString UTF8String] returns "precomposed" version,
while the one used in the FCP was "decomposed".
Thank you again.
Ken Thomases wrote:
On Jun 18, 2008, at 1:49 PM, JongAm Park wrote:
Can anyone tell me why the two different data source are displayed as
same "자연", while what it contains are different?
I haven't looked into the specific character sequences in-depth, but I
suspect the difference is in Normalization Forms. Specifically, form
C vs. D.
http://unicode.org/reports/tr15/
The idea is that the same character can be obtained from a single code
point or by several combining code points.
In Cocoa, see -precomposedStringWithCanonicalMapping and
-decomposedStringWithCanonicalMapping.
Cheers,
Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden