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


Hi,

Von: Aron Xu


I've tried xliff2po to convert documentation file to po, and it
produces a po file with no header, but many duplicate msgids. We are
lacking tools like msgmerge, msgfmt for xliff/sdf translation files,
which significantly increases the hardness of managing them.

Well, converting po to xliff to work on xliff and then convert back
to po is quite stupid. You do not get the advanteges of the more
feature-rich xliff file format (as you are still restricted to
the po capabilities) but lose the tooling support that you know
from po.

XLIFF is only usefull if it is your primary file format for handling
translations. Tools similar to msgmerge are available. Most of translate 
toolkit tools process xliff files the same way as they do with po.

So - for our current workflow (where unfortunately sdf will stay for
a while, as "internal" file format) it does not really matter if you
use po or xliff - it's more or less a matter of taste. 

I'd prefere xliff. given the fact, that we process the files with
translate toolkit in our build environment anyway, it should be easy
to leave the joice to the language team and have the build enviroment
work with either xliff or po.

regards,

André

-- 
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.