Upgrading xliff 1.2 to xliff 2.0

Created on 22 December 2016, over 8 years ago
Updated 8 May 2025, 29 days ago

xliff 2.0 has become the standard version of xliff since 2014

http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html

Some translation services require the xliff file to be version 2.0, which causes translation workflows to include a step to convert the xliff version 1.2 file into an xliff version 2.0 file with 3rd party software.

Is there any way to alter the tmgmt module to support xliff version 2.0, or is there a way for a custom module to hook into that process to update the xliff file generated by tmgmt to be version 2.0?

Thanks in advance!

Feature request
Status

Active

Version

1.0

Component

Translator: File

Created by

🇺🇸United States sgtsaughter

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • Merge request !111Support for XLIFF 2.0 export format → (Open) created by kurttrowbridge
  • 🇺🇸United States kurttrowbridge

    Hello! I didn't see a newer issue related to XLIFF 2.0 support, but I needed this for a client project, so I implemented this for them and wanted to contribute it back. I was able to confirm with their translator that they could successfully export the file, provide a translation with their XLIFF 2.0-supporting software (Trados Studio 2019), and import it back in with TMGMT.

    I've added a merge request that's ready for review. Reviews would definitely be appreciated—full disclosure, I used AI to help generate the initial code based on the 1.0 exporter and the 2.0 schema, and would have been out of my depth otherwise. :) Thanks!

  • Pipeline finished with Failed
    29 days ago
    Total: 477s
    #491885
Production build 0.71.5 2024