TermBase eXchange format (Version 2) is a standard format to exchange terminology data. 

In addition to the standard level, it also has a somewhat lighter version called TBX Basic. Using it really only makes sense if you work with tools that specifically require the V2 Basic format, like MadCap Lingo.

Glossary Converter does not support all the details of the standard, but it seems to do the job for the basics. In particular, all TBX files it creates should be fully standard compliant. 

One possible problem: the entry Id in TBX V2 can be any string value. MultiTerm requires the ID to be a number. So when you convert from TBX to Termbase (or xdt), and the TBX has non-number entry ids, those will be replaced by unique random numbers.

The converter attempts to find fields in TBX and assigning them to the correct MultiTerm level. It's impossible to represent the layers of complexity the TBX defines for fields in other formats, so you frequently won't get a lossless conversion.

The TBX format is moving to a new version, TBX V3, which is also supported.

TBX files usually have the extension tbx, but sometimes also just xml. Since this could clash with the mtf.xml export files of MultiTerm, Glossary Converter automatically detects which type an xml file is.

See Known Issues for differences between TBX and MultiTerm language codes, and for size limits in general.

Created with the Personal Edition of HelpNDoc: Full-featured multi-format Help generator