Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-2041

Tag IDs of created XLF 2 are invalid for importing in other CAT tools

XMLWordPrintable

      problem

      The XLF created by Translate5 (1.2 and 2.1) can not be imported in other CAT Tools which rely on the tag IDs. This problem is obviously only for the XLF 2.1 export, which can be triggered over the GUI. Therefore only for XLF 2.1 an example is provided.

      <segment id="seg1" state="reviewed" subState="translate5Autostate:reviewed_unchanged">
<source><pc id="1">Transcripción</pc></source>
<target>
<mrk id="1" translate="no" translate5:trackChanges="del">Transcripción</mrk><pc id="3">Transcription</pc>
</target>
</segment>

      The pc IDs should be the same in source and target segment since both are the identical tags!

      For XLF 1.2 the export of imported XLF files is not affected, since there the original tag IDs are conserved. Only an internal XLF 1.2 export is affected too. This is used for example for OpenTM2 connection, where the problem is not relevant since only source content is transferred and for globalese pretranslation where no target text is given.

      Since both exports are using the same code base both exports can be fixed together.  → This assumption was wrong, both types share code, but the code to generate the tags is not sharable between both types so far. Since there is no need to fix this problem for XLF 1.2, we do and can not fix it for XLF 1.2

        1.
        		 Exported xliff 2.1 is not valid Sub-task Done Thomas Lauria

          [TRANSLATE-2041] Tag IDs of created XLF 2 are invalid for importing in other CAT tools

          Marc Mittag [Administrator] made changes -
          Start Date [Gantt] New: 23/Apr/24 5:00 AM
          Marc Mittag [Administrator] made changes -
          Workflow Original: MittagQI Workflow [ 29525 ] New: MittagQI Workflow with Peer [ 35942 ]
          Marc Mittag [Administrator] made changes -
          Status Original: Test Ready [ 10005 ] New: Done [ 10000 ]
          Thomas Lauria made changes -
          ChangeLog Description New: The XLF 2.1 output is now valid (validated against https://okapi-lynx.appspot.com/validation).
          Thomas Lauria made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Test Ready [ 10005 ]
          Thomas Lauria made changes -
          Fix Version/s New: translate5 - 5.0.10 [ 11500 ]
          Thomas Lauria made changes -
          Summary Original: Tag IDs of created XLF 1 and 2 are invalid for importing in other CAT tools New: Tag IDs of created XLF 2 are invalid for importing in other CAT tools
          Thomas Lauria made changes -
          Description Original: h1.problem

          The XLF created by Translate5 (1.2 and 2.1) can not be imported in other CAT Tools which rely on the tag IDs. This problem is obviously only for the XLF 2.1 export, which can be triggered over the GUI. Therefore only for XLF 2.1 an example is provided.
          {code:java}
          <segment id="seg1" state="reviewed" subState="translate5Autostate:reviewed_unchanged">
          <source><pc id="1">Transcripción</pc></source>
          <target>
          <mrk id="1" translate="no" translate5:trackChanges="del">Transcripción</mrk><pc id="3">Transcription</pc>
          </target>
          </segment>{code}
          The pc IDs should be the same in source and target segment since both are the identical tags!

          For XLF 1.2 the export of imported XLF files is not affected, since there the original tag IDs are conserved. Only an internal XLF 1.2 export is affected too. This is used for example for OpenTM2 connection, where the problem is not relevant since only source content is transferred and for globalese pretranslation where no target text is given.

          Since both exports are using the same code base both exports can be fixed together.           		New: h1. problem

          The XLF created by Translate5 (1.2 and 2.1) can not be imported in other CAT Tools which rely on the tag IDs. This problem is obviously only for the XLF 2.1 export, which can be triggered over the GUI. Therefore only for XLF 2.1 an example is provided.
          {code:java}
          <segment id="seg1" state="reviewed" subState="translate5Autostate:reviewed_unchanged">
          <source><pc id="1">Transcripción</pc></source>
          <target>
          <mrk id="1" translate="no" translate5:trackChanges="del">Transcripción</mrk><pc id="3">Transcription</pc>
          </target>
          </segment>{code}
          The pc IDs should be the same in source and target segment since both are the identical tags!

          For XLF 1.2 the export of imported XLF files is not affected, since there the original tag IDs are conserved. Only an internal XLF 1.2 export is affected too. This is used for example for OpenTM2 connection, where the problem is not relevant since only source content is transferred and for globalese pretranslation where no target text is given.

          -Since both exports are using the same code base both exports can be fixed together.-  → This assumption was wrong, both types share code, but the code to generate the tags is not sharable between both types so far. Since there is no need to fix this problem for XLF 1.2, we do and can not fix it for XLF 1.2
          Thomas Lauria made changes -
          Status Original: Selected for Development [ 10100 ] New: In Progress [ 3 ]
          Marc Mittag [Administrator] made changes -
          Rank New: Rang erhöht

            tlauria Thomas Lauria
            tlauria Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: