you do not needed the "xdt" file

"xml" is the only file you needed

Unknown said:

you do not needed the "xdt" file

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:

https://multifarious.filkin.com/2016/10/17/square-pegs-in-round-holes/

That article help explain the Glossary Converter too.  It's the most downloaded app on the appstore, 34k downloads:

https://appstore.sdl.com/language/app/glossary-converter/195/

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)".

Regards

Unknown said:

Because I have used that ways, let's say 100 times.

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... 

Just for  little fun... convert this one:

2364.convertme.zip

Make sure that the defnition of the final termbase looks like this:

But don't use an XDT... and do it one click.

Yes, that is just a "little" fun.

I am expecting a better fun.

.

Your comment is a piece of cake.

Where is ".sdltb" ? It has all information you needed, so is mandatory.

If you want me to do this tiny quiz without sdltb, that is not a fun, just silly.

.

My "OneGo" tool reads sdltb first and rekon its structure

And put all the relevant information into it from Excel file.

.

Regards 

Unknown said:

Where is ".sdltb" ? It has all information you needed, so is mandatory.

But the original poster doesn't have an SDLTB and you said she didn't need the XDT?

Unknown said:

My "OneGo" tool reads sdltb first and rekon its structure

And put all the relevant information into it from Excel file.

So, you need an additional step which is to create the SDLTB first and then you can import the Excel file.  This of course is obvious because you need that structure and if you don't have an SDLTB you need the XDT to be able to create one that has the appropriate structure.  That's why when you use MultiTerm Convert you get two files, the XDT and the XML.

I hope you see what I'm saying here Adrian.  This is not a disagreement, I just just trying to add clarity to your statement that the user did not require an XDT when she clearly did because she didn't have an SDLTB.

However, here's an XDT for you, see if your tool can one-click the Excel file I gave you and convert it to the appropriate multilingual termbase with images, picklists etc.

0383.littlegame.zip

If it can then you've done a great job.

The Glossary Converter can convert the Excel file without the XDT, but this is because it asks for the structure in it's own UI before it can make the conversion.  For simple files it's also a simple drag and drop as you don't need the structure.  It also converts both ways, from SDLTB to Excel and can aso convert between TMX, TBX, CSV, TXT, UTX, GLO and a couple of machine translation dictionaries.

Unknown said:

Where is ".sdltb" ? It has all information you needed, so is mandatory.

But the original poster doesn't have an SDLTB and you said she didn't need the XDT?

Unknown said:

My "OneGo" tool reads sdltb first and rekon its structure

And put all the relevant information into it from Excel file.

So, you need an additional step which is to create the SDLTB first and then you can import the Excel file.  This of course is obvious because you need that structure and if you don't have an SDLTB you need the XDT to be able to create one that has the appropriate structure.  That's why when you use MultiTerm Convert you get two files, the XDT and the XML.

I hope you see what I'm saying here Adrian.  This is not a disagreement, I just just trying to add clarity to your statement that the user did not require an XDT when she clearly did because she didn't have an SDLTB.

However, here's an XDT for you, see if your tool can one-click the Excel file I gave you and convert it to the appropriate multilingual termbase with images, picklists etc.

0383.littlegame.zip

If it can then you've done a great job.

The Glossary Converter can convert the Excel file without the XDT, but this is because it asks for the structure in it's own UI before it can make the conversion.  For simple files it's also a simple drag and drop as you don't need the structure.  It also converts both ways, from SDLTB to Excel and can aso convert between TMX, TBX, CSV, TXT, UTX, GLO and a couple of machine translation dictionaries.

you used lots of words (280 of them including quote) as usual

but amazingly,  you do not understand the basic comcept/process of  "import"

what is import ?

you can not import when you do not have sdltb

so I did not mentioned it earlier

Regards

Unknown said:

you can not import when you do not have sdltb

Of course you can. You create sdltb first and then import.
Just like you do exactly the same when you get a TMX from someone and you are supposed to make a (new) sdltm from it.

Are you trolling here by making these dumb comments, or you are really just so dumb?