MultiTerm 2021 Fatal Error when importing a *.mtf.xml: Invalid character (Unicode: 0x12)

Question

Hi,

I am trying to import an Enlish>German termbase (*.mtf.xml) into a SDL MultiTerm 2021 termbase (*.sdltb).

In the import log file there is the line:

Fatal Error at (file C:\*\*.mtf.xml, line 3, column 250890): Invalid character (Unicode: 0x12)

The conversion log file (SDL MultiTerm 2021 Convert) contains the following:

Value of '0' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value</item>
<item type="Message">Error converting entry, [none]

How do I solve this?

Many thanks for your input.

Anne Spitzmüller · Accepted Answer

Thanks a lot for your help, Paul :-) 
 I fixed the issue by adding a line with the language names in the format of a Termbase entry to the beginning of the TXT file.

Paul · Answer

Anne Spitzmüller 
 Did you create the XML? If you did try recreating it, perhaps using the Glossary Converter as opposed to Multiterm. 
 If you didn't then try dragging the XML into a web browser... Firefox is best for this... and it will report where the problem characters are. Then you can remove them with a text editor and try again.

Paul · Answer

Anne Spitzmüller 
 Anne Spitzmüller said: Ok, I will try Glossary Converter. I hope, it works with TXT files ... 
 It does... but note that a TXT file can contain content in any format at all and so the format you need must be one that the Glossary Converter understands. This is from the Glossary Converter help:

Excel 
 File Type Support &rsaquo;&rsaquo;

Xls, xlsx, txt and csv files are supported for input. Output is usually to the Excel default format (xls for Office 2003, xlsx for Office 2007 and later), but can be configured to be another format instead. 
 Txt input files are expected to be tab separated, csv files comma separated. Other delimiters are currently not possible. 
 Both txt and csv files are written in Unicode encoding, to support all languages. Note that Microsoft Excel will export csv files in ANSI, thereby breaking non-Latin based languages. It can open Unicode files, though, so there should be no problem with the GlossaryConverter output. 
 Input tables need to have the language and field names in the first row. If a name is equivalent to a known language name (see table of supported languages , upper/lower case differences are ignored), the language is used automatically. For all other cases, users can choose a language interactively or configure a column name/language list. 
 You can have any number of languages in a table; field columns are also permitted, and unwanted columns can be skipped, see Field Selection . 
 Excel can be written (and read) in two formats, handling synonyms in different ways, see Synonyms and Synonyms in multi-line format .

Paul · Answer

Anne Spitzmüller 
 Anne Spitzmüller said: The names of the source and target language in the SDLTB file under Home > Languages are now the first entry and its translation. 
 I'm afraid I don't understand what you mean by this. Can you try and explain another way, or even better provide a screenshot?

Trados Studio > 3. MultiTerm

MultiTerm 2021 Fatal Error when importing a *.mtf.xml: Invalid character (Unicode: 0x12)

Top Replies

Excel