Early on, the folks in charge at MadCap recognized that there was a strong link between the language and technical writing industries (this may have a “duh” effect on most of us, but remember that many in the technical authoring world have yet to make this amazing discovery). So they spent quite a bit of early effort to become more visible to the translation industry, partly by showing up at industry events but also by providing useful features such as full Unicode support, outstanding double-byte support for East Asian languages and support for bidirectional languages. . .
Setting up a project is as easy as the actual translation interface suggests and essentially consists of three steps: selecting the translation files, the TM and the termbase. The ease of creating projects is fundamentally relevant to a tool that is designed to be used not only by language specialists but also by managers of technical writing crews.
It’s important to note, though, that the tool isn’t primarily set up to be used as a management tool; it is built with the translator in mind. While it is possible to send out external files in the form of so-called “Lingo bundles,” these really are only zipped-up XLIFF files. If you want to send other supporting data along with it, such as translation memories or termbases, you’ll have to separately export those in the form of TMX and TBX-Lite respectively.
As a translation tool, Lingo has some very helpful features . . .