Our Flare localization workflow is designed to preserve the full integrity of your project while delivering translated, build-ready output. The process begins with a thorough analysis of your Flare project package. We examine the topic structure, identify all conditional tags and their build expressions, catalog snippet dependencies, and map variable sets that may need language-specific values.
We work with your exported translation package or directly with the Flare project files, depending on your preferred workflow. When using Flare's built-in Lingo integration, we process the XLIFF files through our CAT tools while maintaining all inline formatting tags and Flare-specific markup. When working directly with topic files, we use a controlled extraction process that preserves the XML structure and all MadCap-proprietary elements.
During the DTP phase, our operators open the localized project in MadCap Flare to verify visual rendering, fix text expansion issues (common when translating from English to German, French, or other languages that typically run 20-35% longer), and adjust layout elements such as drop-down text areas, expanding text sections, and responsive content regions. We also verify that all cross-references resolve correctly and that the table of contents hierarchy reflects any localized heading changes.
Before delivery, we compile every target output defined in your project — typically HTML5 and PDF — and run a visual QA pass against the source-language output. This ensures that no build warnings have been introduced, all images and multimedia references are intact, and the final output matches your quality expectations. We deliver the complete localized Flare project so your team can rebuild and maintain it independently going forward.
English
Bulgarian
French
German
Spanish
Italian
Dutch