I am not a translator but I think that working from XLIFF documents would make the translation a bit easier.
XLIFF makes it possible to follow the translation process, at least partially. For example, if the translation tools implement the "Change Tracking Extension" module defined in the latest XLIFF specification (v2.1), you can track the status of elements. The "property" attribute can indicate a new level: for example, the translator who changed the "state" (XLIFF attribute) of the translation: initial, translated, reviewed, final. [1] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff [2] http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.pdf Unfortunately, translators would need to use translation tools based on the latest XLIFF specification (v2) to take advantage of this. However, someone will eventually be able to use the tools at their disposal. Garulfo <garu...@azules.eu> writes: > Does anybody has a guide about "how to set up a documentation > translation project with git ?". > One requirement will probably to define how propositions are > officially validated. Does it requires Joaquín to learn how to use git > ? Can we just work by sending files (or patches) to Joaquín who will > update with a single git command ? -- Best regards, Kevin Vigouroux ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
