Working with Translation Export Files

When you export a translation file you can choose XML or Excel as the file format.

There are some important things to know about working with each file type.

When you export an Excel translation file, you'll see quite a few columns.

The Course, Modules, Learning Objects, Pages and Elements columns help you understand the context of the text content.

The Current Text column shows you the first-language text that needs to be translated.

The Translated Text column is where the translated text strings need to be added (the purple cells). These will be blank when you export the file.

Here's an example image of a completed translation file.

Markup

If the Current Text field contains mark-up, the mark-up needs to be included in the translated text cell in order for the translated text to have the same formatting when it's imported.

For example, in the above image the Current Text in cell F12 shows:

The text that needs to be translated is "Preventing Slips and Trips", the content before and after that is mark-up.

So in the translated text cell you need to provide the translated text in the same location as the current text:

Additional sheets/tabs at the bottom of the Excel file

You will see additional sheets or tabs in the Excel file if your Project includes certain types of actions, variables, links or glossaries.

Actions-related text (such as for Pop-ups) and links will be listed for translation in the Links sheet (tab) accessible at the bottom of the file interface.

Glossaries and variables will be also shown on separate sheets/tabs.

The most important aspect of working with an XML translation export file is ensuring that the translation text strings are added in the correct location.

For each content element requiring translation, there is a line that shows the current text:

The translation text needs to be added into the next line and specifically within the [] brackets that follow "CDATA":

Here's what that looks like in the context of the overall document:

In the XML file, actions-related text (such as for Pop-ups), links, glossaries and variables are all listed at the top of the document.

dominKnow | ONE provides some text for your Projects automatically. Some examples:

• The rollover tool tip text for navigation bar buttons
• Text for Submit buttons on questions
• The text on default end screens and certificates

These language strings are already translated into the full list of available translation target languages, so these text strings are not included in the translation export files. 

The language setting for the Project or the user-selected language in a package published with multiple-languages sets the Project to use these default language strings automatically.

Not only do you save time and cost by not having to translate these text strings, you can also use them in your own content pages for additional time and cost savings.

They are all available as System Variables, so if you create your own end screens or certificates, for example, you can use these variables and know that these text strings are already translated for almost any language you need.