Translation workflows in dominKnow

Two easy ways to make new-language versions of any Project

When you are working in a project with the Ribbon toggled on the Home tab has a Translate button at the right end:

This opens the Translations panel.

There are two options at the top of this panel:

Duplicate and Export for Translation
Duplicate for Localization or Translation

These offer two different workflows for translating content, depending on your translation needs.

The first option, Duplicate and Export for Translation, is the workflow to choose if you are making an exact translation of the project with no need to make content changes or alterations before translating for the new language version.

The second option, Duplicate for Localization or Translation, is the workflow to choose if you need to make localization changes to the content before translating.

Here’s a walkthrough of each option.

Duplicate and Export for Translation

This workflow:

creates a copy of the first-language (master) project
sets it to the desired second language, and
automatically exports the Excel or XML translation file containing all the text strings in the master project.

The copied project is set in Pending Translation status and cannot be edited. (You will not see the copied project in the Browse Projects lists when it is set to this status.)

Once the translation team completes its work, the author imports the translation Excel or XML file imported back into the dominKnow | ONE site using the Import Translation File option on the Translation panel.

This replaces all the original-language text with the text strings provided in the Excel or XML doc and automatically moves the project from Pending Translation status to Active status. It will now be available in the Browse Projects lists.

Here’s a diagram of this workflow:

Because this workflow makes the copied, second-language course uneditable until the translation document is imported, it means this process is ideal for projects that need to be translated without any content alterations. The content in the master project and the second language project would be indentical, aside from the language differences. (You can, of course, make changes to the second-language project once the translation document has been imported and the project is set to Active status.)

Duplicate for Localization or Translation

This workflow:

creates a copy of the first-language (master) project
sets it to the desired second language, and
opens the copied project for editing.

Authors can then make required content changes so it is relevant to the target audience for the second-language version – maybe some pages need to be deleted or added, for example.

Once that work is done, the author then Exports the translation file using the Export Translation File option available on the Translations panel.

Once the translation team completes its work, the author imports the translation Excel or XML file imported back into the dominKnow | ONE site using the Import Translation File option on the Translation panel. This replaces all the original-language text with the text strings provided in the Excel or XML doc.

Here’s a diagram of this workflow: