• State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 436 subscribers
  • Views 419 views
  • Users 0 members are here
Options
Related

Migrating to Trados Studio 2024: existing segments in TM are no longer 100% matches

Triview Translations

We've built a TM for a client in older versions of Trados. We've just installed version 2024. We're creating a new translation project for this customer, and segments for which we know 100% matches exist in the database are now seen as 98%. We double-checked this by creating a project with the same file in the older Trados version.

We use a custom XML filter for these files. We converted the filter from XML 1 to XML2, that seems to have gone well. Do we need to edit the TM to get our 100% matches back?
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    I can confirm that there's been a change in how tags are treated. This is the same segment, from the .sdlxliff file in the two versions:

    Trados 2021:

    <source>Company B.V.<x id="1403"/>Street name and postcode<x id="1404"/>PO Box<x id="1405"/>The Netherlands<x id="1406"/>T: +31 (0) 11 22 33<x id="1407"/>E: info@example.com</source>

    Trados 2024:

     <source>Company B.V.<x id="locked1" xid="lockTU_2de3274a-73b4-416d-9ad0-f90a1f326924"/>Street name and postcode<x id="locked2" xid="lockTU_020e643f-9c92-4368-89c3-dc8de4d3f77c"/>PO Box<x id="locked3" xid="lockTU_4af45342-6c75-42c0-8c0e-c76d507f6c1f"/>The Netherlands<x id="locked4" xid="lockTU_3b407000-9eaf-4b20-a25c-a1b8e1361b5a"/>T: +31 (0) 11 22 33<x id="locked5" xid="lockTU_0fac6235-8d98-4a0a-a152-c11513b0be14"/>E: info@example.com</source>

    Trados 2021:

    x id="1403"

    has been replaced with Trados 2024:

    x id="locked1" xid="lockTU_2de3274a-73b4-416d-9ad0-f90a1f326924"

    This is a line break in the source file (br/)

    So changing the XML filter won't help, and if I want to modify the TM, I'd have to create the new id and xid attributes in a way that they'll match what will be generated by Trados in the next translation job.
    emoji
Reply
  • 0

    I can confirm that there's been a change in how tags are treated. This is the same segment, from the .sdlxliff file in the two versions:

    Trados 2021:

    <source>Company B.V.<x id="1403"/>Street name and postcode<x id="1404"/>PO Box<x id="1405"/>The Netherlands<x id="1406"/>T: +31 (0) 11 22 33<x id="1407"/>E: info@example.com</source>

    Trados 2024:

     <source>Company B.V.<x id="locked1" xid="lockTU_2de3274a-73b4-416d-9ad0-f90a1f326924"/>Street name and postcode<x id="locked2" xid="lockTU_020e643f-9c92-4368-89c3-dc8de4d3f77c"/>PO Box<x id="locked3" xid="lockTU_4af45342-6c75-42c0-8c0e-c76d507f6c1f"/>The Netherlands<x id="locked4" xid="lockTU_3b407000-9eaf-4b20-a25c-a1b8e1361b5a"/>T: +31 (0) 11 22 33<x id="locked5" xid="lockTU_0fac6235-8d98-4a0a-a152-c11513b0be14"/>E: info@example.com</source>

    Trados 2021:

    x id="1403"

    has been replaced with Trados 2024:

    x id="locked1" xid="lockTU_2de3274a-73b4-416d-9ad0-f90a1f326924"

    This is a line break in the source file (br/)

    So changing the XML filter won't help, and if I want to modify the TM, I'd have to create the new id and xid attributes in a way that they'll match what will be generated by Trados in the next translation job.
    emoji
Children