Website Translation Technology
Website translation technology has evolved with the complexity of the tasks. Modern web applications targeting global markets are dynamic, fast-growing, and include thousands of pages. eCommerce and travel apps are especially challenging due to huge volume of content and frequent updates. They require real-time translations on an unprecedented scale. This can only be accomplished via integrations with translation management systems.
There are multiple ways to handle multilingual websites:
- Single site with subpages and a language selector (yoursite.com/fr/page, yoursite.com/de/page)
- Multisite means deploying separate websites for each language under a new domain (yoursite.com, yoursite.de, yoursite.fr). These sites are all connected to the same database and use the same style.
- Translation proxy or a JavaScript website translation system.
Multilingual Content Management Systems (CMS)
Multilingual CMS play a critical role in the localization of online content. They support publishing content in multiple languages and create language switchers with links between different language versions of the same pages. Moreover, they streamline management of multilingual content and its production. Popular website CMS such as Drupal and Joomla have basic functionality embedded in the system, which can be improved with extensions and plugins. WordPress, Typo3, and the popular game design platform Unity do not come multilingual out of the box, and need plugins to support multiple languages.
Features of Multilingual CMS:
- Change detection helps translate changes and keep language versions synced
- Customizable and synchronized non-translatables (number formats, date, currency)
- Translatable taxonomies and category names
- Support for XLIFF
- TMS integration (automated import and export)
- Provide local themes or sub-sites
- Image localization
Connectors
Connectors are preconfigured integrations of translation tools with multilingual CMS. They enable website content managers to send pages for translation from the CMS to TMS, and get translations instantly published, all without manual export and import. Translation management systems have their own connectors and can get integrated with other software with middleware such as Clay Tablet and iLangl.
Below are examples of connectors for particular TMS:
Wordbee |
XTM |
Cloudwords |
Memsource |
---|---|---|---|
Adobe Experience Manager |
Adobe Experience Manager |
Adobe Experience Manager |
Adobe Experience Manager |
Censhare |
Drupal |
Drupal |
Drupal |
Drupal |
Sitecore |
Oracle Web Center |
GIT |
Episerver |
WordPress |
Veeva Vault |
WordPress WPML |
Joomla! |
JIRA |
Sitecore |
|
Kentico |
Zendesk |
SDL Web |
|
SDL LiveContent |
Microsoft Team Foundation Server |
WordPress |
|
SDL Tridion / Web |
Git |
HubSpot |
|
Sharepoint |
SDL LiveContent |
Marketo |
|
Sitecore |
Salesforce service cloud |
Oracle Compendium |
|
TYPO3 |
Oracle service cloud |
Oracle Eloqua |
|
Umbraco |
RSuite |
Salesforce ExactTarget |
|
WHATS'On |
easyDITA |
||
WordPress |
InDesign |
||
DITAworks |
|||
Ovitas |
|||
muldrato |
Translation Application Programming Interface (API)
Translation API is a set of commands that allows two systems to communicate. In website translation, APIs are commonly used to pull files from CMS to TMS, and push back a translation. Because of the incredible variety of CMS (more than 2,000 have been developed), it is not possible for translation systems to cover all important systems with preconfigured plugins. A well-developed and well-documented Translation API makes it easy to integrate popular translation tools with content systems. Translation APIs are the focus of the GALA-supported TAPICC initiative.
Translation Proxy
Translation proxy is a website localization technology that functions a bit like putting a new tablecloth on the same old table. Proxy creates a new “layer” on top of the website where it displays translations. The translations are stored separately on the proxy service’s cloud. Only the original website exists. This approach simplifies page updates in multiple languages, eliminates the need for the CMS to support multilingual, and the need for subpages. Most proxy solutions offer an in-context editor to translators. Proxy is easy to implement and use, however there are downsides including reduced SEO capabilities and dependency on proxy platform provider.
Examples of Companies with Website Translation Proxy:
- Smartling
- EasyLing
- LinguaSol
- Lionbridge
- Sajan SiteSync
- Transperfect GlobalLink OneLink