• 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 14:01:47 -0700

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.

Scott

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.";


Should I be doing this in a more Xcode-savvy way? I notice that the default project template doesn't include these keys, but as a result apps built with the default project template don't show any version information from the Finder's Get Info dialog.

Daniel

On May 25, 2005, at 1:06 PM, Scott Tooker wrote:


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:
sweater.com


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

  • Prev by Date: Re: 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: Re: 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