JC Helary wrote on 03/03/2006 04:11 PM:
> Thanks Samual, it is much clearer now :)
My pleasure... I only hope Henry agrees with my summary.
> Now I am not a Trados client so I don't really understand all the
> issues discussed here, but let's say we have a bilingual file parser
> (the XLIFF thing Martin is working on :) It seems to me we'd need
> only a(n external) filter (a la OLT) to have PO/Trados/etc support
> within the XLIFF support ? Am I wrong ?
That went completely over my head, so I have no idea.
Just to restate my position, my original comments in these thread did
not imply that we *should* create such a feature in OmT (Henry indicated
the possibility thereof quite voluntarily). My original threads in
various mailing lists concerned attempts to support Trados uncleaned
files using OmegaT's and OOo's *existing* features. Along the way I
discovered that OOo's Find/Replace feature is a dismal failure AFAICS
and that it would not be possible to tweak my existing methods to
utilise OOo only.
I'm all in favour of an OmegaT suite of tools which include the main
program and several extra programs that does various things in a useful
manner. If the extra programs can be plugins, great. If they can be
written in a language which presumably the user has installed already
(ie Java and OOo macro), then great. Remember, not all translators are