• 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
Question on STRINGS_FILE_OUTPUT_ENCODING
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Question on STRINGS_FILE_OUTPUT_ENCODING


  • Subject: Question on STRINGS_FILE_OUTPUT_ENCODING
  • From: Ulf Dunkel <email@hidden>
  • Date: Tue, 09 Nov 2010 08:35:28 +0100
  • Organization: invers Software

Introduced in Xcode 3.1, we now have the new Strings files output encoding option, which can be set to either "UTF-8", "UTF-16" (default), or "binary".

I appreciate that Apple wants to make apps smaller (which might have been one reason why they also introduced the Interface Builder NIB Postprocessor option "Strip NIB Files" and other stuff).

Why is the STRINGS_FILE_OUTPUT_ENCODING set to UTF-16 by default?

I cannot find any useful reason for artificially blowing up all .strings files. You can code every Unicode character in UTF-8, by the way.

---Ulf Dunkel
---invers Software
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Question on STRINGS_FILE_OUTPUT_ENCODING
      • From: Joar Wingfors <email@hidden>
    • Re: Question on STRINGS_FILE_OUTPUT_ENCODING
      • From: Ricky Sharp <email@hidden>
  • Prev by Date: Localizing the Display name of non-app bundles?
  • Next by Date: Embedding private Framework
  • Previous by thread: Localizing the Display name of non-app bundles?
  • Next by thread: Re: Question on STRINGS_FILE_OUTPUT_ENCODING
  • Index(es):
    • Date
    • Thread