MultiTerm Extract 2017 just purchased - "warning!" error message on every TMX file and no extraction

Question

Hi there, 
 I just purchased MultiTerm Extract 2017 and have been attempting to extract terminology from bilingual files for hours with no luck. 
 I tried exporting a number of my SDLTMs to TMX format using Studio 2017 and then adding them to a project in MultiTerm Extract, but received this error every time: 
 "Warning! There were translation units (tu) found in file (name of my TMX file) which did not have a translation unit variant (tuv) with target language "English (United Kingdom)" 
 This warning pops up even after changing/checking the source and target languages are set as the correct sub-language (i.e. English (United Kingdom) rather than just English)... or am I missing something else here? I've tried using lots of different import/export settings but nothing helps. I've tried exporting and importing then re-exporting my TMs in Studio, using all kinds of different settings... I've tried only exporting from older TMs created in Studio 2014... only from brand new TMs... absolutely nothing has worked. 
 When I exported an SDLTM to a TMX checking the option for a Workbench-optimised TMX format for use in Trados 2007 (to see if this would help) I didn't get the error, but MultiTerm Extract just hung on reading the file, counting out the minutes without ever making any progress... 
 The only thing I have managed to make the software do is extract terms from a .doc file in a monolingual project... One file worked fine, but then another .doc file I tried imported all the Norwegian characters incorrectly, and when I tried to import exactly the same file in .rtf format to see if that would make a difference, MultiTerm just hung on reading the file and failed to open it at all... 
 To say that this software (for me at least) is "buggy" is an understatement! I have to say I'm really frustrated at just having parted with 400 Euros for this software and to have so far got nothing but hours of frustration with no return. Perhaps I'm doing something wrong here, but then surely a 2017 released product should not be this difficult to use, and should be compatible with the files I am exporting from Studio 2017 without this kind of trouble? 
 Hopefully someone at SDL can help me with this issue? Suggestions gratefully received! 
 Thanks, Alison

Paul · Answer

Hi Alison, 
 
Any chance you can share the SDLTM you are working with so I can do some testing? You can send me a link, if it's too large, to pfilkin@sdl.com 
 
Regards 
 
Paul

Paul · Answer

Hi Alison, 
 It seems the issue is related to your specific language pair. So Norwegian Bokmal. The best workaround I think is this: 
 
 Export from Studio using the export for Trados 2007 option (this is essential) 
 Replace the language codes nb-NO in the TMX file with no-NO using a simple search and replace and set the termbase or languages to use Norwegian Nynorsk, or 
 Replace the language codes nb-NO in the TMX file with no and en-GB with en using a simple search and replace and set the termbase or languages to use Norwegian and English without any variants 
 Complete the project and export to your termbase 
 
 That will allow the application to work correctly. MultiTerm Extract is still based on some fairly old technology and Norwegian Bokmal was always a problem when we transitioned from 2007 to 2009 all those years ago. Unfortunately the same overhaul was not applied to MultiTerm Extract. It's still a very useful application and often performs better than most alternatives today, but could do with some work to iron out these types of issues. 
 Once you have completed this if you specifically want a termbase with the Bokmal variant separate to the Nynorsk then the easiest solution is to run your termbase through the glossary converter to get an excel spreadsheet and then run it back through again with the variants you need. This last part will only take a minute or two and will allow you to get where you need to go. 
 I hope this helps, and apologies for the lengthy wait while we figured this out. 
 Regards 
 Paul

Trados Studio > 3. MultiTerm

MultiTerm Extract 2017 just purchased - "warning!" error message on every TMX file and no extraction