I18N content

hi folks !

I've just commited some changes to have I18N content in archetypes.
The current implementation holds translation in the field. The available
i18n fields are : 

I18NStringField
I18NMetadataField
I18NFileField
I18NTextField
I18NLinesField
I18NImageField

There is still some works to do for :
  _ UI (I've just quickly modified templates to be able to switch from a
    language to another)
  _ catalog interaction : how to correctly index multiple translation
    for the same field
  - I18N Vocabulary
  _ translation management (get missing / outdated translations)
, but the current implementation should works.

For information, I've done that work after some time playing with I18NLayer
which has some good ideas but is IMHO unusable as soon as you have more 
than a few objects. Navigation in zope/plone objects is not so easy in 
general and having a folderish wrapper on each object of a site is really 
a pain for maintenance. Another problem with I18NLayer is the
translation of folderish objects. ALl that make me decide to implements a 
field oriented solution in archetypes.

feedback welcome !

-- 
Sylvain Thénault                               LOGILAB, Paris (France).

http://www.logilab.com   http://www.logilab.fr  http://www.logilab.org



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php