#41: Make Plone more aware of and prepared for multilingual content

Contents
  1. Motivation
  2. Proposal
  3. Implementation
by Alex Limi — last modified Jan 21, 2010 07:29 AM

Plone needs a native ITranslatable interface for use by the different multilingual solutions.

Proposed by
Helge Tesdal
Seconded by
Alexander Limi
Proposal type
Architecture
State
completed

Motivation

Plone is already very good at handling multilingual UI. There are a lot of translations available, and multilingual is one of the features that helps us sell Plone. Now is the time to up the ante by making Plone more aware of and better prepared for handling multilingual content.

We need different multilingual content implementations to use the same interface to be able to switch between them and easily plug into sites. We don't want multilingual content in the core of Plone, but we want to make it easier to integrate.

Proposal

Make Plone more prepared for and aware of multilingual content by adding an interface for translatable content.

Implementation

Add ITranslatable interface to Plone. The interface is originally suggested by Ben Saller, and is used for handling translatable content. It has methods for retrieving translations, handling canonical translations and so on. It can currently be seen in LinguaPlone and the psol-redux branch of I18NLayer.

Comments (0)