raptus.multilanguageplone 0.5

adding multilanguage support to default plone content types

Introduction

raptus.multilanguageplone provides a simple way to have internationalization on content objects. raptus.multilanguageplone isn’t meant to be a fully fledged multilanguage tool, like LinguaPlone. Translation is done directly in the edit view of a content type and provides a widget to use google’s translation api to translate the different fields.

Unlike LinguaPlone raptus.multilanguageplone doesn’t create an object for each translation, it stores the translation on the object itself and therefor doesn’t support translation workflows and language aware object paths.

Changelog

0.5 - (2010-01-26)

• setting schemata for title, description and text fields

0.4 - (2010-01-25)

• Fixed document, event, newsitem and topic extenders (missing primary field markers)

0.3 - (2010-01-21)

• Fixed file, image and link extenders (missing primary field markers)

0.2 - (2009-12-02)

• Added README.txt

0.1 - (2009-10-30)

• Initial release