• 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: Unspecified File Encodings in 3.0
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unspecified File Encodings in 3.0


  • Subject: Re: Unspecified File Encodings in 3.0
  • From: "Shawn Erickson" <email@hidden>
  • Date: Mon, 19 Nov 2007 10:50:15 -0800

On Nov 19, 2007 10:40 AM, Nick Nallick <email@hidden> wrote:
> I've recently encountered an odd change in Xcode 3.0 that took me a
> while to track down so I thought I'd share it.
>
> I have a set of localized files which I created from the original
> English versions.  For some reason the original English file was
> marked in Xcode as using MacRoman encoding but the other files in the
> same set didn't have a specific encoding (they reported "no explicit
> file encoding" when I checked).

Ideally you should use UTF-16 encoded files for strings files, at
least that is Apple statement on this type of thing.

<http://developer.apple.com/documentation/MacOSX/Conceptual/BPInternational/Articles/StringsFiles.html>

-Shawn
 _______________________________________________
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: Unspecified File Encodings in 3.0
      • From: Nick Nallick <email@hidden>
References: 
 >Unspecified File Encodings in 3.0 (From: Nick Nallick <email@hidden>)

  • Prev by Date: Unspecified File Encodings in 3.0
  • Next by Date: Re: Unspecified File Encodings in 3.0
  • Previous by thread: Unspecified File Encodings in 3.0
  • Next by thread: Re: Unspecified File Encodings in 3.0
  • Index(es):
    • Date
    • Thread