• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • Subject: Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness
  • From: Ken Thomases <email@hidden>
  • Date: Wed, 18 Jun 2008 16:02:57 -0500

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[Canonical/ Compatibility]Mapping.


The result was that [NSString UTF8String] returns "precomposed" version

That's not quite accurate. Any given string will be in precomposed or decomposed form (or it might not be normalized to either form, and have a mix). Whatever form that string is in, -UTF8String will maintain it. So, -UTF8String doesn't necessarily return "precomposed" form, it just so happens that the string you got was already in precomposed form.



, while the one used in the FCP was "decomposed".

The low-level file-system APIs on Mac OS X use what Apple calls "file- system representation", which is mostly decomposed (NFD) with some specific exceptions. So, any time you obtain a file name from the file-system -- by enumerating a directory or from an NSOpenPanel, for example -- it's likely to be mostly decomposed. This is true even if the name originally used to create the file was passed in precomposed form.


If you want the string in a specific normalization form for some reason, you need to transform it using the above methods. Don't rely on "file-system representation" being in any particular form. You can compare strings without regard for normalization form using one of the -compare:... methods and _not_ specifying NSLiteralSearch. Note that isEqual: and isEqualToString: _do_ specify NSLiteralSearch (or the equivalent) and so can report NO for two strings which display identically.

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


  • Follow-Ups:
    • Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness
      • From: JongAm Park <email@hidden>
References: 
 >[Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness (From: JongAm Park <email@hidden>)
 >Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness (From: Ken Thomases <email@hidden>)
 >Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness (From: JongAm Park <email@hidden>)

  • Prev by Date: Re: NSKeyedArchiver finishEncoding takes forever
  • Next by Date: Re: [Q] UTF-8, stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding, weirdness
  • Previous by thread: Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness
  • Next by thread: Re: [Q] UTF-8 stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding weirdness
  • Index(es):
    • Date
    • Thread