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: Daniel Jalkut <email@hidden>
- Date: Wed, 25 May 2005 14:18:05 -0700
On May 25, 2005, at 2:01 PM, Scott Tooker wrote: The current direction is to not localize these keys in the InfoPlist.strings file, instead just provide non-localized keys in the Info.plist. Otherwise (aside from using the Apple generic versioning support), what you are doing looks fine.
On May 25, 2005, at 1:56 PM, Daniel Jalkut wrote: The keys I'm localizing are CFBundleShortVersionString and CFBundleGetInfoString. Since the text consists of localizable words as well as the version number, I'm trying to do something like this:
CFBundleShortVersionString = "MyApp version ${APPLICATION_VERSION}"; CFBundleGetInfoString = "MyApp version ${APPLICATION_VERSION}, Copyright 2005 Red Sweater Software.";
Interesting - is this non-localization direction formally recommended somewhere? The "Property List Key Reference" documentation still endorses localizing at least the get info string.
Anyway, I'll probably switch to this strategy since it will definitely make the build process easier.
Thanks for the insights, 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