When Flare source files are packaged with MadCap's Lingo application the files for translation are prepared, managed, and exported into the XLIFF format that translators can understand. With this method, you use Lingo along with Flare to put files into a format that translators can use with any computer-assisted translation (CAT) tool.
|
Pros |
|
Translators are able to work with files bundled by Lingo, and use in a CAT tool of choice. |
|
Translated XLIFF files are easily integrated back into Lingo, and finally into Flare. |
|
Cons |
|
The files necessary for translation are not bundled automatically, and need to be selected manually for extraction. |
|
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 Third-Party Tool Workflow
There are many CAT tools available for a translator to use for translations (including Lingo).
- Author Creates Flare project in source language.
- Author Creates Lingo project based on Flare project. For details, see the Lingo online Help.
- Author Creates bundle of files in Lingo. This zips the files into the XLIFF file format.
- Author Provides the translator with the bundled files.
- Translator Uses a CAT tool to translate segments.
- Translator When done, the translator zips the translated XLIFF files, and sends them back to the author,
- Author Imports the XLIFF files into the Lingo project.
- Author Exports the Lingo project into a Flare project in the target language.
- Author In the translated Flare project, the author generates one of the following using the Target Editor: single target, multilingual target, or PDF stitching.
