Using MadCap Lingo is a highly streamlined approach for translations. The translator can use Lingo as a computer-assisted translation (CAT) tool and translation management tool.
|
Pros |
|
MadCap products are designed to work together for maximum efficiency. This includes not only Flare and Lingo, but the entire suite: Central, Capture, Mimic, etc. |
|
When using Flare and Lingo some benefits are: managing your content, extracting source files for translation (automatically), running quality assurance reports, outsourcing to various vendors, and leveraging termbases and translation memory. |
|
Content is easily integrated back into Flare. |
|
Lingo can be used as a computer assisted translation (CAT) tool, as a translation management tool, or both. |
|
Lingo ensures that only the necessary files get translated as it identifies the strings and files that need to be translated per output. |
|
Cons |
|
When you receive translated files back, you might need to make minor adjustments to localized styles or layouts (e.g., text expansion) for publishing. Communicate with the translator about these needs. |
Translation With Lingo Workflow
The overview process in using Lingo for translation keeps the workflow aligned for optimal efficiency.
- Author Creates Flare project in source language.
- Author Zips Flare source files, and sends to the translator.
- Translator Creates a new Lingo project using the Flare project provided. The translator selects the source language and the target language. The translator uses Lingo to translate segments.
- Translator Exports the translated Lingo project into a Flare project in the target language and sends it to the author.
- Author From the translated Flare project, the author generates one of the following using the Target Editor: single target, multilingual target, or PDF stitching.
