[Zope-CMF] Zope component model and CMF

[Robert Rottermann]

I know translation an component model are two separate things. Somehow.
Both are related in that they need a rethinking of how things are done.
And that's what you are doing (and which I hope can be extended "ein wenig")

> task.  Note, however, that there is only one place (the portal_actions
> tool) that is not fully localizable already.  Have you seen the German
> translation of the CMF?
Here I do not agree. Translation and customization are two different things.
Although skins can be misused for translation they (to my mind) are here for
customization. It just makes no sense to throw all modules of the divers
skins on one big translated heap. Even if you do so you still have lots of
untranslated elements (result of raise statements, many hardcode strings,
descriptions of portal_types ...)
Yes I did look at the German skin. It does stress my arguments.

Robert

----- Original Message -----
From: "Shane Hathaway" <shane@digicool.com>
To: "Robert Rottermann" <robert@redcor.ch>
Sent: Thursday, July 05, 2001 11:57 PM
Subject: Re: [Zope-CMF] Zope component model and CMF


> On Thu, 5 Jul 2001, Robert Rottermann wrote:
>
> > I would be showing off pretending I did understand every detail. I
probably
> > have to read some discussion on your paper. So I can not yet talk about
its
> > technicalities.
> > However there is something I am missing badly:
> > Support for translating to non English languages.
> > I will prepare (with help of others) a proposal what we from the non
English
> > part of the world need.
> > I believe it will be a small effort for you to implement and of a great
help
> > to us from the rest of the world.
>
> The translation task is important, but independent of the component model
> task.  Note, however, that there is only one place (the portal_actions
> tool) that is not fully localizable already.  Have you seen the German
> translation of the CMF?
>
> Shane
>
>