#1220 Unable to use XLIFF file as TM

[Marc Riera]

According to the documentation, reference TMs are not limited to TMX, but can also be in any of the bilingual formats supported for translation (such as PO or XLIFF). However, the new built-in XLIFF filter apparently cannot find my TM.

I have created a minimal fileset to reproduce the issue. Create a project from English to Catalan, copy "Test1.xlf" to "source" and "Test1_tm.xlf" to "tm". No matches are shown at all.

If the built-in XLIFF filter is disabled and the Okapi XLIFF filter is used, matches are detected correctly.

Using OmegaT 6.0.0 on Arch Linux x64 with Java 11 (OpenJDK).

Thanks in advance,

Marc Riera

[Hiroshi Miura]

@marcriera
Could you try to use OmegaT 6.1 weekly version?
It has deprecated old (monolingual) XLIFF filter you tried, and provide full bi-lingual XLIFF filter.

[Marc Riera]

Sorry if I was not clear, I ran the original test with OmegaT 6.0.0 with the new XLIFF filter (the one based on StaX). I have the legacy filter disabled.

I just ran the same test with the latest weekly build (6.1.0 Beta) and the same happens. I am attaching the log in case there is anything useful. Thanks!

[Hiroshi Miura]

An old XLIFF filter in OmegaT 6.0.0 is monolingual filter. It is because XLIFF is not supported.
A StaX filter has a feature to process bilingual XLIFF file, but it does not claimed as bilingual filter in IFilter API.
A new XLIFF1 filter in OmegaT 6.1.0, which delivered from StaX filter, also does not claimed as bilingual filter in IFilter API.

It seems bug in new XLIFF1 filter driver.
@t_cordonnier Any comment?

[Hiroshi Miura]

A fix pushed
https://github.com/omegat-org/omegat/pull/804