• 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: Best way to process each existing localization of strings file?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best way to process each existing localization of strings file?


  • Subject: Re: Best way to process each existing localization of strings file?
  • From: Scott Tooker <email@hidden>
  • Date: Wed, 25 May 2005 12:09:53 -0700

Just to be clear, you expect the version number to be dependent on the localization the user is using? I'm curious why you expect this, normally version numbers are non-localized and defined in the Info.plist file (which can support macro expansion of build settings).

Scott

On May 25, 2005, at 12:04 PM, Daniel Jalkut wrote:


I am trying to automate my versioning by defining a version number in a build variable and then using that build variable in all the required files.


I noticed by searching the archives that Xcode's failure to perform variable substitution in InfoPlist.strings files is a known limitation, so I am trying to concoct my own solution for those files.

As it happens, I only have an English localization at the moment, but I'd like this build phase to be robust enough to automatically handle any localized versions I might add in the future.

What's the best and most reliable way for me to iterate over all of the localizations of a given file? Right now I'm trying to perform this variable substitution at the very end, by manipulating the files in the built products directory. Would it be easier to try to hook in at some earlier build phase?

My naive approach is that I'll look in the Resources directory for any directory ending in ".lproj". Is there a better way? Will I miss anything by doing this?

Thanks!
Daniel

_______________________________________________
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


_______________________________________________ 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: Best way to process each existing localization of strings file?
      • From: Daniel Jalkut <email@hidden>
References: 
 >Best way to process each existing localization of strings file? (From: Daniel Jalkut <email@hidden>)

  • Prev by Date: Best way to process each existing localization of strings file?
  • Next by Date: Re: Best way to process each existing localization of strings file?
  • Previous by thread: Best way to process each existing localization of strings file?
  • Next by thread: Re: Best way to process each existing localization of strings file?
  • Index(es):
    • Date
    • Thread