JC Helary ha scritto: > I wrote this mail with OmegaT in mind since it seems to be used more > and more within the OOo community to translate OOo produced documents > -and not so much imported documents from the MS world. > > The Italian documentation translation group (I think) seems to be > using OmegaT and thanks to their work we have discovered glitches in > the OOo tags support. I think the reason is that before, when OmegaT > was used to translate mainly texts imported from MS, OOo filtering > was very conservative and would produce a very small quantity of OOo > tags, that were all properly handled by OmegaT. Now that people use > OOo to create documents (and it is especially true not for the OOo > documentation process), authors are free to use the full creativity > options of OOo and the generated documents are now much more complex.
Indeed, I confirm that we, as Italian localization / documentation translation group have started a big translation project which will cover all the OOoAuthors Guides. Now it's underway the first group of introduction guides. We have about 30 persons involved. This project has been planned for months with a deep research of available translation memory tools that could integrate easily with OOo. OmegaT has been chosen and it's used since it has a few good points, it's free software, it's multi-platform (written in java), it's small (people can download it and use it straight out), it support OOo native file format, it provides an glossary service, and it support standard Memory Translation formats. We are building the first generation of Translation Memories ENG-ITA for OOo which will form the base for future works, OOo localization and translations. This will reduce translation time recycling the previous work and permit an easy update of already translated documents. This is necessary considering that original documents are often subject to updates and revision by other English speaking people. This approach is useful in order to maintain and grant uniformity of translation stiles and terminology between different documents and the OOo software itself. Our group has also defined a stile guide for Italian works. As work proceeds, some problems arise, for this reason, my project co-leader Alessandro Cattalan has consulted OmegaT lists and similar in order to point out bugs and eventually sort out a solution. I don't know if in this list there are people that use OmegaT, but it would be useful to have their feedback, maybe on other lists. For all the rest, I would like to share this experience, it could be useful also for other translation groups to adopt more professional tools in order to enhance productivity and translation quality. I will keep updated on our progress on the Italian translation side of the guides. Once they will be completed they will be uploaded on OOoAuthor Site. I am also starting an Italian OOo FAQ translation project. In a few months we should have available much more Italian documentation! Regards and Merry Christmas to everyone! Andrea Sanavia PLIO Documentation Italian Native Lang Group
