[Zope-CMF] keeping a customized CMF in sync with CVS-CMF

[Tres Seaver]

On Tue, 25 Sep 2001, Joachim Schmitz wrote:

> I don't think, that this is different. Or let me put it
> differently:
> 
> The only straightforward idea to make a german (only) CMF I see
> at the moment, would be to make a customized version of CMF.
> Which is hard to keep in sync with CVS-CMF.

In the future:

 - You should be able to build an "I18N-aware" skin, which uses
   something like gettext to indirect all "software" string
   literals through a message catalog.  This skin *must* be
   maintained separately;  the overhead of maintaining the
   message catalog, and of indirecting through it, are costs
   which not all users of the CMF will want to bear.

 - The CMF itself should expose all of the mechanisms on which
   the skins depend in I18N-friendly ways.  For instance, the
   paths for redirects should be computed using the types or
   actions tools;  the actions tool itself could probably be
   extended to work with the message catalog to internationalize
   all the action titles;  Message strings emitted from software
   (errors, confirmations, etc.) should use an indirection
   mechanism, etc.

We aren't there, but we have significant inducement to get there,
in the relatively near term.  One consequence of this design
choice should be to decrease the significance of the "generic"
skin (as currently shipped with CMFDefault/CMFDecor);  we may
need to move the non-presentation elements (the PythonScripts
which serve as POST targets) into a different layer, to make them
easier to reuse across skins.

> On Tue, 25 Sep 2001, Paul Everitt wrote:
> 
> >
> > The issue of localization is different.  I thought you wanted to
> > signicantly change the templates (different CSS, etc.)
> >
> > Apparently there are two schools of thought in the land of Zope about
> > localization.  Until some consensus emerges, I'm not sure how to comment.
> >
> > Can you describe how a different, non-Zope system (such as PHP-Nuke)
> > accomplishes localization in web software, and whether you consider it
> > to be successful on the issue of keeping in synch?
> >
> > --Paul
> >
> > Joachim Schmitz wrote:
> >
> > > thanks everybody for the good advises, they mainly confirmed to me what I
> > > had suspected. There is no easy way to do it :-(.
> > >
> > > Now the big question, how does one build a localized say german version
> > > or even a multilingual version of CMF, and keep it in sync with the CMF ?
> > >
> > > I think, if that is not easely doable, or better a builtin feature, then
> > > the CMF will be a dead end for the no-english market.


Tres.
-- 
===============================================================
Tres Seaver                                tseaver@zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com