Stax Filters and DGT-OmegaT test/dev: new releases published

Downloads: DGT-OmegaT 3.4-TEST-2.2, DGT-OmegaT 3.5-DEV-2.2, Stax-Filters-2.0.3

Open XML: ensure all files are in the target (bug corrected)

Files from Microsoft Office (DOCX, XLSX, PPTX...) are in reality zip archives containing multiple files. In previous versions of the filter, if translation of one of these files failed, other XML files were not translated and the resulting target file could be corrupted and not open in Word. In new version, it can happen that one of the file fails but this does not prevent generation of the rest of the document. As a result Word may protest about a missing file but will repair the document and open it, eventually with errors.

Note that the presence of such errors does not necessarily mean that the plugin has a bug: such errors can happen in particular when there are wrong tags in your translation. So, before reporting a bug, try to use OmegaT's tag validation (or Check Issues in OmegaT 4), and only if no error is detected but the document is corrupted, then you can consider that the plugin has a bug.

These changes are made in the plugin and in DGT-OmegaT 3.4-TEST 2.2 and 3.5-DEV 2.2. Stable release 3.3 is not affected because it does not include OpenXML filter at all.

Open XML: treatment of comments (experimental feature)

Actually our Open XML filter has same options as its equivalent in standard OmegaT. In particular you can choose whenever you want to translate comments or not.

In these new releases, we experiment a new possible behaviour: if you decide not to translate comments, then they will also be removed from the document.

In the future we may develop more options about what to do with comments: do you want to remove them completely (because you consider them as info for the translator, not as a part of the translation), to keep them in the original version, or to translate them? Do you want to have them only as "source text entry comments" (as they are info for the translator, you want to see them but without possibility to translate them)? Do you want to add translator's note in the result (as it is the case for XLIFF fillter but only in DGT-OmegaT, not in the plugin) ? Don't hesitate to comment and tell us if you see other possible options.

Entry key for XLIFF filters (only for StaxFilters-2.0)

In XLIFF filters, the entry key's "path" field should contain a path starting from the contents of <file original> markup, and then followed by eventual <group id> markups. This ensures that multiple files inside an XLIFF and also XLIFF groups can use identical ids without any conflict.

This is like that from early 1.0 versions but did not work for release 2.0; the bug had already been corrected in DGT-OmegaT 3.3 and later versions, but I had forgotten to update also the plugin.

Glossaries : display file in search results (DGT-OmegaT 3.5-DEV only)

Now if you use the search screen and includes glossaries, the matching location will not only say "Glossaries", but mention the file name.

Since it is done using fields from glossary entry which did not exist before release 3.5, only the DEV version includes this new feature.