Re: IB localization question
Re: IB localization question
- Subject: Re: IB localization question
- From: "Rick C." <email@hidden>
- Date: Fri, 01 Jul 2011 15:34:35 +0800
Thanks again for the replies I'm continuing to look into this...
On Jun 30, 2011, at 7:33 PM, Christiaan Hofman wrote:
>
> On Jun 30, 2011, at 13:15, Torsten Curdt wrote:
>
>> I stay away from maintaining multiple NIBs and use this
>>
>> https://github.com/tcurdt/localizer
>>
>> - (void) viewDidLoad
>> {
>> [[TCLocalizer localizer] localizeView:self.view];
>> }
>>
>> ...and everything else is happening in the strings files.
>>
>> cheers,
>> Torsten
>
> Sometimes this kind of approach works. I use my own variation in one of my apps. I also have a script phase (only run for Release, because it's relatively slow) that automatically generates .strings files for the XIBs using ibtool.
>
> However this approach does not take care of localization dependent UI layout, which you still have to do yourself if it's needed, in code. So wether this kind of approach is useful for you depends very much on how complex and localization dependent this layout is.
>
> That said, I agree that maintaining multiple NIBs is a real big hassle, also as the tools for localization often cannot be dependent on (Apple's own recommendation AppleGlot for instance was broken in 10.6, and is still not fixed). So if it's feasible to write some code to fix localization dependent layout, which you only do once, that will save you a lot of work and pain in the long run.
>
> Christiaan
>
> _______________________________________________
> 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
_______________________________________________
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