Methods for Translation

This feature requires you to communicate with a language professional, such as a translator or language service provider (LSP). During the conversation, you can ask about pricing, services, scheduling, process, and more. From Central, you can use the MadTranslations service or a third-party service.

MadTranslations

The easiest approach to getting material translated into another language is engaging MadTranslations. Since translation in Central is integrated with MadTranslations, much of the process is automatically handled for you.

Pros

MadTranslations offers complete end-to-end translation and localization services for any supported language.

The status of your translation project is automatically updated in Central, and you receive a fully functional project to build and publish.

This is a great option if you want to be guided through the translation process, and want it all done for you.

MadTranslations has an International Organization for Standardization (ISO) certification.

Cons

Full-service might sound costly but it proves to be more cost effective considering quality translation services and industry professionalism in return.

Workflow

1. Author Creates a translation branch in Central's Translation wizard. This includes selecting the MadTranslations service and agreeing to the Terms and Privacy statement.

2. MadTranslations Sends a pricing quote to client.

3. Author Rejects or approves the quote. When approved, the translation begins.

4. MadTranslations Sends the translated material back to Central (which notifies the author). The status is updated in the Translation grid. The translated branch overwrites the existing branch.

5. Author Coordinates any review of the translated content (if necessary), then generates and publishes output.

Third-Party

Your project will get packaged for your translator. This method is more hands on as it requires you to manually initiate steps in the translation process.

Pros

Translators are able to work with branches containing files packaged by Central, and use in a computer-assisted translation (CAT) tool.

Translated project files are easily integrated back into Central.

Cons

The translator needs to use a CAT tool that is familiar with Flare-based project files (e.g., MadCap Lingo). If not, additional steps outside of the Central workflow may need to be implemented to get translation files in a readable format (e.g., XLIFF); this type of conversion can be done with Lingo.

The author needs to manually download the project for translation, upload the translated project, and update the project status in Central's interface. The timing of these actions might require communication with your translator.

Workflow

1. Author Creates a translation branch in Central's Translation wizard. This includes selecting the manual translation process in Central.

2. Author Once the Create button is selected the branch displays in the Translation grid.

3. Author Communicates with a translator, downloads the translation branch, and sends it to the translator.

4. Translator Uses a CAT tool that can work with Flare project files to translate the content.

5. Translator Communicates with the author that the project is completed, and provides the author with the translated branch of the project.

6. Author Uploads the translated branch, and updates the status manually.

7. Author Coordinates any review of the translated content (if necessary), then generates and publishes output.

What’s Noteworthy?