* Betr.: " [tryton-dev] Re: providing translated docs" (Tue, 27 Oct 2009 17:10:36 +0100):
> Here is the way:
> I used index.rst as file example but it must be done for every rst file.
>
> - Create/Update pot file in doc directory:
>
> # txt2po doc/index.rst doc/index.pot -P
>
> - Create the language directory:
>
> # mkdir -p doc/lang
>
> - Create/Update language po file:
>
> # pot2po doc/index.pot doc/lang/index.po -t doc/lang/index.po
>
> - Create/Update the language rst file:
>
> # po2txt doc/lang/index.po doc/lang/index.rst -t doc/index.rst
>
> And so we will add to mercurial:
> doc/*.pot
> doc/*.rst
> doc/lang/*.po
> doc/lang/*.rst
Here are my preliminary testing results:
I What we need from the technical point of view:
- translation by paragraph (to not have to translate word by word)
- display of diffs by words (to be able to see small changes in the original -
e.g. if there is only a small change like a typo or a forgotten comma etc.
it is otherwise very difficult and uncomfortable to detect the change)
- simple handling (complicated procedures will result in unmaintained
translations)
@1) is provided by translation toolkit
@2) here we are facing the difficulty, that only one of the softwares (poedit,
virtaal, kbabel, lokalize) I tested can handle diffs: kbabel. It is not really
a choice since it depends on kde and is superseeded by lokalize.
Basically we need something like
$ wdiff -l index.po.old index.po |less
I tried to work with
$ wdiff index.po.old index.po | sed -e 's/{+#, fuzzy+}/#, fuzzy/' > index.new.po
to get a file working with po editors.
After translation we naturally had to take care to merge back the original src,
or to merge the translated strings into the original likewise.
I think this could be automated enough with scripting to get a reasonably
comfortable procedure.
I also tried with direct translation of csv in spreadsheet (via csv2po), but it
seems much more error prone and complicated.
Anyway any other ideas or experiences are appreciated to get the best handling
for doc translation.
II What we need for the doc handling in the project:
- There are number of small errors in the existing english documentation,
that should be cleaned up *before* translation. I don't know, which could
be the best way to achieve doc review, but personally I dislike to put
it all on Rietveld, because it is too much work for such small, but
multiple changes. Best for me would be some kind of doc team with direct
commit permissions to doc dirs, but I am aware, that modules normally are
in the responsibility of the module creator. So I don't know which way to go
here, but it is kind of pointless (at least for me) to translate docs with
errors.
So looking ahead also here for your input.
Cheers
--
Mathias Behrle
MBSolutions
Gilgenmatten 10 A
D-79114 Freiburg
Tel: +49(761)471023
Fax: +49(761)4770816
http://mbsolutions.selfip.biz
UStIdNr: DE 142009020
PGP/GnuPG key availabable from any keyserver, ID: 0x89BCA161
signature.asc
Description: PGP signature
