Localisation Framework - Giving you the chance to keep the labels relevant
Contensis has been designed with localisation in mind from the ground up. In essence, our localisation allows you to override the text of any element either in our CMS or in the web controls used in pages published by the CMS.
It is worth noting that localisation is very different to our multilingual support for content , although multilingual does use localisation.
This screenshot shows the localisation editor whilst editing the text for context sensitive help.
CMS Localisation
In this scenario you may simply want to change a piece of text in the CMS user interface. This is possible simply by clicking on the localisation editor, finding the relevant piece of text and then changing it.
If you want to, you can turn a setting on which allows you to see the ID for every localisation element without actually needing to search for the text.
Supporting a new language is no issue.
You may want your editors in the Japan office to use the CMS in a different language. If this is the case, they can simply switch the language at logon and use the relevant language.
If you do not have the language in question translated at a particular stage, then you can simply export an XML file and then re-import it into the system once translated.
Web Site Localisation
If you provide your website or sites in multiple languages it is probable that you are using standard Contensis web controls on the site. All of our controls are fully localised so that you can support any language required, and just like the CMS localisation, the localisation editor can be used to update existing localisation and import new languages.
7 languages out of the box.
When creating templates for localised sites, you can also use the localisation framework to insert localised elements within the templates; localised elements can be HTML if required.
This facility means that you can continue to leverage the power of the localisation framework through any custom development processes.