Data in custom fields is lost in TMX conversion

Data in custom fields is lost or only partially preserved in TMX conversion using Trados Studio 2021 SR2 - 16.2.10.9305 (see far right column in the images). This data is important for our translator. The problem occurs even though there is no processing of the TMX file on our part, just SDLTM - TMX - SDLTM roundtrip. Is there a workaround or a fix in a later version?

Trados Studio interface showing a project with Japanese text in the translation memory editor. The far right column indicates missing or partial data after TMX conversion.

Trados Studio interface with a focus on the translation memory editor. The issue with data loss in the far right column after TMX conversion is visible.

Fritz Knobloch



Generated Image Alt-Text
[edited by: Trados AI at 9:14 AM (GMT 0) on 29 Feb 2024]
emoji
Parents
  • Hi  ,

    Thank you for the above screen prints.

    I have tried to reproduce the same using simple flow such as exporting a TM with custom fields into a TMX format and importing it back. Unfortunately I could not reproduce this either in Studio 2021 SR2 -- 16.2.10.9305 or higher versions.

    Screenshot of Trados Studio showing a Translation Memory (TM) entry with Japanese source text and English target text, including custom fields with values 'test1Oana, test2Oana, test3Oana'.

    So my question is this a general issue that you're see this happening with all your TMs or with only specific ones? 

    How do you use the export-import, using the options in the Translation Memories view, out of the box? Or are you perhaps using a plugin for this?

    Regards,

    Oana Nagy | RWS Group

    _____________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 9:14 AM (GMT 0) on 29 Feb 2024]
  • Hi Oana,

    Thanks for your help. 

    I have not seen the problem in every file. In a number of tries I couldn't reproduce it in small files (< 2M). On the other hand, it may not always be immediately noticeable (e.g., here and there the number of items in a list is reduced by 1).

    It was my understanding that import-export has been moved out of Trados and into a plugin. I have Trados Translation Memory Management Utility installed, and I assume that is what is handling the conversions. The procedure I'm using is as follows.

    Export to TMX: Translation Memories view > Click Export in ribbon > browse to folder, specify filename > Finish (checkbox not checked)

    Import to SDLTM: Translation Memories view > click Upgrade Translation Memories icon on ribbon > Add File-based TMs > select TMX file > Finish

    Here is some more detail on what happened in an affected file I examined today. The segment I picked as an example started with 14 items in the custom field, and that decreased to 5 after a couple round trips.

    14 values in the original TM
    14 in the TMX from that
    7 in the TM from that
    7 in the TMX from that
    5 in the TM from that

    This seems to show that the problem occurs during import (TMX → SDLTM conversion).

    I don't know to what extent our format is common, but in the body of the TMX there is what appears to be a master list of values (<prop type="x-Sensor:MultiplePicklist">), and then in each <tu> that same tag is repeated for each value occurring in the segment. The master list lost one value in the roundtripping above, and of course in the segment itself the list of items went from 14 to 5. I haven't seen any pattern in what goes missing.

    Fritz Knobloch (standing in for Dai Yabashi)

    emoji
  • Hi  Fritz,

    It was my understanding that import-export has been moved out of Trados and into a plugin.

    Not necessarily! So while the plugin helps exporting to .tmx, remove duplicates or reverse the index, you can still use the out-of-the-box export/import options inside Studio, you can find them in the ribbon, here's the ribbon print screen with both options in the Translation Memories view:

    Screenshot of Trados Studio ribbon showing Translation Memories view with 'Import' and 'Export' options highlighted.

    So if you only tried using one, please check what happens if you use the other option, since you mention it happens only with some files.

    I would also be interested to test this further if you can share the problematic files and let you know my findings?

    Oana

    Oana Nagy | RWS Group

    _____________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 9:14 AM (GMT 0) on 29 Feb 2024]
  • Hi Oana,

    Apologies for the delay. I was away for a couple of weeks and then busy catching up. As I mentioned, I haven't seen the problem in small files. In a large file where I do see it (importing with the Upgrade Translation Memories button), if I cut out most of the TUs the problem disappears.

    I can send you a couple of sample files so you can see what's happening. I've replaced the TUs in a large TMX file (20,000+ TUs, 12.4 MB) with dummy data and anonymized the metadata. A smaller TMX file contains just the first 15 TUs from the larger one. How can I get the files to you?

    Fritz

    emoji
Reply
  • Hi Oana,

    Apologies for the delay. I was away for a couple of weeks and then busy catching up. As I mentioned, I haven't seen the problem in small files. In a large file where I do see it (importing with the Upgrade Translation Memories button), if I cut out most of the TUs the problem disappears.

    I can send you a couple of sample files so you can see what's happening. I've replaced the TUs in a large TMX file (20,000+ TUs, 12.4 MB) with dummy data and anonymized the metadata. A smaller TMX file contains just the first 15 TUs from the larger one. How can I get the files to you?

    Fritz

    emoji
Children