TBX is about the worst format for translating term lists, and, once this decidedly odd format was chosen, importing the TBX is about the worst way to go about the job.
#Ultraedit xsd code#
Then the client can convert the term list to TBX, XML, relational database, morse code recorded onto vinyl records or whatever suits their fancy. In that case, you put (the client puts) the words in an Excel table or a txt file and translate them.
Why would anyone want you to translate a TBX file, that is, a glossary?īecause you have a list of words in one language and you want them translated into another. (Why it expects a Multiterm XML when the TBX option was selected is a mystery.) One could argue that this is the case as it is: MT Convert expects a (Multiterm-format) XML and even if you try to trick it by renaming your TBX to XML, all you get is an error message because the file format is not right. xml like it should, the whole extension issue would be a moot point, and only the actual content of the file would matter. If the Multiterm import window had an "All files" option apart from. It's just to help programs and users identify the file type of each file, but it's not much more than a friendly indication, sort of "you may want to open this file with such and such program". Everything before that (in this case, glossary.tbx) is simply part of the file name, so there is no practical difference between calling something or glossary.xml.īTW the extension itself isn't too relevant, either. Each file has one extension, the bit after the last dot. while I applaud the spirit, I'm afraid that's not how computers work.
To the person who came up with the idea of making the file a. Hopefully SDL support will come clean on this. It would seem that the TBX import in your Multiterm version doesn't work. Apologies for assuming it was your fault. In fact in the next screen Multiterm says "Please choose TBX file (*.xml)" and if I expand the file selection drop down menu, *.XML is the only possible selection that I am allowed to make.
0 kommentar(er)
