On 2009 Dec 21, at 01:27, Symadept wrote: > Now pass these files to Localization > team and they shall simply copy paste the other version of the string in RHS > of the corresponding files.
Well, of course there are tools for this. I use and recommend Max Seelemann's Localization Suite, and just learned that it has now been open-sourced. This is great news, since a localization tool is something that you'll often want to tweak. For example, I'd love to make it scriptable from the command line so I can add it to my Build script. http://www.loc-suite.org/ More good news is that Max is that it looks like Max is actively working on it. > If you go with multiple nib files for various locale, UI maintainance will > become hectic. We discussed the pros and cons of this recently -- read this... http://lists.apple.com/archives/Cocoa-dev/2009/Dec/msg00363.html (*) On 2009 Dec 20, at 12:30, Ricky Sharp wrote: > In getting quotes from many localization companies, I've found that some have > different processes. For example, one company would prefer if I just provide > .string files. During their QA process, they'll then run the app and look at > everything in context. Since any app can by definition do an infinite number of tricks (and errors), the "test coverage" they get when they "run the app" is going to be 85% at best before they get tired of mousing around and ship it back to you. So, I would recommend giving this localizer good comments. I try to make my strings files read like API documentation, with comments defining the "contract" stating how each string can be used (and re-used). > How have others tackled localization? The dearth of replies should tell you something :) Here's my answer: A combination of techniques. Localization is always costly, iterative, compromised, and imperfect. Some have used each of the techniques you propose, and others have rejected them. They may well be optimum for your situation. Judging from your post, you are a good tech writer and thus might want to rely heavily on .strings comments as I do, and choose localizers which do the same. Jerry (*) I can rarely get Apple's List Search to find threads, even if I'm looking at an email I sent and copy keywords exactly. But then I found it in a Google search!!!! Bug has been filed -- again -- 7490709. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
