Multilingual Module
Giving you the ability to manage and deliver content for multiple countries or targets in multiple languages and dialects.
When we think about multilingual, there are many aspects to consider. Here we are not talking about the specifics of localisation, which is straightforward, what we are talking about here is the ability to manage and deliver content for multiple countries or targets in multiple languages.
There is a very subtle difference between a true multilingual solution and a simple multi-language system. The main issue we are talking about is the ability to localise for specific dialects of a language. As an example, an organisation may have a website for France and a site for Canada. Both may have a French version 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.
How we achieve content delivery to multiple countries in multiple languages, requires a number of specific features.
Language synchronisation allows us to synchronise the content from a master language site to a slave language site with a full multilingual workflow and change tracking. A slave can also become a master if required. A simple diagram of a typical synchronisation is shown below.
This diagram demonstrates how language synchronisation could be configured; note the French site becomes the master for the Canadian French site
The first time a piece of content is approved in the master version, a direct copy of the content is created in the slave (there could be any number of slaves or language variation). When this happens, the system stores an indicator that says the content has not yet been translated.
You will understand the status of your content at all times
When workflow kicks-in, the slave site editors and contributors, lets say the France site in French for sake of the argument, will now start changing the content.
When changing and translating the content, they will update different parts of the data including, for example, meta-data, properties and content. Each of these different attributes have separate change tracking so, unless you specifically change them, the next time the master is updated the content or meta-data that you did not originally change will just update.
This screenshot shows a typical report, similar to the translation queue. For more information on other reports available see the
reports section.
The editors on the slave 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.
This process simplifies the issues around dialects and content produced for different countries in similar languages.
Language synchronisation is just a part of our overall content synchronisation and blue-printing model.
Making the process of using the multilingual features easy for your editors is a challenge, but a challenge we have taken up and produced effective clear solutions through the user interface.
This screenshot shows a typical report, similar to the translation queue. For more information on other reports available see the
reports section.
The starting point for many translators is their translation queue. This queue shows you all content that requires attention ordered by priority. It is worth noting that editors can request urgent translation and target due-dates when creating content, which will push content higher up the translation queue
When you are navigating a slave 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.
There are many configurable options for language variations, including the functionality to hold back publishing of language variations until all variations have been translated. This is just one example of the many options available.
This screenshot shows the screen you will see after submitting a master language variation for approval
When you are creating content that will need translation you can request urgent translation and set a due-date; we have shown this functionality in the screenshot.
The system also estimates the translation due-date based upon the word count of the content. If the estimated translation time is longer than you desire, then you can request an urgent translation.
This gives you the ability to set a due-date for translators, and it will appear in a higher position in the translation queue.
Typically, this is only an issue when you cannot publish the master until the slave is published; perhaps in an English/Welsh situation, for example, or a product release.
The traditional means of entering translated versions of content is to use the standard Contensis user interface. In some cases, however, 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, if set-up, the system will fully integrate with their systems, so they can translate the content and get it back into Contensis in a fully-automated electronic fashion.
Employing a third party company to carry out your translation can happen in a totally seamless manner, without any manual intervention.
All you need to do is create the master and let them take care of the rest.