Lars Sidelmann Nielsen 

So your problem is not that you import and you get an empty TM?  You solved that one?  It's just that you no longer see an AT status for a TMX created off a machine translation project.  You have highlighted the original translation memory format attribute, which is Translators Workbench and not machine translation specifically.  The important thing is that the creationID is "MT!".

However, this will only work in later versions of Studio if the SDLTM was created in an older version of Studio.  The reason for this is that a few years ago a decision was taken to change the import behaviour so that the act of importing was essentially considered an approval on your part for the segments to be used as a Translation Memory... ie. they are now approved and not just unedited MT.

The best solution I can suggest is you penalise the TM you created from this TMX so it always gets a 99% match or lower.  IF you have imported the TMX into an existing SDLTM already then create a filter mismatch penalty so you get the results like this when they come from TUs created by MT!:

Created here:

Lars Sidelmann Nielsen 

So your problem is not that you import and you get an empty TM?  You solved that one?  It's just that you no longer see an AT status for a TMX created off a machine translation project.  You have highlighted the original translation memory format attribute, which is Translators Workbench and not machine translation specifically.  The important thing is that the creationID is "MT!".

However, this will only work in later versions of Studio if the SDLTM was created in an older version of Studio.  The reason for this is that a few years ago a decision was taken to change the import behaviour so that the act of importing was essentially considered an approval on your part for the segments to be used as a Translation Memory... ie. they are now approved and not just unedited MT.

The best solution I can suggest is you penalise the TM you created from this TMX so it always gets a 99% match or lower.  IF you have imported the TMX into an existing SDLTM already then create a filter mismatch penalty so you get the results like this when they come from TUs created by MT!:

Created here:

Hi,

Thanks to you I can in fact use the tmx created from machine translation, but it is quite annoying to have to edit the tmx first. What I don't understand is that - without having edited the file first - I can import the tmx into a TM in Studio 2019 without any problems. In Studio 2022 nothing is imported. The problem is only with these MT.tmx's and not f.ex. *AL.tmx or *RET.tmx.

I first discovered the missing AT-status when I upgraded my 2019 version of Studio a while ago. I will try to adapt your suggestions - or just live with it as it is.

Thanks a lot for your help.

Best regards

Lars

Lars Sidelmann Nielsen 

Lars Sidelmann Nielsen said:

The problem is only with these MT.tmx's and not f.ex. *AL.tmx or *RET.tmx.

I have no idea what all these files are... looks like some naming convention your customer uses.  I guess the problem just relates to MT! as I already explained.

Hi Paul,

Do you know where I can get technical help in order to solve this problem as it is a problem which only exists in Studio 2022?

I have asked my former colleagues in the European Commission. They have Studio 2021 installed and they have no problems importing these tmx's created with machine translation - neither with earlier versions of Studio.

Kind regards

Lars

Lars Sidelmann Nielsen 

If you want a closer connection with the technical support team then you will need to purchase a support contract.  If you don't want to do that then you have this forum.

Hi,

We have also recently discovered this issue with these MT TMX files. After a little experimenting, we have found the following:

It seems that in order for segments to be displayed as "AT" in Studio, the TMX files need the following configuration:

• o-tmf="TW4Win 2.0 Format" in the header element and <tu creationid="MT!"> for the segments, or
• o-tmf="SDL TM8 Format" in the header element, and both <prop type="x-Origin">MachineTranslation</prop> and <prop type="x-ConfirmationLevel">Draft</prop> in the tu elements in the tmx file.

Apparently, segments to be interpreted as "AT", the Confirmation level should be set to Draft (this is implied in the TW4Win version). However, Studio 2022 seems to have disabled Draft in the list of confirmation levels by default when importing TMX files. 

The goal therefore is to convince Studio 2022 to import segments that have Draft status.

We have found two possible workarounds for Studio 2022:

1. Programmatically, for automated project preparation: add ConfirmationLevel.Draft to ConfirmationLevels when setting import settings:

private void SetImportSettings(SdlImportSettings imp, bool allowDraft = false)
{
  imp.CheckMatchingSublanguages = false;
  imp.NewFields = SdlImportSettings.NewFieldsOption.AddToSetup;
  imp.ExistingFieldsUpdateMode = SdlImportSettings.FieldUpdateMode.Merge;

  List<ConfirmationLevel> levellist = new List<ConfirmationLevel>();
  levellist.Add(ConfirmationLevel.ApprovedTranslation);
  levellist.Add(ConfirmationLevel.ApprovedSignOff);
  levellist.Add(ConfirmationLevel.Translated);
  if (allowDraft) levellist.Add(ConfirmationLevel.Draft); // this is the key

  imp.ConfirmationLevels = levellist.ToArray();
  imp.ExistingTUsUpdateMode = SdlImportSettings.TUUpdateMode.AddNew;
  imp.PlainText = false;
  imp.TagCountLimit = 10;
  imp.IncrementUsageCount = true;
  imp.IsDocumentImport = true;
}

2. For manual import, a little trick is needed:

1. Save a blank text file with the extension sdlxliff (e.g. "empty.sdlxliff") somewhere handy
2. In Studio2022, open the Import dialog for the TM to import the MT tmx file into
3. Select both the MT tmx file and "empty.sdlxliff" in the list of files to be imported. This will enable the Bilingual Document Import Options step.
4. At the Bilingual Document Import Options step, check Draft.
5. Import. You will get an error line for "empty.sdlxliff" but the MT contents will be imported, and the AT tag will be displayed in the Translation Results window.

This way, you can keep using the original tmx output format  (o-tmf="TW4Win 2.0 Format" and <tu creationid="MT!"> for the segments).

Having said all the above, I (and presumably many of our colleagues) would really appreaciate it if Trados could (re-)include ConfirmationLevel.Draft in the list of default ConfirmationLevels for TMX import, or at least make the option available in a user-friendly way for Studio 2022 (and later).

Best regards,

Attila

Daniel Brockmann  fyi.

Thanks for making me aware  Paul  - it seems this particular case is fixed in the upcoming Studio 2022 SR1 release, but we have another instance where alignment TMX files with Draft confirmation level is not imported correctly, either, and I will prioritize that with the team as well.

Yep, I just came across the issue with the confirmation level and it would be great if it could be solved.