Translation Memory is the key to minimizing your translation costs. The rest of this article focuses on how you can save time and money by taking control of your TM and exploiting it to the full. Having got the translated content for the required target languages in Lingo, you then export back to a new Flare project for each of those languages. Figure 1 illustrates the two possible workflows. In both cases, it is possible to handle multiple target languages within the same Lingo project. The translation company then sends back the translated bundle, which you merge back into the Lingo project. Lingo identifies the files that require translation, converts them to XLIFF (XML Localization Interchange File Format), a standard format used by translators, and then you send these files to the translation company as a zipped ‘Translation Bundle’.
#Madcap lingo software#
Lingo is a self-contained product from MadCap Software that helps with the translation of MadCap Flare projects, Doc-To-Help projects, XML files, and documents in a range of formats including Microsoft ® Word. Whether you translate your MadCap Flare projects in-house, or you send them for translation by third-party translation companies, MadCap Lingo can play a potentially useful and cost-saving role in the process, mainly through its support for Translation Memory (TM). This can be time-consuming and costly - in some cases, far more expensive than the development of the source documentation in the original language. Within an increasingly global market, many software companies need to translate the documentation and supporting Help for their products into a range of different languages.