Translate
Dear all,
maybe you have seen something similar and have an explanation or solution for this.
A term base created in MultiTerm 2017 with MultiTerm convert 2017 from a TBX file (from across) throws an error message when importing the converted XML file (see attached error message)
The term recognition window in Studio 2017 shows either nothing, continuously the information "loading term base" or, if the search settings are adjusted, only the first source term (no translation).
The red overhead lines for recognized terms are visible, so the search and the recognition works. It just seems that the term recognition window does not show the results (properly).
This is how it looks like in Studio 2017 with a term base created in MultiTerm 2017, MultiTerm Convert 2017 from TBX.
And this is how it looks like in Studio 2014 with the term base from MultiTerm 2017, converted TBX with MultiTerm Convert 2017.
If I convert the TBX file in MultiTerm 2014 and then create the MultiTerm 2017 term base out of that, the term recognition window shows the correct view of all terms and translations (in Studio 2014, 2015 and 2017).
Conversion of Excel files does not show this issue, so I assume it has something to do with the conversion of TBX.
Can anybody confirm this?
(sorry for not uploading the TBX for tests, but this is a customer file that I am not allowed to pass on)
thanks for your ideas,
Angelika