Thanks Alex and Peter. Your link to Wil's blog post is exactly what I
was looking for.
Best regards,
Tobias Jordan.
On Nov 2, 2009, at 2:08 PM, Peter Ilberg wrote:
The other day, Wil Shipley shared his solution to the localization
problem:
http://wilshipley.com/blog/2009/10/pimp-my-code-part-17-lost-in.html
-- Peter
On Nov 2, 2009, at 12:50 PM, Alexander Spohr wrote:
Am 02.11.2009 um 11:55 schrieb Tobias Jordan:
The problem I am currently having is that when updating the
interface I have to a) make my changes to every localization (en,
ge, fr, jp, etc.) or b) re-create all of the localizations which
isn't that easy to handle since I am not the one translating
everything.
That is how you do it for localized nibs.
Both ways are really time-consuming and I was wondering if there's
a way to define some placeholders for strings and other resources
such as images or sth. like that.
Alternatively you can use just one nib and replace the values using
NSLocalizedString(). But you have to watch out for the lengths and
sizes in different languages.
What's the most fastest and efficient way?
It depends on what you goal is.
a & b) are best if you want to have nice sized buttons in all
languages
NSLocalizedString is easier to implement and to translate but the
final look might get gruesome.
atze
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
