On Wed, Sep 23, 2009 at 8:56 AM, Alexander Henket <[email protected]> wrote:
> > > > 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. > > Xibs are not some mythical beast that apple is going to implement years from now. They are out *now*. And they really help because they are plain text and not binaries, so you can see the changes in the source code in version control. So a year from now if you were to stop working on Growl, someone else could look to see what changes you made, without having to use a tool like iLocalize at all. Say for instance 10.7 comes out, iLocalize doesn't work, and magically they decide to close shop and not put out another update. We're not stuck, since we know what changes you made. The fact that these are plain text and not binaries should be a no brainer here. You don't need an elegant fancy setup to go editing them, you can just open them in a text editor and find the little bits to change, and even send a diff back. It's going to streamline the process by my understanding of things. So no, it's not about saving just little bits here and there. When an application with xibs are compiled, they become nibs in the app, which can be editable or uneditable, depending on a switch. Uneditable nibs run faster, and what we are going to ship. So if there's a little problem that doesn't show up unless it's a stripped nib, then we won't catch that in a beta. Which nullifies a beta process. This all said, we're not on xibs yet. That's post 1.2. So, like I've asked before, please be patient. We're still working through just plain bugs in the product in the first place, thanks to the beta process. We're not to the point where we can say "here's some editable nibs for you guys!" yet. We only have 2 people working on 1.2, you need to be patient. We're switching to xibs in 1.2.1, and I think that's where I'd like us to formalize a process for localization, fully document it (none of our documentation currently is any good for anything except the implementing the framework stuff, so to make it clear I want very good documentation on this process). We didn't ask you guys to start localizing yet, so I'm not sure why you were trying to localize the betas, other than to just do it right then. We typically give a 2 week period when we're ready for localizations, but even that's been sketchy. Unfortunately that's just how things have been in the past. However, please do not try to localize anything until we ask you to, and we have a plan. I appreciate the energy you're bringing here, but we're not even sure as to how we want to do localizations in the near future, much less the distant future, and I'm tired of you guys having to go through this time and time again without a game plan. The end game for us is that at points before the release, we'll send a message to the localizations list, and provide a window that you guys feel is reasonable. Once that window is hit, we move on to the next step in the release process. You guys should not have to go localize a beta, *period*. At least, that's my take on it. Chris > 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 -~----------~----~----~----~------~----~------~--~---
