Translating Mozilla with Portable Object Templates
Thursday March 11th, 2004
Caio Begotti (caio1982) writes: "Everyone who has some contact with great Open Source projects knows that localization and internationalization are really important and even essential in places like France or Italy. The Mozilla project have a nice L10N team but the tool that everybody actually uses isn't so helpful for collaborating over translations. This article explains how you can use .pot files to translate Mozilla products or extensions. Let's retire Mozilla Translator; using .pot files from the GNU/Gettext library is much easier, IMHO.
"The original article was written by me for the Brazilian community Mozilla Brasil but was accepted by the Translate project too as an introduction to the theme. I'm not a real developer, just a enthusiast and amateur translator, so any comments are very appreciated, but sorry about the flame baits or rants."
#1 pot is not a good replacement
Friday March 12th, 2004 8:18 AM
You are replying to this message
i just created a mozillazine account, just so i can response to this annoying post.
first of all, that text file assumes everyone uses linux and has python installed may i remind you, that even among mozilla users, most people use Win32. it says, "If you want to translate some portion of the suite, say the ChatZilla, you need to download the latest Mozilla Translator release (dated from 2002), install the Java SDK, study how it works and then start to translate it." and if you want to use that other translator, you have to install python (which is not installed by default on windows, may i remind you), run the script to convert the dtd files to pot files, learn how to translate with VI (assuming Kbabel doesn't have a port to win32 [when will these kde guys grow up and stop adding K to every application they make?] and that you've never used VI before, at least for translating) and then start working on the translation. what's the difference? (and VI, IMHO, is for people who like pain. Notepad may be weaker, but it's sure easier to understand where do i write there.)
he goes on to say, "But, you can't easily merge two translations packs into MT what means is really hard to more than one person to translate something. At least is that what we from Mozilla Brasil have noticed." maybe you don't know MT enough. i worked with other people on the same translation with MT quite comfortably. you can easily export components of mozilla, and send them to the project coordinator, who would just as easily import them into the central work.
ok, so other projects use other methods. but other projects don't use dtd files. marely converting to and from the pot format will increase the amount of work, compared to what is needed with MT.
the text explains how to get the file from CVS. where's the FTP site? am i a developer? (hint: no, i'm not) why do i have to start looking for a cvs program? why do i have to access cvs? software should always be released as files to be installed, and not in this form. i feel that some of the open source community still doesn't understand that normal people don't care how cool their programs are. normal people want to double click and start working (and see my note about notepad above).
indeed, mozillatranslator has not been updated in some time now, and it's about time someone (with more knowledge than i have in java) will pick it up and add some new features. but MT is still, IMO, one of the best solutions that exist today, and certainly the easiest to use, for translating mozilla.
tsahi asher, hebrew L10n.