• 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: CFBundleDevelopmentRegion != "English"?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CFBundleDevelopmentRegion != "English"?


  • Subject: Re: CFBundleDevelopmentRegion != "English"?
  • From: Mailing list subscriptions <email@hidden>
  • Date: Mon, 11 Sep 2006 18:29:44 +0200

El 11/09/2006, a las 16:55, Michael Hecht escribió:

Now, when I try to "Add Localization" to a file, it doesn't seem to do anything. Shouldn't Xcode be consulting this Info.plist key to determine what source file to use for the new localization?

Is this supposed to work?

I have had problems with that button not working and I always use "en" as my development reason. I hadn't previously considered the possibility that the change to the development reason might be the cause. It's always annoyed me a little bit that Apple tells developers to use ISO country codes (ISO 3166, from memory, I could be wrong about that) yet all their templates use the full English names.


As a workaround for the problem you describe I always just create the localization on disk and then drag it in to the Xcode project, adding it to the appropriate target manually.

We should both probably file a bug report.




_______________________________________________ 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
References: 
 >CFBundleDevelopmentRegion != "English"? (From: Michael Hecht <email@hidden>)

  • Prev by Date: Re: Broken 10.2.8 SDK with Xcode 2.4 update?
  • Next by Date: Re: Broken 10.2.8 SDK with Xcode 2.4 update?
  • Previous by thread: CFBundleDevelopmentRegion != "English"?
  • Next by thread: Using source trees
  • Index(es):
    • Date
    • Thread