On 31 Aug 2008, at 6:26 PM, Mauro Mazzieri wrote: >> The latest version of AppleGlot (v3.4) certainly works on Leopard. >> ADViewer doesn't, but the files can be edited with any text editor. I >> use Xcode myself. > > Translating with a text editor is not comparable at all to translating > using a localization tool.
This is more a personal preference. I like to be able to be able to edit text files rather than having to deal with opaque data blobs in some private format. For example, when a bug in ibtool or nibtool messes up the database I can go in and fixed that (I actually have done that). > >> Because of the problems I'm still having with iLocalize, and >> because I >> don't know it, I would personally prefer if you would use either >> Localization Suite or AppleGlot. The advantage of Localization Suite >> is that you can import existing localizations, so you don't need to >> start from scratch. Another advantage of Localization Suite is that >> it >> separates the work for the developer and the translator. The >> interface >> for the translator is pretty intuitive. > > I don't think that the fact you don't know iLocalize can be a valid > motivation to prevent contributors using it; once translations are > created, they can be edited using any software. Not really. You can't move a localization from one system to another, you basically need to start over from scratch. The fact is that if there's a problem, I won't be able to help. Moreover, I'm not able to asses whether iLocalize does the right thing. And I did have problems with localizations produced by iLocalize. > > I completely disagree with the statement that Localization Suite > interface is pretty intuitive. Note that I'm talking about Localizer only. I agree that Localization Manager is not very intuitive. But the point is that a translator needs to use only Localizer. > Actually, is the worst documented > software I ever saw. The disk image came with two applications, > Localization Manager and Localizer. On the website there is no > documentation. Localization Manager has no help. Localizer has a short > and outdated help; it only says to open a .loc file, with no mention > of how to create it. With iLocalize, for comparison, I can simply > import the application bundle and export the file to be committed, > doing both AppleGlot and ADviewer work in one step. The fact that it has no help is indeed not very nice, but that's just because it's a beta, for which the Help has not yet been written. The thing about Localization Suite is that the translator only needs to do the translation step using Localizer. The actual creation and application of .loc files is left to the developer. Moreover I can choose which files can be localized and which are not, I don't know whether iLocalize can do that (I know AppleGlot can't). > > However, as there is a requirement for Tiger compatibility, I finally > found a way to make the translation Tiger-compatible (I have to > install Xcode 2.5, downloading from ADC website). > I'll made the commit once the localization is Tiger-compatible. > > -- > Mauro Mazzieri Please use Xcode 3 and ibtool for localization. If it's done right it should be compatible with Tiger. I don't know how iLocalize works with the various versions, but I know AppleGlot and Localization Suite work properly Toger compatible. nibtool has many bugs that have been fixed (now) in ibtool. And using 2.x and 3.x tools together actually leads to various problems I'd like to avoid in the future. Christiaan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Skim-app-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/skim-app-users
