StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMaintaining different localized versions of interface NIB files
text
Body
copied!<p>I'm learning the basics steps to internationalize an app and I have a question about localizing interface NIB files... I've seen that in Xcode you can click on a AppViewController.xib interface file and click on the <em>+</em> in the Localization section of the inspector window to add another language along with the default English one (I add Italian for example)... This allows me to translate the interface in Italian... but then how do you maintain future evolution of the App? If you need to add a button, for example, you have to add it <em>by hand</em> to all the localized versions of your interface NIB file? Documentation says also</p> <blockquote> <p>Objects in a nib file typically have connections between them that should not be broken. Make sure you lock all connections before handing your nibs off to translation. For information on how to lock down your nib file, see “Localization” in Interface Builder User Guide.</p> </blockquote> <p>Can you explain me this concept? I've seen the Localization Locking section within the inspector which allows you to lock <em>Properties</em>, <em>Localizable Properties</em> or <em>Un-localizable Properties</em>, but I don't understand very well what it does.</p> <p>So, to sum up a bit, I'd like you to suggest me what is the workflow to design localized versions of your interface and maintain the multiple NIB files when the interface evolves.</p> <p>EDIT: any idea and/or link that can help me?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload