LO Pootle

l10n
#1

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é