Re: IB localization question
Re: IB localization question
- Subject: Re: IB localization question
- From: Ulf Dunkel <email@hidden>
- Date: Mon, 04 Jul 2011 09:35:47 +0200
- Organization: invers Software & DSD.net
Hi Rick.
Am 01.07.2011 13:11, schrieb Rick C.:
I don't know what you think about this:
http://developer.casgrain.com/?p=94
The approach seems to be nice at face value, but will run into the same
issues as all other NIB layout methods which do not keep in mind that
localized strings can be much longer. So you will also have to adjust
the base language (English in most cases) NIB layout every now and then.
Of course the generating of localized NIBs only in the build phase seems
to be handy, but I don't see any advantage over having localized AND
properly layouted NIBs at any time in your sources.
And I do NOT agree with what the linked page claims: "Translators want
strings files, not nib files". That's pretty nonsense, because real
translators aka localizers don't simply translate but localize apps. So
they need to check their localized app in run-time, without asking the
developer all the time for new versions.
This is what convinced me of the way how iLocalize implements
localization and testing.
IF (a very huge "if") Apple would finally implement any way to
auto-adjust the size of text-containing UI objects, maybe from a given
instructive way which tells the system in which direction objects may
grow (or shrink!), the developer.casgrain.com method would be perfect.
Until then, it is NOT.
Localization still needs these things:
- a well-thought and designed base language NIB layout
- an easy way to localize and update localizations
- an easy way to test localized layouts in run-time
- glossary handling to keep localizations in sync
---Ulf Dunkel
_______________________________________________
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