Managing Translation Projects

After preparing content for translation, you need to complete the language structure by creating missing language copies, and create translation projects.

Translation projects enable you to manage the translation of AEM content. A translation project is a type of AEM project that contains resources that are to be translated into other languages. These resources are the pages and assets of the language copies that are created from the language master.

When resources are added to a translation project, a translation job is created for them. Jobs provide commands and status information that you use to manage the human translation and machine translation workflows that execute on the resources.

Translation projects are long-running items, defined by language and translation method/provider to align with organizational governance for globalization. They should be initiated once, either during initial translation or manually, and remain in effect throughout content and translation update activities.

Translation projects and jobs are created with translation preparation workflows. These workflows have three options, for both initial translation (Create&Translate) and updates (Update Translation):

1. Create new project
2. Add to existing project
3. Content structure only 

AEM detects whether a translation project is being created for the initial translation of content, or to update already-translated language copies. When you create a translation project for a page and indicate the language copies for which you are translating, AEM detects whether the source page already exists in the targeted language copies:

• The language copy does not include the page: AEM treats this situation as the initial translation. The page is immediately copied to the language copy, and included in the project. When the translated page is imported into AEM, AEM copies it directly to the language copy.
• The language copy already includes the page: AEM treats this situation as an updated translation. A launch is created and a copy of the page is added to the launch, and included in the project. Launches enable you to review updated translations before committing it to the language copy:
  • When the translated page is imported into AEM, it overwrites the page in the launch. 
  • The translated page overwrites the language copy only when the launch is promoted.

For example, the /content/geometrixx/fr language root is created for the French translation of the /content/geometrixx/en master language. There are no other pages in the French language copy. 

• A translation project is created for the /content/geometrixx/en/products page and all child pages, targeting the French language copy. Because the language copy does not include the /content/geometrixx/fr/products page, AEM immediately copies the /content/geometrixx/en/products page and all child pages to the French language copy. The copies are also included in the translation project. 
• A translation project is created for the /content/geometrixx/en page and all child pages, targeting the French language copy. Because the language copy includes the page that corresponds with the /content/geometrixx/en page (the language root), AEM copies the /content/geometrixx/en page and all child pages and adds them to a launch. The copies are also included in the translation project.

Create translation projects so that you can execute and manage the workflow for translating the resources of your language master. When you create projects, you specify the page in the language master that you are translating and the language copies for which you are performing the translation:

• The cloud configuration of the translation integration framework that is associated with the selected page determines many properties of the translation projects, such as the translation workflow to use.
• A project is created for each language copy that is selected. 
• A copy of the selected page and associated assets are created and added to each project. These copies are later sent to the translation provider for translating.

You can specify that the child pages of the selected page are also selected. In this case, copies of the child pages are also added to each project so that they are translated. When any child pages are associated with different translation integration framework configurations, AEM creates additional projects.

You can also manually create translation projects.

Initial Translations and Updating Translations

The References panel indicates whether the you are updating existing language copies or creating the first version of the language copies. When a language copy exists for the selected page, the Update Language Copies tab appears to provide access to project-related commands.

After translating, you can review the translation before overwriting the language copy with it. When no language copy exists for the selected page, the Create & Translate tab appears to provide access to project-related commands.

After you have created a translation project, you can use the Resources pane to add pages to the project. Adding pages is useful when you are including pages from different branches in the same project. 

When you add pages to a translation project, the pages are included in a new translation job. You can also add pages to an existing job.

As when creating a new project, when adding pages, copies of the pages are added to a launch when necessary to avoid overwriting existing language copies. (See Creating Translation Projects for Existing Language Copies.)

You can add pages, assets, tags or i18n dictionaries to the Translation Job of your Translation project. To add pages or assets:

Your pages and/or assets are added to you translation job.

You can add pages, assets, tags or i18n dictionaries to the Translation Job of your Translation project. To add an i18n dictionary:

Your dictionary is now in your translation job.

You can add pages, assets, tags or i18n dictionaries to the Translation Job of your Translation project. To add Tags:

Your tags are now added in your translation job.

The Translation Summary tile contains the properties that are configured for a translation project. In addition to the generic project information, the Translation tab contains translation-specific properties:

• Source Language: The language of the pages that are being translated.
• Target Language: The language into which the pages are being translated.
• Translation Method: The translation workflow. Either Human Translation or Machine Translation is supported.
• Translation Provider: The translation service provider that is performing the translation. 
• Content Category: (Machine Translation) The content category that is used for translating.
• Cloud Config: The cloud configuration for the translation service connector that is used for the project.

When a project is created using the Resources pane of a page, these properties are automatically configured based on the properties of the source page.

The Translation Job tile of a Translation project provides the status of a translation job, as well as the number of pages and assets in the job.

The following table describes each status that a job or an item in the job can have:

To see the status of each file in the job, click or tap the ellipsis on the bottom of the tile.

Specify the date before which your translation vendor needs to return translated files. You can set the due date for the project or for a specific job:

• Project: Translation jobs in the project inherit the due date.
• Job: The due date that you set for the job overrides the due date that is set for the project.

Setting the due date functions correctly only when the translation vendor that you are using supports this feature.

The following procedure sets the due date for a project.

The following procedure sets the due date for a translation job.

Scope a translation job to obtain an estimate of the cost of translation from your translation service provider. When you scope a job, source files are submitted to the translation vendor who compares the text to their pool of stored translations (translation memory). Typically, the scope is the number of words that require translating.

To obtain more information about scoping results, please contact your translation vendor.

When you scope a translation job, the status of the job is Scope Requested. When the translation vendor returns the scope, the status is changed to Scope Completed. When scoping is completed you can use the Show Scope command to review the scoping results.

Scoping functions correctly only when the translation vendor that you are using supports this feature.

Start a translation job to translate the source pages to the target language. The translation is performed according to the property values of the Translation Summary tile.

After you start the translation job, the Translation Job tile shows the Translation in Progress status.

Cancel a translation job to halt the translation process and prevent the translation vendor from performing any further translations. You can cancel a job when the job has the Committed For Translation or Translation In Progress status.

When the content comes back after translation and is in Ready for Review status, you can go in the translation job and accept/reject content.

If you select Reject Translation, you have the option to add a comment.

Rejecting content sends it back to translation vendor where he will be able to see the comment.

When content is translated for an existing language copy, review the translations, make changes if necessary, and then promote the translations to move it to the language copy. You can review translated files when the translation job shows the Ready For Review status.

To compare Language Copies to the language Master:

Complete a translation job after you have reviewed the translated files from the vendor. For human translation workflows, completing a translation indicates to the vendor that the translation contract has been fulfilled, and that they should save the translation to their translation memory.

After you complete the job, the job has the Complete status.

Archive a translation job after it is complete and you no longer need to see job status details. When you archive the job, the Translation Job tile is removed from the project.

Populate your language copy so that it contains content from the master language that you are translating. Before you populate your language copy, you must have created the language root of the language copy. 

You can manually create a translation project if you prefer to use the Projects console. 

When you manually create a translation project, you must provide values for the following translation-related properties in addition to the basic properties:

• Name: Project name.
• Source Language: The language of the source content.
• Target Language: The language into which the content is being translated.
• Translation Method: Select Human Translation to indicate that the translation is to be performed manually.

You can download the content of a translation job, for example to send to a translation provider that is not integrated with AEM via a connector, or to review the content.

You can import translated content into AEM, for example when your translation provider sends it to you because they are not integrated with AEM via a connector.