Personal tools
You are here: Home Produkte Content Management mit Plone Informationen zu Plone Plone Module – Basis-Installation LinguaPlone – Managing international content with Plone
Document Actions

LinguaPlone – Managing international content with Plone

LinguaPlone is a tool to manage and maintain multilingual content that integrates seamlessly with Plone.

What is LinguaPlone

LinguaPlone aims to be the multilingual/translation solution for Plone, and achieves this by being as transparent as possible and by minimizing the impact for existing applications and Plone itself.

LinguaPlone is transparent to your content

  • It utilizes Archetypes references to do the translation, and all content is left intact both on install and uninstall - thus, it will not disrupt your content structure in any way. It also works with WebDAV and FTP.

Every layout or content structure works

  • LinguaPlone doesn't require a particular hierarchy of content, and will work with any layout of your content space.

Some benefits of LinguaPlone (I)

  • Totally transparent, install-and-go.
  • Each translation is a discrete object, and can be workflowed individually.
  • This also means that it works with WebDAV and FTP.
  • Translations are kept track of using AT references.
  • You can multilingual-enable your types without affecting their operation outside LinguaPlone.

More benefits of LinguaPlone (II)

  • Even if you uninstall LinguaPlone after adding multilingual content, all your content will be intact and will work as separate objects! The only thing that will be inactive is the references between the objects. If you re-install it, they will be back. It's very non-intrusive.
  • Supporting multilingual capabilities is a 4 (!) line addition to your Archetypes class, and does not alter the functionality of the class when used outside LinguaPlone.
  • Fully integrated with ATContentTypes, so the basic content types are translatable.

Special benefits of LinguaPlone (III)

  • Supports language-independent fields (example: dates, first/last names) for fields you want to be the same across translations, and updated in all languages if one of them changes.
  • Uses the notion of Canonical versions, so you can do interesting things with workflow, like invalidate all translations of a document when the master copy has changed.

Current release: LinguaPlone 0.9.0

  • Released Jun 17, 2006 — tested with Plone 2.5, Plone 2.1.3, Plone 2.1.2, Plone 2.1.1
  • Updated to work with Plone 2.1.3 and Plone 2.5, with improved image/file translation. Provides a migration script if you are coming from LinguaPlone 0.9-beta or earlier and have existing content.

Product page:

More detailed infos provides the Lingua-Plone FAQ Presentation


Design and development
Plone Solutions (Alexander Limi, Dorneles Treméa, Geir Bækholt, Helge Tesdal, Stefan H. Holek)
Original design idea
Objectrealms (Benjamin Saller, Kapil Thangavelu)
Funding and deployment, initial version
Oxfam International
Additional funding/sponsorship
Hitotsubashi University in Tokyo, Centre for New European studies (Jonathan Lewis)
Funding Plone 2.0.x compatibility
Zope Japan Corporation (Takeshi Yamamoto)

Also many thanks to

Simon Eisenmann
For doing the hard job of the first implementations (I18NLayer) we had to learn from before doing this.
Learning Lab Denmark
For contributing and sponsoring the experience needed to build a multilingual solution.
Nate Aune
For always pushing for the better solution and making us realise LinguaPlone had to be built.
Jodok Batlogg
For extensive testing, deploying and feedback.
Sasha Vincic
For testing and expanding and making cool new stuff happen with LinguaPlone, XLIFF import/export in particular.