You are here: Home Plone products Products.LinguaPlone

Products.LinguaPlone (4.0.2)

by cms last modified 2011-02-03
Released on 2011-01-26 by Jarn, Geir Bækholt, Wichert Akkerman, Dorneles Tremea, Stefan H. Holek, Helge Tesdal, Alexander Limi for Plone 3.0, Plone 4.0 under GPL - GNU General Public License available for All platforms.
Software development stage: stable
Manage and maintain multilingual content that integrates seamlessly with Plone.

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.

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.

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

Some benefits of LinguaPlone

  • 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.
  • 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.
  • 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.
Document Actions
Powered by Plone