SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
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.
right, so this post should moved to the category "SDL AppStore Applications"
you do not needed the "xdt" file
"xml" is the only file you needed
That's incorrect Adrian. It's true that you can import an XML file without the XDT, but in some case the XDT is very important as this defines the definition for the termbase:
That article help explain the Glossary Converter too. It's the most downloaded app on the appstore, 34k downloads:
I am not wrong.
Because I have used that ways, let's say 100 times.
If i wsa wrong, SDL is wrong not me.
If you want, you can rephrase it "that is work only for some case(s)".
As I said, it's true that you can import a multiterm XML into a termbase without the need for an XDT. But this is not always the case. Termbases can contain the same field names and very different data structures. These are defined by the XDT, so all I am saying is that it is incorrect to say you don't need the XDT as this is not correct in all cases. I imagine you only work with very simple glossaries, so in this scenario it's highly likely you have never had a problem. But as general advice for someone else, especially when you have no idea about the complexity of their termbase, it's not a good idea to say the XML file is the only file you need.
MultiTerm has required this for over 20-years...