1. In the Content Library, click the map you want to localize.
   On the right side of the screen, the Resource Drawer opens.
2. Create a localization package by doing one of the following:

   Option	Description
   Recommended: Create a localization package for a released map	In the Resource Drawer, select Releases. In the Releases tab, go to the release you want to localize and click Localize.
   Create a localization package for a branched map	In the Resource Drawer, select Branches. You will see a list of branches related to your map. In the Branches tab, switch to the branch that contains the map you want to localize. The Branches tab closes and you can see the Content Library in the branch you switched to. Click the map you want to localize and, in the Resource Drawer, select the Jobs tab.
   Create a localization package for a standard map	In the Resource Drawer, select the Jobs tab.

3. Click Create Localization Job.

4. From the Job Type drop-down menu, select Source Package.
5. In the Manager field, choose the person you want this project to be assigned to.
6. Click the Locales field and select applicable target languages.
7. Click the Due Date field and set a deadline for this project.
8. In the Notes field, enter information about the project, including information for the localization provider.
9. In the Include drop-down menu, select an option:

   • If you are sending the files for localization for the first time, select All Resources.

   • If the files were already translated and you only need to send the changed files for localization, select Only Changed Resources. As a result, only the files that were modified since the last upload are included in the package.

   

   A summary of the configuration is added to the package in project-notes.txt.

10. Click Create.

    Each localization job has a unique number that appears both in the interface and in the name of the downloaded ZIP file. The number helps you ensure you are uploading the correct file to the correct job.

    Note:

    Localization job numbers are only guaranteed to be unique, not sequential. Non-consecutive numbers are normal and expected.

11. In the Jobs tab, click the newly created package.
12. Click Download Localization Package.
    A ZIP file named localization-job-number.zip, for example, localization-job-101.zip, is saved to your computer. The ZIP file contains these elements:

    

    Where:

    • source-language-reference folder contains the source map and all dependencies in the source language. The files are located in a folder structure that is identical to your Heretto CCMS folder structure.

      Important:

      Use files in this folder as the source for translation. However, never save the translation in this folder; always use a target language folder, like de-de, instead.

    • de-de folder contains DITA files associated with your map.

      Important:

      If this content hasn't been translated before, all files in this folder are in the source language. If this content has been translated before, files in this folder contain the existing translation to the German (de-de) language. Don't use files in this folder as the source for translation. Instead, use files from the source-language-reference folder.

    • project-notes.txt contains project notes added as part of this localization job

13. Send the ZIP file to your localization provider.

    If your localization provider is not familiar with localizing Heretto CCMS source packages, you may want to share with them Localize Source Package Content.

When localizing source package, it is important to understand how to use each folder the package contains. Make sure to follow these guidelines to ensure your translation uploads to the CCMS correctly.

1. Save the ZIP file you received for localization to your computer and unzip it.
   Important:

   Do not change the name of the folder to which you unzip the file.

   

2. Open the unzipped source package folder and read the project-notes.txt file that contains an email address for the project manager and important project-related information.
3. Navigate down the source-language-reference folder structure and use the DITA and media files in this folder as the source for translation.

   One way of using the source-language-reference folder is creating a copy of the entire folder, translating the copied files into a target language, then copying the translation over into the existing target language folder, like fr-ca or pl.

   Important:

   Don't save your translation in the source-language-reference folder. Instead, always save it in a respective target language folder, like fr-ca or pl. Also, you must save the localized files under their original file names and extensions.

   Remember:

   Don't modify any attributes or elements in the DITA files; only modify the content they contain.

4. Save your translation in a respective target language folder, like fr-ca or pl.

   Feel free to overwrite files in the target language folder or remove them before saving your translation.

   Note:

   If this content hasn't been translated before, all files in target language folders, like fr-ca or pl are in the source language. If this content has been translated before, files in target language folders contain the existing translation to the target language.

5. When you finish localizing all DITA and media files, zip the localized source package by right-clicking it and compressing it into a ZIP file. Name the new ZIP file exactly the same as the original ZIP file.
   Important:

   The new ZIP file must be named exactly the same as the original ZIP file.

   

6. Send the localized ZIP file back to the project manager or upload it to Heretto CCMS.

When your localization provider is done localizing your content, they send you an identical source package ZIP file with the same content. The only difference is that the DITA and media files in the target language folder(s) are now localized. Upload the ZIP file to Heretto CCMS and verify that localization is complete.

1. Navigate to the localization job for which you want to upload localized content back to Heretto CCMS by doing one of the following:

   Option	Description
   Recommended: Upload localized content for a released map:	In the Content Library, click the map for which you want to upload localized content. In the Resource Drawer that opens, select Releases. In the Releases tab, go to the desired release and click Localize.
   Upload localized content for a branched map:	In the Content Library, click the map for which you want to upload localized content. In the Resource Drawer that opens, select Branches. In the Branches tab, switch to the branch that contains the map for which you want to upload localized content. The Branches tab closes and you are back in the Content Library. Click the map for which you want to upload localized content. In the Resource Drawer that opens, select the Jobs tab.
   Upload localized content for a standard map:	In the Content Library, click the map for which you want to upload localized content. In the Resource Drawer that open, select the Jobs tab.

2. From the Localization Jobs list, select a job you want to upload localized content for. The value in the Job Type column will show Source Package for this localization job.
3. Click Upload Source Package and in the Upload localization package window, upload the ZIP file with localized content.

   You can easily identify the correct localization job by using the localization job number that you can see in both the ZIP file name and on the Localization Jobs list.

4. In the Upload localization package window, verify that the locales you upload match the locales in Heretto CCMS and click Apply.

   

   A notification Update was successful! appears.

5. In the Localizations in Progress section, verify that all resources in your localization job show as Current. The number in green should say 100%.
6. Optional: Under Localizations in Progress, click any locale to verify that all files associated with your map are loaded to Heretto CCMS.

   

7. Optional: If all work for this localization job is complete, mark the job complete by clicking Complete Job.

   The localization job status changes to Completed. You can no longer upload localized content for that package.