A short presentation about Plone's multilingual approach. Created for CMSGarden at CeBIT 2014.

1. Multi-Language Support in Plone

2. Your Speaker
● Kees Hink
● Consultant at Four
Digits, Arnhem
● Plone since 2008,
Core contributor
● twitter.com/keeshink

3. Translation of User Interface
● 62 Languages
● Mechanism can be
chosen:
– User preference
– Cookie
– Browser setting
– Fixed

4. Content in multiple languages
It's never
simple.
●
Where to “put”
translations (URL)?
● If no translation: do
we fallback? To what?
●
How to store relations
between translations?
●
Different permissions
on translations?
● Different workflow
state for translations?
●
SEO

5. How Plone does it
● Add-on (not in
Plone core)
● Since Plone 4.1:
plone.multilingual
● Root language
folder (ie. /en,
/de, etc.)
● Language
neutral content

6. Side by side translation

7. Language-independent fields

8. Translation map
● English ● Deutsch

9. Missing Translations
● Show which
languages are
missing
● Show which
languages are there

10. Google translation service
integration
● Uses Google Translation Service to translate
fields
● Requires paid Google API key ($20 / 1M chars)

11. Questions?
● These slides will be
on Slideshare.com
● See twitter/keeshink
for the link