SDLXLIFF filter: not picking up unedited .sdlxliff files created in Trados 2022

Issue #1353 open
Em Es created an issue

I’ll preface this bug report by emphasising that I’m a user, not a coder.

I have an old Studio 2015 license, and am trialling Studio 2022. If I take the same source .docx and create a project in both Studio versions, the resulting target-language sdlxliff from Studio 2015 can be added to an OmegaT project with the SDLXLIFF filter disabled and the SDLXLIFF (Okapti) filter enabled. Under the same file filter settings, the sdlxliff produced by Trados 2022 will not be visible in OmegaT.

Making small changes to the within the editor in Trados 2022 then saving produces sdlxliffs that are recognised by the SDLXLIFF (Okapi) filter. However, these will be displayed in the OmegaT editor suboptimally: all segments are shown as complete paragraphs. (Exception: if two segments are merged to one in Trados, that will usually be shown in OmegaT as two segments within a single paragraph).

Attached is a zip with the source docx, and four sdlxliff files: 1) made directly after importing the docx to the project, 2) directly importing the docx to the project and merging two segments, 3) directly importing the docx to the project then translating and confirming one segment, 4) direct import, confirm one segment, merge final two segments. (This final sdlxliff is to show how OmegaT will display each segment as a paragraph, with the exception of segments that were merged on Trados. The paragraph delimitations are still visible in Trados.)

Comments (1)

  1. Log in to comment