Managing the Localization Process with Multiple Source Languages

The Localization process in Author-it is essentially a one way process - with new content being created in the source library, and the translation being done in the target libraries (either directly or via XML translation jobs). You only create objects directly in the Target Library when they are specific to that localization - and don't need to exist in the source library.

This can prove to be an obstacle when you have various documentation teams working in multiple languages. For example, let's use the scenario that you have an English and a German team - both responsible for creating new/original content. If you can only have one source library, how can content created in the target library be transferred and synchronized with that in the source library?

Solution

Create a multilingual source library with a Target Library for each language variant - including all source languages.

The source library should be used for all content creation, whether that be in English or in German. Publishing would only be done from the target libraries - not from the source. All content is then sent to the Target libraries when a library update is created, but only the relevant objects need to be translated.

Important: The use of release states is vital to control the flow of information. Without them, the whole process will quickly get out of hand and you'll be tearing your hair out as you struggle to identify which objects need translating and which ones don't. The more languages you work with, the more difficult it would become.

Topics created in the source library as English should be put in a release state of Released English and those created as German of Released German. You would then use translation job rules to include only the relevant content in the XML file to be translated - with the translation job rules in the English target library being set to include objects in the release state of Released German and the rules in the German target library being set to include objects in the release state of Released English.

Note: Objects in the target library that do not require translation should be flagged as localized by selecting then right clicking and choosing Localized.