There are two developers disagreeing with you, and there's me agreeing with you.
Apple provides ibtool to extract and insert the localized strings that you manipulate outside of the xibs/nibs. This allows one to use glossaries, automatic translation and all kinds of other nifty stuff that Apple never thought of including in Xcode. Not even Apple uses Xcode for localization. Well sort of. I'm told that a limited number of agencies is allowed directly into their source control. But very likely Apple takes care of the UI, i.e. making the localization fit. This would mean that all those agencies are allowed to touch are the Localizable.strings, *.plist and the HTML files. In a small developer group like Growl has, I'm sure doing all UI for every localization is out of scope, so I'm inclined to think, the localizers would need to adjust UI too after localization. All in all that means testing that too. And that sort of rules out xibs, unless the gameplan involves a quick way to get xib adjustments into nibs. But as said: waiting for the game plan. If I had a clue what could work, I'd suggest it, but at present I have no idea how to pull it off on both ends. Regards Alexander Op 23 sep 2009, om 21:58 heeft Evan Schoenberg, M.D. het volgende geschreven: > > Alexander, > > Only final releases should have nonlocalizable nibs. Their presence in > any other build, including beta builds, is a bug. > > Cheers, > Evan > > > > On Sep 23, 2009, at 12:10 PM, Alexander Henket <[email protected]> > wrote: > >> >> >> I'll wait for the game plan. I'm hoping it'll be along the lines of a >> build with uncompiled nibs so I can test too, using the power of >> iLocalize on my end. If your game plan involves xibs I'm counting on >> both ends of the process being taken into account. Both you as >> developers, and us as localizers. >> >> Regards, >> >> Alexander >> >> Op 23 sep 2009, om 17:19 heeft Peter Hosey het volgende geschreven: >> >>> >>> On Sep 23, 2009, at 06:56:57, Alexander Henket wrote: >>>>>> Xibs are fine and iLocalize supports them just fine, but you >>>>>> currently, to my best of knowledge, cannot use them runtime. This >>>>>> means going down the xib road is going down the "cannot test my >>>>>> localization anymore" road. >>>>>> >>>>>> What is your truly compelling reason not to flip the switch? A >>>>>> few >>>>>> kilobytes? >>>>> >>>>> No. I already answered this question. >>>> >>>> Reread a couple of times and don't see that answer. >>> >>> It's an indirect answer. Here it is again: >>> >>>> Actually, using xibs lets us diff and (sometimes) merge them. Nibs >>>> are not diffable or mergeable at all. Thus, xibs are a huge win for >>>> those of us who are developing. >>> >>> We're using xibs and compiling to nibs. That's not up for debate. >>> >>> What the switch controls is whether the nib compiler strips the >>> nibs. >>> An unstripped nib is editable, so it's what you need. We will do >>> that >>> in a localization build configuration with which we'll put out >>> localization builds (most likely, the last beta for each release). >>> >>> At this point, I want to get 1.2 out this month, so we'll finish >>> setting up the localization-build system for a future release, >>> hopefully as soon as 1.2.1. >>> >>> >>>> >> >> >>> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en -~----------~----~----~----~------~----~------~--~---
