Calvin F 

What fun problem to resolve. If it works in 2019 - can you then open the TM in 2022?

Are you have to share the tmx file with me as I would love to ensure moving forward a direct import into 2022 should be possible. 

Lyds

Hi. Thanks for looking into it!

Yes, when you create the TM in 2019 and upload the TMXs, you can then open the TM without issues in Studio 2022.

I can't share the TMX files (at least not without a lot of modification) - however, it really does seem to affect any TMXs with note elements and not just the specific TMXs we're working with.

For example, I've tested the short, simple sample TMX document from the TMX specifications here:

https://www.gala-global.org/tmx-14b#AppSample

That TMX document does not import in Studio 2022 either. However, as soon as you delete the <note> elements, the TMX imports without issue.

Calvin F 

My instinct tells me note would be considered a custom field and provided that is accommodated for the data will import.
If you create an empty 2022 SDLTM then run an export to open in NotePad++  <note> does not fall part of its basic structure. 



But why does it work in 2019?
Could it be that for 2019 you are using a template when creating the TM / importing into an existing TM that has <note> as part of the TM structure?

I will take a look at the link you shared 

Lyds

Thanks for looking into it.

Apologies if I'm misunderstanding but in your screenshot it seems to list <prop> elements, which are indeed used for custom fields. However, in this case I'm not referring to a custom field, but the <note> element as part of the TMX specification:

https://www.gala-global.org/tmx-14b#note

(Again, sorry, I may be misunderstanding what you mean)

 Calvin F 

<prop> elements as seen in my screen print are not custom fields. They are in fact default.
Where as you are thinking 

Calvin F said:

it seems to list <prop> elements, which are indeed used for custom fields.

<note> would be a custom field as I see it. This is further supported given your resource link has the following statements

• while <note> and <prop> allow you to store information specific to each <tuv>.
• <note>Text of a note at the TU level.</note>
  
  

I also see they say: 

<note>This is a note at document level.</note>

In your working examples is note at document level or TU level?

In order to try clear confusion quicker and given you say that Trados Studio 2019 the import works error free,  please open the TM settings and check to see if there is <note> listed as a custom field:

Alternatively please do provide a small data set

Lyds

 Calvin F 

<prop> elements as seen in my screen print are not custom fields. They are in fact default.
Where as you are thinking 

Calvin F said:

it seems to list <prop> elements, which are indeed used for custom fields.

<note> would be a custom field as I see it. This is further supported given your resource link has the following statements

• while <note> and <prop> allow you to store information specific to each <tuv>.
• <note>Text of a note at the TU level.</note>
  
  

I also see they say: 

<note>This is a note at document level.</note>

In your working examples is note at document level or TU level?

In order to try clear confusion quicker and given you say that Trados Studio 2019 the import works error free,  please open the TM settings and check to see if there is <note> listed as a custom field:

Alternatively please do provide a small data set

Lyds

Yes, I understand <prop> elements are default. I was just saying they are used to define custom fields, i.e. those elements which are not part of the TMX specification.

However, <note> is a part of the TMX specification, just like <prop> is. Yet it appears to cause issues in Studio 2022 but not Studio 2019.

"Note" is not a custom field in the TM in Studio 2019 or Studio 2022. And even if I add it, that does not change anything. It would create a prop element defining note. But note is a part of the TMX specification just like prop is.

As mentioned, the sample TMX file from the TMX specification does not work either. But as soon as you delete the note element, it will import both in Studio 2019 and Studio 2022.

https://www.gala-global.org/tmx-14b#AppSample

As a further test, I have created the simplest TMX via Studio that I could. Then I added a <note> element. Afterwards, I could import that TMX without issue into a blank Studio 2019 TM. However, that same import does not work on a blank Studio 2022 TM. It only works once you delete the <note> element.

<?xml version="1.0" encoding="utf-8"?>
<tmx version="1.4">
  <header creationtool="SDL Language Platform" creationtoolversion="8.1" o-tmf="SDL TM8 Format" datatype="xml" segtype="sentence" adminlang="en-US" srclang="en-US" creationdate="20240104T130028Z" creationid="test">
    <prop type="x-Recognizers">RecognizeAll</prop>
    <prop type="x-IncludesContextContent">True</prop>
    <prop type="x-TMName">Test (EN-DE)</prop>
    <prop type="x-TokenizerFlags">DefaultFlags</prop>
    <prop type="x-WordCountFlags">DefaultFlags</prop>
  </header>
  <body>
    <tu creationdate="20240104T130153Z" creationid="test" changedate="20240104T130156Z" changeid="test" lastusagedate="20240104T130156Z">
    <note>A simple greeting</note>
      <prop type="x-LastUsedBy">test</prop>
      <prop type="x-Context">0, 0</prop>
      <prop type="x-Origin">TM</prop>
      <prop type="x-ConfirmationLevel">Translated</prop>
      <tuv xml:lang="en-US">
        <seg>Hello</seg>
      </tuv>
      <tuv xml:lang="de-DE">
        <seg>Hallo</seg>
      </tuv>
    </tu>
  </body>
</tmx>

Calvin F Please find attached a tmx file based on your sample.

It fails for me in 2021 and 2022 with the same error you mentioned: 

It is very unclear to me how you have it working error free in 2019 but I will continue to enquire. 

Note.tmx

Lyds

I think I had a similar problem last spring (2023) trying to import tmx files from an external MT engine into the trial version of Studio 2022. During an Elevate event in May 2023 I was explained the problem was not popping up with Studio 2021 and was going to be fixed with the Studio 2022 release of June 2023. I would like to make sure this issue has been fixed before upgrading. Looking forward to knowing more, thanks and regards.