Preparing Content for Translation
- Topics:
- Language Copy
CREATED FOR:
- Admin
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 sample Geometrixx Demo Site includes several language branches and uses the following structure:
/content
|- geometrixx
|- en
|- fr
|- de
|- es
|- it
|- ja
|- zh
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/geometrixx/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.
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.
Use the following steps to prepare your site for translation:
- Create the language root of your language master. For example, the language root of the English Geometrixx demo site is /content/geometrixx/en. Ensure that the language root is correctly configured according to the information in Creating a Language Root.
- Author the content of your language master.
- Create the language root of each language copy for your site. For example, the French language copy of the Geometrixx sample site is /content/geometrixx/fr.
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
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:
-
<language-code>
The supported language code is a two-letter code as defined by ISO-639-1, for exampleen
. -
<language-code>_<country-code>
or<language-code>-<country-code>
The supported country code is a lower-case or upper-case two-letter code as defined by ISO 3166, for exampleen_US
,en_us
,en_GB
,en-gb
.
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 Geometrixx site has fr
as the Name property. Note that the Name property is used as the name of the page node in the repository, and therefore determines the path of the page. (http://localhost:4502/content/geometrixx/fr.html)
The following procedure uses the touch-optimized UI to create a language copy of a web site. For instructions that use the Classic UI, see Creating a Language Root Using the Classic UI.
-
Navigate to Sites.
-
Click or tap the site for which you want to create a language copy.
For example, to create a language copy of the Geometrixx Outdoors site, you would click or tap Geometrixx Outdoors Site.
-
Click or tap Create, and then click or tap Create Page.
-
Select the page template and then click or tap Next.
-
In the Name field type the country code in the format of
<language-code>
or<language-code>_<country-code>
, for exampleen
,en_US
,en_us
,en_GB
,en_gb
. Type a title for the page. -
Click or tap Create. In the confirmation dialog box, click or tap either Done to return to the Sites console, or Open to open the language copy.
Seeing the Status of Language Roots
The touch-optimized UI provides a References panel that shows a list of language roots that have been created.
The following procedure uses the touch-optimized UI to open the References panel for a page.
-
On the Sites console, select a page of the site and then click or tap References.
-
In the references panel, click or tap Language Copies. The Language Copies panel shows the language copies of the web site.
More help on this topic
Experience Manager
- Administering User Guide overview
- Sites Features
- Website Administration
- Reusing Content: Multi Site Manager and Live Copy
- Live Copy Overview Console
- Configuring Live Copy Synchronization
- Creating and Synchronizing Live Copies
- MSM Rollout Conflicts
- MSM Best Practices
- Translating Content for Multilingual Sites
- Managing Translation Projects
- Identifying Content to Translate
- Preparing Content for Translation
- Creating a Language Root Using the Classic UI
- Connecting to Microsoft Translator
- Configuring the Translation Integration Framework
- Language Copy Wizard
- Translation Enhancements
- Translation Best Practices
- Configurations and the Configuration Browser
- AEM FAQs
- Operations
- Dashboards
- Operations Dashboard
- Backup and Restore
- Data Store Garbage Collection
- Monitoring Server Resources Using the JMX Console
- Working with Logs
- Configure the Rich Text Editor
- Configure the Video component
- The Bulk Editor
- Configuring Email Notification
- Configuring RTE for Producing Accessible Sites
- The Link Checker
- Troubleshooting AEM
- Audit Log Maintenance in AEM 6
- Editor
- Managing Access to Workflows
- Using cURL with AEM
- Configuring Undo for Page Editing
- Proxy Server Tool (proxy.jar)
- Configuring for AEM Apps
- Administering Workflows
- Configuring Search Forms
- Tools Consoles
- Reporting
- Administering Workflow Instances
- Configuring Layout Container and Layout Mode
- Enabling Access to Classic UI
- Starting Workflows
- Configure the Rich Text Editor plug-ins
- Admin Consoles
- Security
- User Administration and Security
- User, Group and Access Rights Administration
- Security Checklist
- OWASP Top 10
- Running AEM in Production Ready Mode
- Identity Management
- Adobe IMS Authentication and Admin Console Support for AEM Managed Services
- Creating a Closed User Group
- Mitigating serialization issues in AEM
- User Synchronization
- Encapsulated Token Support
- Single Sign On
- How to Audit User Management Operations in AEM
- SSL By Default
- SAML 2.0 Authentication Handler
- Closed User Groups in AEM
- Granite Operations - User and Group Administration
- Enabling CRXDE Lite in AEM
- Configuring LDAP with AEM 6
- Configure the Admin Password on Installation
- Service Users in AEM
- Encryption Support for Configuration Properties
- Handling GDPR Requests for the AEM Foundation
- Content Disposition Filter
- Personalization
- eCommerce
- Integration
- Integrating with Third-Party Services
- Integrating with Salesforce
- Integrating with Adobe Target
- Integrating with Adobe Analytics
- Connecting to Adobe Analytics and Creating Frameworks
- Configuring Link Tracking for Adobe Analytics
- Mapping Component Data with Adobe Analytics Properties
- Configuring Video Tracking for Adobe Analytics
- HTTP2 Delivery of Content FAQ
- Troubleshooting your Adobe Campaign Integration
- SharePoint Connector Licenses, Copyright Notices, and Disclaimers
- SharePoint Connector
- DHTML Viewer End-of-Life FAQs
- Integrating with Adobe Campaign Classic
- Related Community Articles
- Integrating with Adobe Campaign Standard
- Flash Viewers End-of-Life Notice
- Integrating with Adobe Creative Cloud
- Integrating with Adobe Dynamic Tag Management
- Opting Into Adobe Analytics and Adobe Target
- AEM Portals and Portlets
- Integrating with Dynamic Media Classic
- Troubleshooting Integration Issues
- Integrating with BrightEdge Content Optimizer
- Best Practices for Email Templates
- Catalog Producer
- Integrating with Silverpop Engage
- Integrating with Adobe Campaign
- Integrating with ExactTarget
- Analytics with External Providers
- Integrating with the Adobe Marketing Cloud
- Manually Configuring the Integration with Adobe Target
- Prerequisites for Integrating with Adobe Target
- Adobe Classifications
- Solutions Integration
- Target Integration with Experience Fragments
- Best Practices
- Content Management