• 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
Localization.strings in UTF16 vs UTF8
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Localization.strings in UTF16 vs UTF8


  • Subject: Localization.strings in UTF16 vs UTF8
  • From: Torsten Curdt <email@hidden>
  • Date: Tue, 15 Dec 2009 16:47:53 +0100

Anyone know of any reasonable explanation why for Cocoa localization
files need to be in UTF16?

 http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPInternational/Articles/StringsFiles.html#//apple_ref/doc/uid/20000005-SW1

Is this just to make using SCMs painful? Or what is wrong with using UTF-8?

Anyone filed a radar for this yet? At least I didn't find anything over at

 http://www.openradar.appspot.com

cheers
--
Torsten
_______________________________________________

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: Localization.strings in UTF16 vs UTF8
      • From: Joar Wingfors <email@hidden>
  • Prev by Date: Re: Core Data Save As Binary Error
  • Next by Date: Re: pls explain rotated iPhone coordinates to me
  • Previous by thread: Help Debugging NSPredicateEditor reloadCriteria Exception
  • Next by thread: Re: Localization.strings in UTF16 vs UTF8
  • Index(es):
    • Date
    • Thread