• State Verified Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 48 subscribers
  • Views 1499 views
  • Users 0 members are here
Options
Related

x-context information lost after TM migration from GS 2015 to GS2020

Sébastien Desautel

Hello,
We have just migrated our TMs from GroupShare 2015 to 2020. Now we notice today that the context information to detect if an exact match is also a context match has been lost for many segments.

The exports from GS2015 had still these x-context information stored but the import task in GS2020 does not import the segment with the given information. In some segments on GS 2020, there is a x-context information but when I compare with the information in the GS2015 export file, I see other values.

Do we missed something? Is there an option to consider the x-context information that was maybe deactivated. I tried an import with the API and an import directly in Trados Studio but it does not help.

Can you tell me more about the import function? Is this a limitation in Trados or a bug?

Kind regards

Sébastien
Rate translation
×
Suggest better translation
×
Parents
  • +1

    Hi Sébastien,

    I had the same problem when exporting from GS 2014 and importing this into into GS 2020.

    You can try to use the workaround given by SDL support (Thanks to Sorin):

    " ... it seems I have found a workaround.

    If you remove from the header section of the original TMX (GS 2014 version) the

        <prop type="x-TextContextMatchType">PrecedingAndFollowingSource</prop>
        <prop type="x-UsesIdContextMatch">True</prop>

    properties and repeat the import into GS 2020, the resulting new TMX export should include the missing "x-Context" properties for TUs but also their equivalent "x-ContextContent" properties..."

    This worked on my side!

    Regards

    Rainer
Reply
  • +1

    Hi Sébastien,

    I had the same problem when exporting from GS 2014 and importing this into into GS 2020.

    You can try to use the workaround given by SDL support (Thanks to Sorin):

    " ... it seems I have found a workaround.

    If you remove from the header section of the original TMX (GS 2014 version) the

        <prop type="x-TextContextMatchType">PrecedingAndFollowingSource</prop>
        <prop type="x-UsesIdContextMatch">True</prop>

    properties and repeat the import into GS 2020, the resulting new TMX export should include the missing "x-Context" properties for TUs but also their equivalent "x-ContextContent" properties..."

    This worked on my side!

    Regards

    Rainer
Children