Jean-Christophe Helary wrote
We need a localization format (PO, XLIFF, key=value, anything) that
matches the localization data SUN provides us with (TMX).
I have read this 20 times in 2 days, and I dissagree. We need to use TM,
but we can perfectly well generate our own TM with the format that we have.
If we are using PO, we need TM that comes from PO. The format of the
data is the format that it will be used in PO. We can generate this with
any tool (KBabel, poedit), and use it with the same tool.
We can do the same thing with XLIFF. We create internal TM from XLIFF
files, and we use it in new XLIFF files. The format might be different
from the one in PO, and different form the TM provided by SUN, but it
can be used perfectly well, because it goes back to the same place that
it was taken from.
We have been doing this for years with PO, and it worked... and it also
works with XLIFF.
When we upgrade to new versions of OOo, we do not mandatorily need to
use TM, we can do direct transfer of information from the old version of
the file to the new version, based on ID matching, as we have been doing
for years. TM supports this for strings that are new (but equal to an
old string) and strings that have changed ID, but this is a very small
minority.
To have the TM from SUN is very nice, but it is not necessary, as we
have survived for many years without it, using internal TM. Maybe I am
wrong, but I believe that there is no technical advantage to using it,
as far as I understand.
At this point I believe that the best PO editor is KBabel, but it runs
only on Linux. It does quite good TM matching, enough for the needs of
OOo translation.
Javier
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
