03.8.2018 by Peter Argondizzo

Six things to consider for your next MadCap Flare™ translation project

two people sitting across from each other looking at a computer and discussing language barriers

Many clients have transitioned to MadCap Flare™ to handle the authoring of their Help System content as well as their user instructions. MadCap Flare™ has quickly become the industry-leading solution for topic-based authoring. We just released a new e-book covering six critical points to consider for your next MadCap Flare translation project.

These topics will help you avoid some of the hassles associated with the translation of help content. Here is a list and a brief overview of the topics covered in the e-book.

1. Image Callouts in Flare

One of the cost drivers in the translation of technical content is handling embedded content or text in images. The cost of translating and formatting images can be reduced by following a few simple steps. Learn how to minimize the cost and time required to handle the translation of text in your images.

2. Localizing Images/Screenshots

Many of our clients use Flare to create instructional materials related to software. That type of documentation usually features screenshots of the different menus and components that a user encounters while utilizing the software. Following a few crucial steps will reduce the complexity and time required to manage all of your screenshots and images.

3. Replacing Images/Screenshots on the Back End in a Translated Flare Project

This step is a perfect follow-up point to number 2 on our list. Authors including screenshots in their documentation will need to take screenshots with the translated or localized software loaded in the system so that the user can easily find the relevant options in their language.

4. Publish and Review the EN Target

It is important to publish and review the English target, especially a PDF, to look for areas that might present any issues in the translated versions. The spacing/layout of the target should be reviewed, keeping in mind text expansion during translation. This step is also important because it allows the editor to review from the user’s perspective in the final format of the content.

5. Using Conditions in Flare

One of the significant advantages of using Flare is the ability to conditionalize text. This functionality means that you can designate pieces of content only to be used under certain conditions. Translating conditional text can sometimes be tricky if not handled properly.

6. Using Snippets – Chunks of Texts You Can Use Over and Over

Snippets are chunks of content that you can use in your project over and over. It’s content that you want to reuse in many different topics, but you don’t want to have to keep retyping that content, so you just type it once in a snippet. A good example would be a warning text. When you couple snippets with translation memory technology you can save significant time and money on translation costs.

Proper consideration of these steps should reduce the complexity and cost of your translation project. Download “Six Things to Consider for Your Next MadCap Flare™ Translation Project” here.