I18N content

Hey everybody !

At europython I've discussed with longsleep (author of I18NLayer) about
our respective I18N stuff and I'll try to explain some idea here. 
My implementation has some problems which are not easy to fix, 
catalog support and navigator's cache support. Those are correctly
supported by I18NLayer. So we think that we should implement a field
based internationalization using the I18NLayer. 
The base idea is to add a 'internationalizable' (or another shorter name:) 
attribute  to the field which may be set to true or false. Then in the 
accessor/mutator methods, if this attribute is false and if the object is
contained by an I18N layer, we would set/get it on the parent layer
instead of the object itself (otherwise everything would occurs as it is
currently). 

After that, I'ld like to add some ui stuff to hide the I18NLayer as much
as possible.

Opinions ? If no one complains, I'll revert my change and implement it
as described here.

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

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



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01