On Sep 23, 2009, at 6:28 PM, Alexander Henket wrote:
> 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. Right. A basic need is that the localizer be able to take true ownership of the localization, from translation to interface adjustment. Anything less is going to lead quickly to out of date and/ or poorly aligned translations, as we simply don't have the bandwidth to manage localizations on this side of things. Using iLocalize to prepare releases isn't viable because we need to have the localized files - whatever those files may be - in source control, not just appearing at the last minute in the distribution bundle. -Evan > > 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
