Detecting language please wait for.......
I am working on a package sent by the client on a Mac (with the virtual machine paralells and windows and esxcel installed there). I tried to convert an excel file to sdl tb format as suggested by the SDL Manual used by the client. But I could only generate the formats: xdt, xml (as html file) and xdt.log. According to the help menu of the glossary converter the xml format can be used to be uploaded in Multiterm as glossary. But when I upload the xdt format in the term base section I get this the above message. Any idea. Had a look at other similar questions, but I did not get any further there.
Hi Ute Neumaier
The problem might be related to type of characters used in the termbase name or/and the path where the termbase is saved. Try making sure there are no Asian chars, or any characters with diacritics in the path.
not so good tip
now, we are living in the world of UNICODE
if you have problem with UNICODE, your tool is bad, simply BAD.
ok Former Member... thank you for that useful information. I'm trying to help with the error message received and there is a known bug in the knowledgebase that if you were to look would see that this could be caused by this problem. It's a bug and it might be the one the user has encountered.
Hello Paul, thanks for trying to help. I downloaded the latest version of the Glossary Converter, but I get the same message. The excel file does not have any asian characters nor diacritics. So the reason must be different. Any other idea?
Can you share your termbase by any chance? Would give me a chance to rule out a problem with that first? You can email to firstname.lastname@example.org if that's ok.
Could this have to do with the previous error message I get when opening the Glossary Converter? Multiterm is not detected and therefore standard format will be xdt/xml (translated from GErman)? But MT 2017 is installed and I can both open it.
Any idea why the xml format is created as HTML file?
It might be worth making sure you have the correct versions of MultiTerm and Studio installed:
SDL Trados Studio 2017 SR1 - 14.1.10017.54668SDL MultiTerm 2017 SR1 - 22.214.171.124461
Also did you see this advice in the Glosary Converter?
What exactly do you mean by "xml format is created as HTML file" (that doesn't make any sense to me) and what exactly makes you believe that this is happening?
It would be way more effective if you lay out the symptoms you see instead of laying out the - presumably incorrect - conclusions you made based on the symptoms?Looks like a typical XY problem: http://xyproblem.info/
Hi again Paul, I have run the Repair tool and have checked the versions. I have installed:
SDL Trados Studio 2017 SR1 126.96.36.199.4688
SDL Multiterm SR1 188.8.131.52461
I could update MT within the tool, for Trados I had to download the latest version manually. When I did that I got the message, that a newer tool is installed and if I want to install that, I need to delete the installed version first.
I ran the repair function before and after updating MT, but when opening the GC I still get the message that MT is not found. No idea, what else I could do.
HI Evzen, Thanks for trying to help. What I mean by html file is what you see on the attached picture:
That picture doesn't help at all as it doesn't show the content of the file...
But I'm guessing you just doubleclick the file and wait for what happens... and it opens it in Internet Explorer, which makes you believe it's an HTML file.But that's incorrect assumption. It's - most probably, since I'm guessing only from the file extension visible onthe screenshot - just a normal XML file.
looks like, your computer has some strange "Link" between file format (xml) and application (browser Explorer).
Hi Paul, Gerhard got back and wrote: "Hi Ute, believe me, if I had a solution, I would have fixed it or put it in the help file. When MultiTerm is not detected, it's a lottery. In some cases the repair tool helps, but not always. It seems to be related to the Windows patch level, too, and of course we can't reproduce it on any developer machines :-(Cheers, Gerhard".
Now I really don´t know what else to do and how to be able to use the Glossary Converter and creating MT glossaires myself. Any other idea what I could do?
thank you so much!
The solution is the old fashioned one I’m afraid. Use MultiTerm Convert. Once you’ve done this process once it’s not too bad, and I can explain the process for you using the files you’re sent if you need it?