Conditional tags and snippets are two of Flare's most powerful features — and two of the areas most likely to cause problems during localization if not handled carefully. Conditional tags allow authors to include or exclude content based on audience, platform, output format, or any custom dimension. Snippets enable content reuse across multiple topics. Both require specific handling during translation and DTP.
For conditional tags, our first step is to obtain your condition tag set definitions and understand which build expressions you use for each target. This is critical because some conditioned content may never appear in certain outputs, meaning it either does not need translation (saving cost) or needs to be translated but will only be visible in specific builds. We map every condition tag to its build targets and translate content accordingly, ensuring no visible content is missed and no hidden-only content is unnecessarily translated.
During the DTP phase, we verify conditional rendering by compiling the project with each relevant build expression. We check that conditioned text blocks expand and collapse correctly, that conditioned rows in tables display as expected, and that no orphaned content appears where conditions have been applied to inline elements within paragraphs.
For snippets, we ensure translation consistency by processing all snippet files first and creating approved translations before moving to the topic files that reference them. This guarantees that the same terminology and phrasing appears everywhere a snippet is used. Our Flare operators also verify that snippet insertion points accommodate text expansion without breaking page layout, particularly in print outputs where column widths and page dimensions are fixed.
We document all condition and snippet handling decisions in our project report, so your team has full visibility into how these elements were managed across each target language.
English
Bulgarian
French
German
Spanish
Italian
Dutch