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 14:07:50 -0700
Thank you for the additional information.
Interestingly I found a similar method in NSFileManager, fileSystemRepresentationWithPath.
So, is there any document on which file system uses which representation?
Also, is there any reason why a program, like the FCP, prefers the decomposed string over precomposed string?
Will there be a problem, if a program expect decomposed string and its client program sends precomposed one to the server?
(Well.. it depends on implementation of the programs.. )
Sure looks like it, based on the data. EC 9E 90 is U+C790, "�"; E1
84 8C E1 85 A1 is U+110C "ᄌ", U+1161 "ᅡ", which is the decomposed
version of the same thing. -[NSString fileSystemRepresentation] may
also be of use here, given that this is really a file path -- the
normalization form used for file names is dictated by the file system.
--Chris Nebel
AppleScript Engineering
_______________________________________________
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