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.
If you are new to translating content, see Sites Translation Journey, which is guided path through translating your AEM Sites content using AEM’s powerful translation tools, ideal for those with no AEM or translation experience.
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):
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:
For example, the /content/wknd/fr
language root is created for the French translation of the /content/wknd/en
master language. There are no other pages in the French language copy.
/content/wknd/en/products
page and all child pages, targeting the French language copy. Because the language copy does not include the /content/wknd/fr/products
page, AEM immediately copies the /content/wknd/en/products
page and all child pages to the French language copy. The copies are also included in the translation project./content/wknd/en
page and all child pages, targeting the French language copy. Because the language copy includes the page that corresponds with the /content/wknd/en
page (the language root), AEM copies the /content/wknd/en
page and all child pages and adds them to a launch. The copies are also included in the translation project.Translation projects can be created or updated directly from the sites console.
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:
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.
To create a project, your account must be a member of the project-administrators
group.
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.
Use the Sites console to select the page that you are adding to translation projects.
Using the toolbar, open the References rail.
Select Language Copies, and then select the language copies for which you are translating the source pages.
Select Create & Translate and then configure the translation job:
Select Create.
Use the Sites console to select the page that you are adding to the translation projects.
Using the toolbar, open the References rail.
Select Language Copies, and then select the language copies for which you are translating the source pages.
Select Update Language Copies and then configure the translation job:
Select Create.
After you have created a translation project, you can use the Resources rail 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 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.)
Use the Sites console to select the page that you are adding to the translation project.
Using the toolbar, open the References rail.
Select Language Copies, and then select the language copies for which you are translating the source pages.
Select Update Language Copies and then configure the properties:
The target language set in the translation project should match with the path of the language copy as shown in references rail.
Select Update.
It is possible to create only the structure of the language copy, allowing you to copy content and structural changes in the language master to (untranslated) language copies. This is unrelated to a translation job or project. You can use this to keep your language masters in sync, even without translation.
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.
Use the sites console to select the language root of the master language that you are using as the source.
Open the references rail by clicking or tapping References in the toolbar.
Select Language Copies, and then select the language copies that you want to populate.
Select Update Language Copies to reveal the translation tools, and configure the properties:
Select Update.
Manual edits of translated content can be synchronized back to the Translation Management System (TMS) to train its translation memory.
AEM updates the translation of the existing strings in the translation memory of the configured TMS.
To use this feature:
storeTranslation
.
The translation memory updates can be intercepted and sent to a custom destination, for cases where a proprietary translation memory is used.
A property can be selected in the list view of the sites console that shows if a page has been translated, is in translation, or has not yet been translated.
The sites console now displays the Translated column showing the translation status of the pages listed.
Many translation tasks and advanced options can be accessed in the projects console.
Translation projects in AEM use the standard AEM projects console. If you are not familiar with AEM projects, review that documentation.
As any other project A translation project is made up of tiles that present an overview of the project tasks.
Use the commands and ellipsis buttons at the top and bottom of the tiles (respectively) to access controls and options for the various tiles.
You can manually create a translation project if you prefer to use the projects console instead of the sites console.
To create a project, your account must be a member of the project-administrators
group.
When you manually create a translation project, you must provide values for the following translation-related properties in addition to the basic properties:
You can add pages, assets, or tags to the translation job of your translation project. To add pages or assets:
On the bottom of the translation job tile of your translation project, select the ellipsis.
In the next window select the Add button in the toolbar and then select Assets/Pages.
In the modal window, select the topmost item of the branch that you want to add, and then select the check mark icon. Multi-select is enabled in this window.
Alternatively, you can select the search icon to easily look for pages or assets you want to add to your translation job.
Once selected, select Select. Your pages and/or assets are added to the translation job.
This method adds pages/assets and their children to the project. Select Asset/Page (without children) if you only want to add the parents.
You can add tags to a translation project similar to how you add assets and pages to a project. Just select Tags under the Add menu then follow the same steps.
The translation project properties are accessible via the ellipsis button of the project summary tile. In addition to the generic project information, the translation project properties contains translation-specific.
In your translation project, select the ellipsis at the bottom of the Translation Summary tile. Most project-specific properties are on the Advanced tab.
When a project is created using the references rail 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, and 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:
Status | Description |
---|---|
Draft | The translation job has not been started. Translation jobs are in Draft status when they are created. |
Submitted | Files in the translation job have this status when they have been successfully sent to the translation service. This status can occur after the Request Scope command or the Start command is issued. |
Scope Requested | For the human translation workflow, the files in the job have been submitted to the translation vendor for scoping. This status appears after the Request Scope command is issued. |
Scope Completed | The vendor has scoped the translation job. |
Committed for Translation | The project owner has accepted the scope. This status indicates that the translation vendor should begin translating the files in the job. |
Translation In Progress | For a job, the translation of one or more files in the job is not yet complete. For an item in the job, the item is being translated. |
Translated | For a job, the translation of all files in the job is complete. For an item in the job, the item is translated. |
Ready For Review | The item in the job is translated and the file has been imported into AEM. |
Complete | The project owner has indicated that the translation contract is complete. |
Cancel | Indicates that the translation vendor should stop working on a translation job. |
Error Update | An error has occurred while transferring files between AEM and the translation service. |
Unknown State | An unknown error has occurred. |
To see the status of each file in the job, select the ellipsis on the bottom of the tile.
Specify the date before which your translation vendor must return translated files. Setting the due date functions correctly only when the translation vendor that you are using supports this feature.
Select the ellipsis at the bottom of the translation summary tile.
On the Basic tab, use the date picker of the Due Date property to select the due date.
Select Save & Close.
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, contact your translation vendor.
Scoping is optional and only applies to human translation. You can start a translation job without scoping.
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.
You can start an individual job from within the project.
After you start the translation job, the translation job tile shows the translation in In Progress status.
You can also start all translation jobs for a project.
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 the translation vendor where they are able to see the comment.
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.
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.
You can use the sites console to review content, compare language copies, and activate the content.
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.
Select the page in the language master, select References, then select Language Copies.
Select the language copy to review.
Select Launch to reveal the launch-related commands.
To open the launch copy of the page to review and edit the content, click Open Page.
After you have reviewed the content and made necessary changes, to promote the launch copy click Promote.
On the Promote Launch page, specify which pages to promote and then select Promote.
To compare language copies to the language master:
In the sites console, navigate to the language copy you want to compare.
Open the References rail.
Under the Copies heading select Language Copies.
Select your specific language copy and then you can either click Compare to Master or Compare to Previous if applicable.
The two pages (launch and source) are opened side-by-side.
If an already translated source page must be renamed or moved, translating the page again after the move create a language copy based on the new page name/location. The old language copy based on the previous name/location will still be there.
The best practice in this scenario is to follow this procedure:
Although AEM offers several translation solutions and interfaces, it is also possible to import and export translation job information 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.