FROM : Erik Buck
DATE : Sun Apr 08 21:54:42 2007
> Well, the problem is localization. Unless you're fluent in pretty
> much every language, you're going to need to send your nib files to
> someone else to translate them into Spanish, French, Japanese, etc.,
> and when they send the modified versions back to you, they sometimes
> end up lacking the .svn directory inside, which causes Subversion to
> go into a *fit*.
>
> If there's any way around this, I'd love to know about it as well.
The old solution for using CVS with nibs in the Nextstep days was to
have scripts which tared and untarred the nib as it was checked in
or out. That way CVS treated the entire nib directory as a single
binary file.
DATE : Sun Apr 08 21:54:42 2007
> Well, the problem is localization. Unless you're fluent in pretty
> much every language, you're going to need to send your nib files to
> someone else to translate them into Spanish, French, Japanese, etc.,
> and when they send the modified versions back to you, they sometimes
> end up lacking the .svn directory inside, which causes Subversion to
> go into a *fit*.
>
> If there's any way around this, I'd love to know about it as well.
The old solution for using CVS with nibs in the Nextstep days was to
have scripts which tared and untarred the nib as it was checked in
or out. That way CVS treated the entire nib directory as a single
binary file.






Cocoa mail archive

