Preparing Content for Translation preparing-content-for-translation

Multilingual web sites generally provide some amount of content in multiple languages. The site is authored in one language and then translated into other languages. Generally, multilingual sites consists of branches of pages, where each branch contains the pages of the site in a different language.

The WKND tutorial site includes several language branches and uses the following structure:

/content
    |- wknd
        |- language-masters
            |- en
            |- de
            |- es
            |- fr
            |- it
        |- us
            |- en
            |- es
        |- ca
            |- en
            |- fr
        |- ch
            |- de
            |- fr
            |- it
        |- de
            |- de
        |- fr
            |- fr
        |- es
            |- es
        |- it
            |- it

The language copy for which you originally author site content is the language master. The language master is the source that is translated into other languages.

Each language branch of a site is called a language copy. The root page of a language copy, known as the language root, identifies the language of the content in the language copy. For example, /content/wknd/fr is the language root for the French language copy. Language copies must use a correctly configured language root so that the correct language is targeted when translations of a source site are performed.

Use the following steps to prepare your site for translation:

After you prepare your content for translation, you can automatically create missing pages in your language copies and associated translation projects. (See Creating a Translation Project.) For an overview of the content translation process in AEM, see Translating Content for Multilingual Websites.

Creating a Language Root creating-a-language-root

Create a language root as the root page of a language copy that identifies the language of the content. After you create the language root, you can create translation projects that include the language copy.

To create the language root you create a page and use an ISO language code as the value for the Name property. The language code must be in one of the following formats:

You can use either format, according to the structure that you have chosen for your global site. For example, the root page of the French language copy of the WKND site has fr as the Name property. The Name property is used as the name of the page node in the repository, and therefore determines the path of the page (http://<host>:<4502>/content/wknd/language-masters/fr.html).

Seeing the Status of Language Roots seeing-the-status-of-language-roots

AEM provides a References rail that shows a list of language roots that have been created.

Use the following procedure view the language copies for a page using the rail selector.

Language Copies on Multiple Levels multiple-levels

Language roots can also be grouped under nodes, for example, by region, while still being recognized as roots of language copies.

/content
    |- wknd
        |- language-masters
            |- europe
                |- de
                |- fr
                |- it
                |- es
                ]- pt
            |- americas
                |- en
                |- es
                |- fr
                |- pt
            |- asia
                |- ...
            |- africa
                |- ...
            |- oceania
                |- ...
        |- europe
        |- americas
        |- asia
        |- africa
        |- oceania