• 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: Localization strategies?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Localization strategies?


  • Subject: Re: Localization strategies?
  • From: Uli Kusterer <email@hidden>
  • Date: Tue, 22 Dec 2009 02:18:06 +0100

On 20.12.2009, at 21:30, Ricky Sharp wrote:
> Thus, I'm wondering if it would ultimately be worth it to externalize all strings from my nibs and just put everything in my single .strings file.  This will clearly involve me adding tons of IBOutlet ivars just so that at runtime I can set their text with NSLocalizedString APIs.

 One approach to avoid the whole IBOutlet excess would be to create subclasses of the standard view classes which, when they are loaded, use their contents/title as the key and pass it to NSLocalizedString(). That way, your NIBs only contain keys, and the .strings files can hold the actual strings, including comments.

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Localization strategies?
      • From: Andy Lee <email@hidden>
References: 
 >Localization strategies? (From: Ricky Sharp <email@hidden>)

  • Prev by Date: Re: Please if some one knows
  • Next by Date: Re: Version number objects
  • Previous by thread: Re: Localization strategies?
  • Next by thread: Re: Localization strategies?
  • Index(es):
    • Date
    • Thread