Multilingual Plone Site

Web sites have increasingly become more sophisticated in how they distribute information to millions of people all around the world. The challenge is how to ensure those sites get information out in a timely, efficient manner to a number of different audiences - even in different languages - all without sacrificing content and the dynamic capability of the site. Internationalizing your web site is not as simple as translation the text from one language into another. The problem is that web sites are rarely just developed and frozen; they evolve over time, often so fast that by the time the translation team finishes with a particular snapshot, the production team might already have a newer version.

Plone was one of the first Content Management systems to support multiple user interface languages transparently out-of-the-box, and currently ships with over 40 languages enabled by default. This happened in large part due to the pioneering work of Plone collaborators all around the world. Plone has been an international system from day one.

LinguaPlone

product. With LinguaPlone, you can easily maintain several different translations of the same page, have workflow processes that notify the translators when the original document is updated - all in an easy-to-use and attractive package. LinguaPlone enables your existing content for multi-lingual purposes. It helps you to create and manage translations of the content and what is more easily navigate with different language versions of the same content. There are a lot of important sides to running a successful multilingual web site or intranet, and LinguaPlone product can help you get the best out of the software and your existing processes.

There are several methods of organizing multilingual Plone site - template switching, master and subordinate sites, and parallel sites. One of the ways is creation of a separate folder for each language. What you need is to create as many folders as many-lingual your site is going to be (i.e. content cam be scattered into the corresponding language folders - ru, de, en etc. (e.g. http://plone-site.com/de, http://plone-site.com/en/)).

The process of translation a content from one language into other ones (here - German and Ukrainian) looks this way:

• Add new folders 'De' and 'Ukr' into the root of the Plone site;
• Now translate all the content one by one into these folders:
  the task is done this way: make sure LinguaPlone is active on your site, then go to the toolbar button 'translate into', click on it and choose 'deutsch', and then 'українська':
  
  
  1. Translation of Folders:
     when a root Folder is translated with LinguaPlone, the translated version is automatically put into the root. What you have to do is to cut the translated version and to paste it into the corresponding 'De' or 'Ukr' folder. Than the problem with shortnames usually emerges. Shortnames are generated automatically on the basis of their titles. And for every Folder - you will have to rename all the shortnames to make them the same as in the root.
  2. Translation of Documents:
     when a Page from initially translated folder is translated, it is put into the corresponding translated folder, so the only difficulty with it is again to rename the shortname for every page.
  
  

When we copy pages and folders, connection between documents in different languages is not lost, a user can easily shift between languages.

One more thing worth mentioning is what happens when we add a completely new document to multilingual site. In Site Setup -> Language Settings you choose the default language of the site, and some other allowed languages. When a new item is added it is created in neutral language, and is visible in both default and other allowed languages. Then you can translate this document from the default language into the other ones.

(Plone 3.0). The choice is between:

• drop-down menu use (this is the preferred method);
  
  

• flags use (but use of flags is not very convenient, as flags represent countries, not languages. Numerous countries use the same language as another country, and numerous countries have more than one official language, so the mixture may appear).
  
  

Example of a Multilingual Site

product - the tool that helps to manage and maintain multilingual content.

1. English version was put into the root of the site - http://www.offshorecompany.com/
2. then we create a folder 'ru' - a Russian version of the site - http://www.offshorecompany.com/ru. In 'ru' folder the content was translated into Russian but the shortnames remained the same as in the English version.