The main difference between a multilingual solution and a simple multi-language system is the ability to localise for specific dialects of a language. For example, an organisation may have a website for France and a website for Canada. Both may be in French but the language may be slightly different on each site and the messages may need tuning. Our solution allows you to set this up with ease.
Primary and secondary sites
The multilingual module allows us to synchronise the content from a primary language site to any number of secondary language site. A secondary can also become a primary if required. A simple diagram of a typical synchronisation is shown below.
When you create content in the primary version, a direct copy of the content is created in the secondary. You may have any number of secondary or language variations.
The multilingual workflow
When new content is created in the primary it is automatically replicated in the secondary. The CMS alerts the secondary editors and flags the new content with an indicator to say that the content has not yet been translated.
When changing and translating the content, they will update different parts of the data including metadata, properties and content. Each of these different attributes have separate change tracking so, unless you specifically change them, the next time the primary is updated the content or metadata that you did not originally change will update as per the primary.
The editors on the secondary site will be able to see all the content that is awaiting translation. They can choose to translate and publish or even to exclude content from publication on their site. This is a particularly important issue when you may have news articles or even products that are just not relevant to a particular language or country.
When you're navigating a secondary site, we have simple indicators to show which content is up-to-date and translated, and indicators to show which content still needs work or attention. This means you can always see and understand the status of your content.
The translation queue
The translation queue shows you all content that requires attention, ordered by priority. When you create content, the system estimates the translation due-date based upon the word count of the content. If the estimated time is longer than you require, you can request an urgent translation which will push content higher up the translation queue. This gives you the ability to set dates for translators.
There is an option to force the workflow to only publish a page once it has been translated into all languages required.
Working with a translation provider
The traditional means of entering translated content is to use the standard Contensis user interface. We understand that in some cases, you may be out-sourcing your language translation issues to a third party.
We provide a simple means of achieving full integration with translation companies using our API.
As soon as content is ready for translation, the system can integrate with their systems so they can translate the content and get it back into Contensis in a fully-automated fashion.
Multilingual is a chargeable module. View our pricing page for details.