• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 434 subscribers
  • Views 3285 views
  • Users 0 members are here
Options
Related

metadata missing after importing DGT tmx into sdltm

davide fezzardi

Hello everyone,

I'm writing here because of a problem with the import of DGT tmx (available here https://ec.europa.eu/jrc/en/language-technologies/dgt-translation-memory) into a sdltm. I can import segments but not fields related to them.

I would need the final sdltm to display the fields I can see in the TMX file which show the type of text the translation unit was taken from.

I have tried to perform the import using both "the imported data will be primarily used in mixed scenarios" and "the imported data will be primarily used with presegmented legacy SDL Trados ITD or TTX files" but the result was the same: no TMX field was imported into the sdltm.

Have you got any suggestion/idea on how to import translation units fields from tmx files into sdltm?

Davide
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi ,

    If you import the TMX then you need to make sure that you already have the appropriate fields available in the SDLTM so they can be populated. If you "upgrade" the TMX then these fields will be created during the upgrade process.

    Paul Filkin | 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

  • 0 in reply to Paul

    Hi Paul,

    thank you very much for your reply.

    I tried both ways (import with new fields, and upgrade) but the result I get is always a TM with plain translation units without extra fields:

    Just for an extra information, during the import and upgrade tests, I tried both the settings "The imported data will be primarily used in mixed scenarios" and "The imported data will be primarily used with presegmented legacy SDL Trados ITD files and TTX files" but each time I got no segment field in the final TM.

    Let me clarify that the reason I'm trying to do all this is that I would need to have only DGT TM segments which have certain CELEX codes in their fields ( for example "2017R1001").

    I would need to split the whole DGT TM into relatively smaller TMs divided by type of source text (directives, regulations, and so on).

    To do this I thought I could:

    1) filter the raw tmx file (using CELEX numbers) and then import it into an sdltm, or

    2) import the whole tmx file into an sdltm and then apply the filter.

    As to way 1, I managed to filter the tmx file (via Olifant or Xbench, I'm not sure which one I used) but it was not possible to import the filtered tmx file into an sdltm because the tmx file seemed corrupted. The filtered tmx didn't fit with the import process, it seemed the file included some errors.

    So I'm relying on step "2" but, regardless of the fact I import the tmx file or I upgrade it, I don't get the fields that could make the filtering step possible.
Reply
  • 0 in reply to Paul

    Hi Paul,

    thank you very much for your reply.

    I tried both ways (import with new fields, and upgrade) but the result I get is always a TM with plain translation units without extra fields:

    Just for an extra information, during the import and upgrade tests, I tried both the settings "The imported data will be primarily used in mixed scenarios" and "The imported data will be primarily used with presegmented legacy SDL Trados ITD files and TTX files" but each time I got no segment field in the final TM.

    Let me clarify that the reason I'm trying to do all this is that I would need to have only DGT TM segments which have certain CELEX codes in their fields ( for example "2017R1001").

    I would need to split the whole DGT TM into relatively smaller TMs divided by type of source text (directives, regulations, and so on).

    To do this I thought I could:

    1) filter the raw tmx file (using CELEX numbers) and then import it into an sdltm, or

    2) import the whole tmx file into an sdltm and then apply the filter.

    As to way 1, I managed to filter the tmx file (via Olifant or Xbench, I'm not sure which one I used) but it was not possible to import the filtered tmx file into an sdltm because the tmx file seemed corrupted. The filtered tmx didn't fit with the import process, it seemed the file included some errors.

    So I'm relying on step "2" but, regardless of the fact I import the tmx file or I upgrade it, I don't get the fields that could make the filtering step possible.
Children