Learn how to define translation rules to identify content for translation.
In the previous document of the AEM Sites translation journey, Configure translation connector you learned how to install and configure your translation connector and should now:
Now that your connector is set up, this article takes you through the next step of identifying what content you need to translate.
This document helps you understand how to use AEM’s translation rules to identify your translation content. After reading this document you should:
AEM Sites pages can contain much information. Depending on your project needs, it is likely that not all of the information within a page must to be translated.
Translation rules identify the content that is included in, or excluded from, translation projects. When content is translated, AEM extracts or harvests the content based on these rules. In this way only content that must be translated is sent to the translation service.
Translation rules include the following information:
AEM automatically creates translation rules for sites pages, but because each project’s requirements are different, it is important that you know how to review and adapt the rules as required to your project.
Multiple rules can be created to support complex translation requirements. For example, one project you may be working on requires all page information to be translated, but on another page only descriptions must be translated while titles are left untranslated.
Translation rules are designed to handle such scenarios. However in this example we illustrate how to create rules by focusing on a simple, single configuration.
There is a Translation Configuration console available for configuring translation rules.
To access it:
AEM automatically creates translation rules for all content. To view these rules:
/content context and then the Edit option from the toolbar.
The Translation Rules Editor opens with the rules that AEM automatically created for the
Page properties that will be translated are located under the General section of the list. You can add or update an existing property names that you want to explicitly include in translation.
You have now configured your translation rules.
AEM automatically creates translation rules. For a simple translation setup or to test a translation workflow, it is not necessary to create new rules or even modify the existing, automatically created rules. The details of these steps are presented to explain how the rules work and to give context to how AEM processes translations.
It is also possible to create rules just for your particular path or project by tapping or clicking the Add Context button in the Translation Configuration console. This is beyond the scope of this journey.
There are a number of additional properties that can be configured as part of your translation rules. In addition, you can specify your rules by hand as XML, which allows for more specificity and flexibility.
Such features are generally not needed to get started localizing your content, but you can read about them further in the Additional Resources section if you are interested.
Now that you have completed this part of the AEM Sites translation journey you should:
Build on this knowledge and continue your AEM Sites translation journey by next reviewing the document Translate content where you will learn how your connector and rules work together to translate content.
While it is recommended that you move on to the next part of the translation journey by reviewing the document Translate content, the following are some additional, optional resources that do a deeper dive on some concepts mentioned in this document, but they are not required to continue on the journey.