[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Translation verification: using diffs
From:       Freek de Kruijf <f.de.kruijf () gmail ! com>
Date:       2013-05-29 15:14:11
Message-ID: 27398031.NgI4gkIQxU () eik123 ! beelaertsict ! nl
[Download RAW message or body]

Op woensdag 29 mei 2013 16:31:58 schreef Chusslove Illich:
> > I'm looking for ideas for effective translation verification. If you have
> > some comments, it would be great!

I use a different approach. I do a daily svn update. When I get a new version 
of a po file from a translator of which I know that this new po file could be 
based upon an older po file, I simply rename the po file to 
<original_name>_<name_translator>.po and copy that file in the folder where it 
belongs to.
After that I start lokalize and click right on that file name to get the 
translations in that file in the TM. After that I open the via svn updated po 
file and go to a fuzzy or untranslated message. Normally in the subwindow TM I 
get the translation of the translator and <Ctrl>+1 copies that translation in 
the translation subwindow. Then I can check the translation and approve it or 
make corrections. After that I go to the next fuzzy or untranslated message. 
The subwindow Alternative Translations shows the changes made in the English 
text, but when the English text has changed between the version got from the 
translator and the via svn updated version, those differences are shown in the 
TM subwindow also, if they are not too drastic.

The only disadvantage is that I don't see changes in previously translated 
unchanged English messages. So I ask them to do that only when they review a 
completely translated po file and to do that within a few days, so I can use 
diff to see the differences.

-- 
fr.gr.

Freek de Kruijf

[prev in list] [next in list] [prev in thread] [next in thread]