The Default Translation Service
AEM Communities includes a trial license for a default translation service enabled for several languages.
When creating a community site, the default translation service is enabled when Allow Machine Translation
is checked from the TRANSLATION subpanel.
Global Translation of UGC
When a website has multiple language copies, the default translation service does not recognize that UGC entered on one site may be related to UGC entered on another. This is true when the UGC is generated by the same component (the language copy of the page containing the component).
It is similar to groups of people discussing a topic. They are unaware of comments that are made in groups other than their own, as compared to everyone in a large group participating in one conversation.
If “one group conversation” is desired, it is possible to enable global translation across a website with multiple language copies, such that the entire thread is visible regardless from which language copy it is being viewed.
For example, if a forum was established on the base site, language copies created, and global translation was enabled, a topic posted to the forum made in one language copy would appear in all language copies. The same would be true for any replies, regardless of from which language copy the reply was entered. The result would be that the topic and its entire thread of replies would be visible regardless of from which language copy the topic is being viewed.
Translation Integration Configuration
To create a Translation Integration, which integrates a Translation Service connector with the web site on the author instance:
-
Sign in as an administrator
-
From the main menu
-
Select Tools
-
Select Operations
-
Select Cloud
-
Select Cloud Services
-
Scroll down to Translation Integration
-
Select Show Configurations
-
Select
[+]
icon next to Available Configurations so you can create a configuration.
Create Configuration Dialog
-
Parent Configuration
(Required) Typically leave as default. Default is
/etc/cloudservices/translation
. -
Title
(Required) Enter a display title of your choosing. No default value.
-
Name
(Optional) Enter a name for the configuration. Default is a node name based on the Title.
-
Select Create
Translation Config Dialog
For detailed instructions, see Creating a Translation Integration Configuration.
-
Sites tab: can leave as defaults.
-
Communities tab:
-
Translation Provider
Select the translation provider from the drop-down list. Default ismicrosoft
, the trial service. -
Content Category
Select a category that describes the content being translated. Default isGeneral.
-
Choose A Locale…
(Optional) By selecting a locale for storing UGC, posts from all language copies appear in one global conversation. By convention, choose the locale for the base language for the website. ChoosingNo Common Store
disables global translation. By default, global translation is disabled.
-
-
Assets tab: can leave as defaults.
-
Select OK
Activation
The new translation integration cloud service must be activated to the Publish environment. When associated with a web site, if not yet activated, the activation workflow prompts to publish this cloud service configuration when the page with which it is associated is published.
Managing Translation Settings
User Preference
User Profile
All Communities Sites provide a user profile that signed-in members can edit to identify themselves to the community and to set their preferences.
One such setting is whether to always display community content in their preferred language. By default, the setting is not set and defaults to the system setting. The user can change the setting to either On or Off to override the system setting.
When pages are automatically translated into the user’s preferred language, the UI for showing the original text and improving the translation are still made available.