Re: [Sugar-devel] Open translation tools (was: Potential volunteer offering technical writing)
Hi Christoph, > I briefly looked at OmegaT and Okapi: the first one looks quite > interesting > but I'm less sure what to do with the latter. So if you have a moment > could > you briefly lay out the workflow in which these different tools would > be > used within the context of a 1-day or multi-day translation sprint > with a > handful of participants? > The idea behind those translation tools is to make the work of the human translator easier, by automatizing tecnical tasks (such as converting, transcoding files) which are (or should be) left outside of the scope of a language specialist and by simplifying the dealing with formatting rules of tagged or structured documents. Rainbow may be used to create so called "Translation Kits" from a set of original documents, which are converted and packaged according to the conventions of the translation tool of choice: * OmegaT: in this case, a "OmegaT Project" is created with all its files and directory structure in place. * Any PO editor: a simple package where translatable files are extracted into PO files. The Rainbow Translation Kits are fully configurable. For instance, you can set up separately the language (say "en-us" for the source documents and "de-at" or "es-uy" for the target documents) and encoding settings (say "us-ascii" for the source documents and "utf-16" for the target documents) of the source and target documents. Then, the individual documents are assigned to a translator (and later, to a reviewer), either online or offline. After being translated & reviewed, the documents produced are post-processed using the function "Translation Kit Post-Processing", wich reverts back the formatting of the original documents and the directory structure, while applying the locale and encoding settings as set up previously. To sum it up, the pre- and post-processing is where Rainbow may be useful, whereas the translation and reviewing may be carried out with the help of dedicated tools (say OmegaT, Poedit, Pottle, GTranslator, etc.). The list of available conversion filters provided by Rainbow (and more generally by the OKAPI framework) contributes to broaden the use cases of the usual localization tools, whose core formats are highly specialized and suitable for translation related tasks (bilingual documents used internally by those tools, as translation memories, glossaries, bilingual alignments). > Thanks, > Christoph > > -- > Christoph Derndorfer > > editor, OLPC News [www.olpcnews.com] > volunteer, OLPC (Austria) [www.olpc.at] > > e-mail: christ...@derndorfer.eu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Open translation tools (was: Potential volunteer offering technical writing)
On Wed, Oct 5, 2011 at 12:19 PM, samy boutayeb wrote: > Following the discussions "Potential volunteer offering technical > writing" about the choice of an adequate translation tool suitable for a > a project like a manual, please see: > > "Open Translation Tools" > http://en.flossmanuals.net/open-translation-tools/ > > Among the tools mentioned in this review, my best candidates would be a > combination of: > > 1/ OmegaT ( http://www.omegat.org/ ), which manages a fair list of > document formats and can benefit from a translation memory (which helps > reuse old texts from previous translations), and a glossary, both useful > fonctions in a collaborative project. The documents are parsed and > segmented properly, providing a simple list of text strings, which may > be translated either internally or with an online tool. > > and > 2/ Pottle, as a well known web based online tool compatible with a > collaborative project management. > > 3/ Additionally, the Okapi framework ( http://okapi.opentag.com/ ) may > provide useful resources such as file filter, allowing to manage a fair > list of file formats. > > See: http://www.opentag.com/okapi/wiki/index.php?title=Filters for a > full list of supported formats > Hi Samy, thanks a lot for compiling this list of recommendations. I briefly looked at OmegaT and Okapi: the first one looks quite interesting but I'm less sure what to do with the latter. So if you have a moment could you briefly lay out the workflow in which these different tools would be used within the context of a 1-day or multi-day translation sprint with a handful of participants? Thanks, Christoph -- Christoph Derndorfer editor, OLPC News [www.olpcnews.com] volunteer, OLPC (Austria) [www.olpc.at] e-mail: christ...@derndorfer.eu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Open translation tools (was: Potential volunteer offering technical writing)
Following the discussions "Potential volunteer offering technical writing" about the choice of an adequate translation tool suitable for a a project like a manual, please see: "Open Translation Tools" http://en.flossmanuals.net/open-translation-tools/ Among the tools mentioned in this review, my best candidates would be a combination of: 1/ OmegaT ( http://www.omegat.org/ ), which manages a fair list of document formats and can benefit from a translation memory (which helps reuse old texts from previous translations), and a glossary, both useful fonctions in a collaborative project. The documents are parsed and segmented properly, providing a simple list of text strings, which may be translated either internally or with an online tool. and 2/ Pottle, as a well known web based online tool compatible with a collaborative project management. 3/ Additionally, the Okapi framework ( http://okapi.opentag.com/ ) may provide useful resources such as file filter, allowing to manage a fair list of file formats. See: http://www.opentag.com/okapi/wiki/index.php?title=Filters for a full list of supported formats ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
