Re: Best way to process each existing localization of strings file?
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 13:06:03 -0700
Okay, since you don't want the version number to change per
localization, you can just remove the version number key from any
InfoPlist.strings file (it will be found in the Info.plist file).
If you are getting these InfoPlist.strings file from a template,
plesae file a bug asking that we remove any non-localized keys from
the InfoPlist.strings files in templates.
Scott
On May 25, 2005, at 12:21 PM, Daniel Jalkut wrote:
On May 25, 2005, at 12:09 PM, Scott Tooker wrote:
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).
No - sorry for the confusion. I don't expect the version to be
dependent, but as the version is included in the InfoPlist.strings
file, I need to perform variable substitution on each of the
localized files.
So, I want to iterate through every localized InfoPlist.strings
file, and replace a well-defined tag with an $ENV{MY_VERSION} value.
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