Re: About Mandriva page
Mario Blättermann <[email protected]>
| Newsgroups | gmane.linux.mandrake.cooker.internationalization |
|---|---|
| Message-ID | <1256768244.4942.52.camel@localhost> |
Am Mittwoch, den 28.10.2009, 23:15 +0200 schrieb Marek Laane: > I've to admit I'm absolutely not familiar with "GNOME's way". But anyway, > how can translator know something is changed if translation file is not > touched? Does it mean you have to do double work to monitor both template and > translation file? > And as for statistics (or, as you say, "status pages"), neither Mandriva nor > KDE don't display any changes in template only in translation file (well, > provided there is translation file; if not, then, of course, changes in > templates are displayed). The status tracker for GNOME works as follows: 1. Any person with write access to the Git commits a changed file. 2. The status tracker is watching any files which are referenced either in POTFILES.in or in help/Makefile.am (for docs) 3. The changes will be merged into an existing translation from Git or into the template, if no translation exists for a certain language. 4. The result is displayed and downloadable as plain text. 5. Translators can edit the file, upload it for review and finally commit the new one. All of these steps doesn't change the real content in Git, it just happens in a »scratchpad«. Due to the permanent watch to the source code changes, the status tracker can provide the merged po files immediately, and we don't have to think about: »Do we already have an up-to-date file, or don't we...?«. And it is impossible that your changed, but not yet committed file becomes too old. Even the uploaded files will be merged with the current pot template, if there any change was happened in the meantime in the repository. Additionally, the uploaded files will be tested, whether they are in UTF-8 or contain any errors, e.g. not matching variables, such as %s in msgid and %d in msgstr, missing mnemonics etc. Furtherly, it prevents people with SVN access from problems with old local copies, untracked changes etc. You do your work outside of the SVN. Once your file is ready to commit, just type »svn up«, drag the file into the folder, and »svn ci«. That's all. Have a look at the environment [1], you'll see how it works. Cheers, Mario [1] http://l10n.gnome.org/languages/et/gnome-2-30/ui/