Helen Brown 

Can you confirm what version of Studio and MultiTerm you are running now?  I guess you should be on these:

Trados Studio 2022 SR2 - 17.2.10.19084
MultiTerm 2022 SR2 - 17.2.3.2795

Also, what language is NE-01?  Some variant of Nepali maybe?  The fact it's an unrecognised code could be your problem.  Certainly we don't use this code at all in Studio so if you know what it's for you could change it in the TBX and then test again.

Hi Paul,

Thanks for getting back to me.

We have the following versions:

Trados Studio 2022 SR2 - 17.2.10.19084

MultiTerm 2022 SR2 - 17.2.3.2795

That is very odd re the language variant. The TBX files "should" only contain English and German.

I opened the TBX using Notepad and that also seems to have the correct languages. "NE-1" can't be found when I search in the tbx via Notepad. I found an older TBX file that had previously correctly converted and I am still receiving the same error message.

I have tried generating a TBX with one of our local multiterm files and then converting it back to XML and that seems to work fine, but it is a TBX compliant file in XML format, so that might explain why it seems to work without issue.

For IT security reasons at work, I am unable to install glossary converter myself to see if this tool will help our issue.

We only recently updated to SR2; I wonder if something has gone awry there.

I would be very grateful if you have any more bright ideas.

Thanks!

Helen Brown 

Helen Brown said:

I would be very grateful if you have any more bright ideas.

None... unless you can share the TBX?  Then we might be able to figure out what's going on.

Hi Paul,

I would like to be able to send you one of the smaller, problematic TBX files. I would have to clarify I am permitted to do so; we have to be aware of which content we are allowed to send out. I will clarify this. Could you let me know where I can send one of our TBX files to?

Thanks!

Helen Brown 

If it's small you could probably anonymise the content, and then it would not require permission.  Small files are always better as we inevitably have to cut them down anyway.  Nobody enjoys working with huge files!

But if this isn't possible for you then please send to pfilkin at sdl dotcom

Hi Paul,

I have permission to send one of the smaller troublesome TBX files. I will send it to you shortly. Thanks a lot!

Helen Brown said:

"NE-1" can't be found when I search in the tbx via Notepad.

 Helen, what language is "NE-01" supposed to be? Nepali? Are you searching "NE-1" or "NE-01"? First of all, make sure you are using standard ISO-639-2 codes (https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes). Next, instead of Notepad, try Notepad++ (a better tool for this purpose), to go inside your TBX file and replace <langSet xml:lang="NE-01"> for a standard ISO code, perhaps <langSet xml:lang="NE">? There would be as many tags of this type as entries for this language (Nepali?). I hope this helps. However, you said "NE-1" can't be found, which begs the questions?, do you have a file with the extension .tbx or .xml? Who is the provider (what tool?) of your TBX files?

In addition, the export functionality of SDL MultiTerm to TBX format is not fully compliant with the TBX-Basic specifications (still using the 2002 standard, not the 2008 standard). That was always a known issue. In fact, MultiTerm is not listed as any of the tools that claim TBX support (see: https://www.tbxinfo.net/tbx-support/). On this interesting subject you can also consult this extensive old post: community.rws.com/.../how-do-i-export-or-convert-a-multiterm-termbase-into-tbx-basic

Helen Brown 

Thanks for sending me the small file.  The header of the file is this:

<!DOCTYPE martif SYSTEM "TBXcoreStructV02.dtd">

This is Version 2 of the TBX standard and despite being officially available since 2008 I don't believe we support it in MultiTerm.  There is also a version 3 available since 2019 and this definitely isn't supported either.

However, the Glossary Converter supports both these flavours and if you set this up correctly you can convert direct to a Termbase in a couple of clicks:

I have sent you the Termbase I converted just so you can see and perhaps enhance your ability to get the Glossary Converter installed.

Hi,

I have run almost exactly into the same issue yesterday:

- TBX file with TBXcoreStructV02.dtd

- MultiTerm Convert 2022

- conversion error about "NO-NO" being an unsupported language (although this string does not exist in my TBX file)

I found an older MultiTerm 2019 Convert installation on an older computer - and here the conversion has worked fine.

So indeed it seems to be an issue with newer MultiTerm Convert installations, not with TBX 2.0 

Cheers,

Christine

Christine Bruckner 

You're right.  I just installed the 2019 version and indeed it does work.  I'll log it with support and if they agree I'll get share the bug number here.

Is there a reason why it's important to use MT Convert for this as opposed to the Glossary Converter?  Helps with prioritisation.

Hi Paul,

thanks a lot!

Well, for complex TBX files, I usually try both (Glossary Converter and MultiTerm Convert):
None of them works perfect in my case, but looking at the 2 results helps me to identify which additional tweaks (via regex in Notepad++) are needed.

One advantage of MultiTerm Convert is that it collects the picklist values from the TBX import file and includes (at least some of) them in the xdt. As far as I know, Glossary Converter does not offer this option - or have I simply overlooked it(?)

Cheers

Christine

The Glossary Converter does collect picklist values, unless they are already defined. Let's say you have a picklist field called Status. Check the list of fields in the settings for a Status field. If it is not there, create it and set the content type to picklist and leave the list of values empty. If it already exists, do same tests.

When you now covert a tbx file that contains Status fields, they are stored in the Field settings. The next conversion will not collect values, since they are already there. If you have multiple sources that have a Status field, with different values, you'll have to clear the stored values. Hmmm, maybe it would be useful to have the option to add to, keep or overwrite existing values...

Changing Field Properties (2)

Cheers, Gerhard

The Glossary Converter does collect picklist values, unless they are already defined. Let's say you have a picklist field called Status. Check the list of fields in the settings for a Status field. If it is not there, create it and set the content type to picklist and leave the list of values empty. If it already exists, do same tests.

When you now covert a tbx file that contains Status fields, they are stored in the Field settings. The next conversion will not collect values, since they are already there. If you have multiple sources that have a Status field, with different values, you'll have to clear the stored values. Hmmm, maybe it would be useful to have the option to add to, keep or overwrite existing values...

Changing Field Properties (2)

Cheers, Gerhard