Download:
    Test release (2.0.5): Source / Binary
    Development release (2.1.2): Source / Binary

Bugs have been found in the releases 2.x of StaX filters. They also affect DGT-OmegaT 3.4 and 3.5, which will be corrected later. DGT-OmegaT 3.3, which is still using (variant of) StaX filters 1.1 (and does not include OpenXML at all), is not affected.

OpenXML filter: did collapse underlined text

The bug was discovered by Kos Ivantsov. The filter considered "w:u" (underlined) as an empty tag, which cannot contain text. The list of tags which can be empty was wrong. Now corrected.

In any case, please don't forget that OpenXML filter has actually not be widely tested, so it can still contain bugs. The only filters which have been widely used and can be considered as stable are Xliff 1 and SDLXLIFF.

Filter for SDLXLIFF: bug when added note from OmegaT

The SDLXLIFF filter has capacity to convert notes from OmegaT to comments understood by Trados Studio. This feature had a bug in filters 2.0 and 2.1 (but not in 1.x) which resulted in corruption of the generated target file. Now it is corrected in all versions.

[Release 2.1.2 only] Filter for XLIFF 2.0 : support change status

One inconvenience for the filter for XLIFF 2.0 was that it did not support setting status of a segment as "translated", as it is the case for a long time in XLIFF 1 filter. The difficulty to do that is due to the fact that in XLIFF 2.0, status is in <segment> markup, so before the source text (while in XLIFF 1 it is in <tra>): as the file is generated markup per markup, we don't know, when generating <segment> markup, which segment in OmegaT it is related to.

In release 2.1.2, we try to solve the problem by buffering the contents of a segment until the end markup </segment>. Then we can change the status because we have read the source and checked in OmegaT whenever this segment has a translation or not.

This is experimental, for that reason we do not put it in release 2.0 yet.

[Release 2.1.2 only] Filter for XLIFF 1.x : reset status when a segment is changed

As xliff is a bilingual file format, it can happen that in OmegaT's "source" directory you put an already translated document. And it may occur that some translated segments have already "Approved" status. Now what if you do a change to these segments? Can we consider the status as approved any more? Now in release 2.1.2, in such a case, i.e. if you do changes in an "Approved" segment, its status will be restored back to "translated", so that a reviewer can decide to accept or not your modification.

In the future this may become an option for file filters. For the moment, use 2.1.2 if you want this feature and 2.0 if you don't want it.