Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi Sophie,

The ODF2XLIFF filters in both translate toolkit and WordForge are broken. They ignore some strings from the source (they do not go into the XLIFF files) in which there is mark-up. They can be used only for plain text without any markup, and even them segmentation is not very good. There are also other problems with them. I-tools does not have enough working tools either.

Our testing shows that the Okapi framework does a good job for the round trip, I don't know about other tools.

This is a very important issue, but not easy to solve. We will be putting some time to fix it, but it will not happen immediately.


Cheers,

Javier





Sophie Gautier wrote:
Hi all,

As promised, I'm going on with the tests concerning the ability to use Pootle in the translation workflow for documentation. As you may know, Pootle is able to handle very large projects now thanks to the great work the team has provided. There is all the tools needed for the translation process, but also you can assign task and objectives to a member or a team.

I've worked on the first chapter of the OOoAuthors guide for beginners. I used WordForge filters [1] to convert the file from .odt (ODF file format) to .xlf (XLIFF file format). Both are standards, so it should be easier to have a good conversion. Several tools manage off line translation for Xliff file format, like WordForge or OmegaT, there may be others I don't know too.

Rimas has kindly uploaded the file on Pootle [2], creating a new project for several languages for the beginning. Currently, en_GB fr hu ko nl oc pt_BR ru zh_CN . Those are the 7 languages for which libo33 project is fully localized plus hu and nl. The issue we meet is that the strings appears as needing review instead of being empty.

If other team wants to give a try, please follow the same process as for the extensions project, post on the mailing list and Rimas (big thanks to him :) will take care of your request.

Please, follow up on the l10n list for the moment, we will settle a more precise workflow once we have solved the issued that may raised and that we are sure most (I know we miss an offline tool currently for Mac translators) of the needs to work quietly and efficiently on the documentation translation.

Thanks for your help in improving the process :)

[1] https://sourceforge.net/projects/wordforge2/
[2] http://translations.documentfoundation.org/projects/doc_test/

Kind regards
Sophie



--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.