Comments on: ibtool scripts on Google Code

By: bdunagan

bdunagan — Wed, 22 Dec 2010 05:38:53 +0000

@ben Good point. I guess my scripts assume the directory structure is already set up. I’ll add the mkdir ruby call on my next pass at the scripts.

By: ben

ben — Wed, 08 Dec 2010 19:12:24 +0000

Seems that the scripts won’t create the *.lproj folders, and my version of ibtool will die if the target folder doesn’t exist. Could be added to the scripts I suppose but a simple mkdir works for me.

By: fill the void – ibtool “Missing object” Confusion

fill the void – ibtool “Missing object” Confusion — Sat, 27 Mar 2010 23:38:35 +0000

[...] week, I ran one of my ibtool ruby scripts to localize an app. During the process, it generated the following [...]

By: anu

anu — Fri, 13 Nov 2009 05:13:10 +0000

works!!! seems like my new English nib had been messed up for some reason. the right translations got pulled out and the resizing of elements were retained as well.

By: bdunagan

bdunagan — Wed, 11 Nov 2009 20:00:58 +0000

@anu, I just tried what you describe on a new project, and it worked for me. There could be a punctuation error in your Danish.strings file that’s preventing the problem string from being read. I have a ruby script in my Google Code repository to validate .strings files better than ibtool.

Also, try generating .strings files for both the old and new Danish.xibs and diff’ing them, just to make sure that string is the only string failing. I do that before every commit.

If you’re still having issues, feel free to email me the problem files, and I’ll take a look at them.

By: anu

anu — Wed, 11 Nov 2009 18:58:52 +0000

I modified the string of the label in the new English.xib. The strings file generated seems to have the same key such as “508.title”, only the value for that key has changed. If I feed in the old English.xib, the updated English.xib with the new string for that textfield, the old Danish.xib, the newly generated Danish.xib seems to have all the other translations in place except this modified string which comes up in English( the way it was specified in the new English.xib).

The ibtool for some reason does not seem to be pulling out the correct the translation from the intermediate Danish.strings file for that label alone.

By: bdunagan

bdunagan — Fri, 06 Nov 2009 03:18:18 +0000

[Man, I'm a slacker replying to comments. Sorry.] The key is the element’s ID. Replacing an element with an identical copy still removes the original element, along with its ID, and adds the new element, with a new ID. You can modify the existing element, like moving or resizing it, and ibtool will still work fine. And, you can always see the element IDs by generating a strings file for the XIB. Not sure if this is your problem, @anu.

By: anu

anu — Sat, 24 Oct 2009 00:35:34 +0000

Does incremental localization work only when adding new UI elements or when you modify existing ones? I have a xib that was translated earlier. I now changed the label of an element in my interface and am using ibtool to update the new translation for the text in all other language xibs. it does not seem to work.

On running this ibtool command, it seems to preserve the element sizing for the translated xibs and display the correct translations for the un-modified elements, but the modified string label is displayed in English in all the other xibs.

By: bdunagan

bdunagan — Fri, 02 Oct 2009 03:56:18 +0000

Absolutely. There are many cases where you should use NSLocalizedString(), like dynamic localized text such as a status, in addition to localizing UI elements. In fact, you can localize a UI element in a XIB, then populate its value with NSLocalizedString() when necessary.

By: andy

andy — Fri, 02 Oct 2009 00:07:12 +0000

Is it possible to both have a localized .xib file as well as a Localizable.strings file that NSLocalizedString can use? The reason I ask is that my app has text not associated with UI elements.