> No. I already answered this question.
Reread a couple of times and don't see that answer. I can only guess it conflicts with your workflow somehow, but I don't see how. It appears as if you are unwilling to make iLocalize the final part in the release chain. 1. Develop in Xcode 2. Build 3. Update English in iLocalize, and send build to localizers 4. Import iLocalize exports from localizer 5. Build total release from iLocalize, and release to public That's about it. So unless you intend to include the results from localizers in your Xcode project, I really don't get it. But then even if that's it I don't get why you effectively kill localization in favor of something Apple might do in the distant future. I'd say that's throwing out people of your development process that are not always easy to find. For now as said I'm calling it quits until you send out your plans. Regards Alexander Op 22 sep 2009, om 21:48 heeft Peter Hosey het volgende geschreven: > > On Sep 22, 2009, at 11:22:18, Alexander Henket wrote: >> Xibs are fine and iLocalize supports them just fine, but you >> currently, to my best of knowledge, cannot use them runtime. > > Right. > >> This means going down the xib road is going down the "cannot test my >> localization anymore" road. > > Unless we turn off nib stripping, which happens in the localization > build configuration I have locally. > >> What is your truly compelling reason not to flip the switch? A few >> kilobytes? > > No. I already answered this question. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
