Re: [Q] UTF-8, stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding, weirdness

On Wed, Jun 18, 2008 at 5:07 PM, JongAm Park <[EMAIL PROTECTED]> wrote: > 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? "Filesyst

Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness

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 That'

Re: [Q] UTF-8, stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding, weirdness

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 ov

Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness

On Jun 18, 2008, at 3:47 PM, JongAm Park wrote: Thank you very much for the information. You're welcome. I even didn't think about the normalization. Wow.. it is quite complicated. I tried the 4 methods, -precomposedStringWith[Canonical/ Compatibility]Mapping and -decomposedStringWith[Can

Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness

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 UTF8S

Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness

On Jun 18, 2008, at 12:24 PM, 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 s

Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness

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. Sp

[Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness

Hello, all. I found a very interesting and strange behaviour of the NSString:stringByAddingPercentEscapedUsingEncoding. I got a UTF-8 string from a Final Cut Pro project file, which is exported as an XML. There is a video clip named "자연", which means "Nature" in Korean. And its pathurl is f