Translations: Migrating to Many to One
A helpful set of steps to assist teams migrating translations from multiple courses to the new many to one feature.
Sections
This overview provides some general steps to aid you in taking your already translated projects, utilizing these translations, and getting a jumpstart on creating a single many to one project that will contain all your project's languages.
In the first section you will begin by exporting the translation(s) from your previously translated project(s) and creating new translation export file(s) from your base project. Your base project will soon become the single project that has multiple languages.
Step 1
You will need to export the text from all the previously translated projects that you wish to import into the many to one single project. Your base project will then contain all your translations.
Step 4
You can use XML, but Excel is generally easier to use when we get to the comparison step.
Step 5
If you are not using Glossary, Page Notes, Page Transcripts, or Authoring Metadata you can uncheck these items. However, when you export again in the next step, you must use the same options as you selected in this step.
Step 11
You can search for the desired language or select it from the drop down. You can select all the languages you wish to export and export them all at once.
Now that you have exported all the translation file(s) from your previously translated projects, you can begin the next section of updating the translation import files for your many to one project.
In this section you will be comparing the structure of the previously exported translations with the blank translation import file(s). If the structures are identical, you will be able to simply copy and paste all elements into the correct column in a single step. If there are differences, you'll need to review closely so when you copy and paste the translations match the correct element.
Step 1
In this step you are comparing the two Excel exports to confirm they have the same number of Rows. If they do, you can simply copy the translations from your first export (on the right) into the the new blank export from your base language project (on the left) and you will have the import file ready for your new many to one multi-lingual project.
Step 2
In this instance we see that the Excel file on the left (new translation) has two less rows than the Excel export of the existing translation (on the right). Given the difference we need to review the two files to determine where the structure difference is located.
Step 3
We see that in the previously translated version of the project (Excel on the right), the translation added a Description for the two titles. These are not fields that have a description in the base project (Excel on the left). So if you skip these two fields when copying the translations into the new import file, everything will line up.
NOTE: There may be additional Tabs in the translation Excel file, such as Glossary, in this example. In many cases these items are reused, so no additional work will be needed, but do double check them to be sure.
Now that you have the new translation import file(s) ready, you can begin the import section.
In our last section, you will import all the newly updated translation file(s) into your base project. Once updated you can then complete any final steps such as unique media or final reviews that are needed to make your many to one languages project ready for distribution.
Step 1
Once you have updated all the new translation files, you can start to import them. In this step we have selected the base project.
NOTE: If you have multiple files, zip them up and you can upload with one step.
Step 3
Upload your newly updated translation file or zip of files and then dominKnow | ONE will process and import the languages into your new many to one project.
Once you have completed this section, make sure you review your content. Some items that you may need to adjust further are:
- In a Flow project if you have labels on an image or video, you may need to adjust the spacing to accomodate all languages so there is no overlap of text.
- In a Claro project, your text boxes will automatically grow in height, but you may need to manually adjust some text boxes so all languages have text wth the appropriate spacing for your page layout.
- If you have audio or video files that have closed captions, they will automatically use the associated language for the closed caption and no changes will be needed.
- If you have audio or video files that are unique to a given language you will need to utilize the Target function in dominKnow | ONE and add the audio or video files to the course and add the appropriate language target for each file, include your base language.
- If the audio and video files also have actions tied to them, you will need to add those actions in with the appropriate timings. Reviewing the actions and their associated settings in your previous project will provide the exact timings for this step.
- If you have unique images or other files, you can also use the Target function to display specialized images for any given language.
- If you use variables to set text used in your project, you can add conditions for setting the text based on the language selected, which is a system variable.
Comments ( 0 )
Sign in to join the discussion.