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


Le 13/09/2013 15:11, Milos Sramek a écrit :
Hi,

does anybody have experience with translation of LO guides from
https://www.libreoffice.org/get-help/documentation/?

I've  tried to use OmegaT for that, but I've failed, because the xml
code is 'polluted' by numerous useless tags (read below) which makes
using translation software impossible. Perhaps a 'clean up' tool would
help, but I do no know anything like that :(

Yes, unfortunately there is no way to use translation tool currently to
translate those guides and keep them updated. I've made a try with
converting to xliff format but I missed feedback to know if it works
really for all languages.
In the FR project, we translate them without any help of translation
software, we use LO and the glossary.
For information, I've nearly finished to translate the Writer FAQ and
will go on with Calc. It's good mid-time between help files and guides,
requesting less efforts than the later.
https://wiki.documentfoundation.org/Faq

Cheers
Sophie


-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

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.