Translations
Previous Topic  Next Topic 

The Multi-Project feature can save on translation costs because when you translate a slave project, the translation can be re-used in any master project that references it. For example, let's say you create a project called "Common" and add 10 topics to it, then create a Spanish translation and have it translated. If you then register the "Common" project with a master project and then add a Spanish translation to the master project, the "Common" topics will appear as translated.


Following on from the "Advanced Example"...

In the "Advanced Example" we have a master project and two slave projects. If we open the master project, the base language currently looks like this:


Now select "Translations | Language Manager", click the [Add] button and choose a language. For this example, "Spanish (Mexico)" has been chosen. Click on the [Show the Contents Tree], then right-click in  the tree and select "Expand Contents Tree", so that we can compare the tree structure:

The Translation contents looks like this:

Referenced topics will have the green arrow to identify them, but if a translation page cannot be found for the referenced project and the current language, then a Question Mark will appear over the arrow to show that it cannot be found.


So, we will now translate the "Quantum Physics" project. After opening the "Quantum Physics" project, add "Spanish (Mexico)" as the Translation language and then translate each page and set the status to Green (for translated). Now, re-open the master project. Unless you have the following option checked, "Refresh Translated Pages when the Language is first Loaded", in the Multi-Project Register, there will be no change to the master translation. But if you now select "Translations | Cascade Changes", the translation will now look like this:

As you can see, the 7 topics below the "Quantum Physics" heading have now appeared, and show as translated.


For this example I have then done the same for the other slave project, "The Law of Attraction", but this time I have set the translated status to Amber, (for Part-Translated), to highlight the difference. After re-opening the master project and cascading the changes, the translation now looks like this:


Editing Referenced Translation Topics

All referenced pages are read-only, including for translations. To edit a referenced page, either open the slave project and edit the translation or click on the Properties tab in the translation and use the [Edit the Original] button.


Exporting Translations

When you export the translation, the Referenced pages will not be included! This is because each translation is independent. To export a translation, you need to export it from the original project.


See also

Updating and Maintaining Referenced Topics

The Multi-Project Register

Potential pitfalls and how to avoid them

Re-usability and your existing Projects

Splitting existing projects