[Zope3-dev] Re: Use case not covered for translation of message ids

[Stephan Richter]

On Tuesday 28 September 2004 10:10, Jim Fulton wrote:
> As I've mentioned before, we could redefine message ids so that they are
> not strings.  This would be a huge change that it would take time to
> understand all of the implications of.  It *might* be a good change.  I'll
> admit that I feel some discomfort in using message ids in schemas.  I
> question whether the dubious benefit of implicit translation justifies such
> a huge change.  What *is* the benefit of implicit translation?  Does it
> make anything possible that isn't possible now?

Shrug, I hope this never happens. Every other Open Source I18n system I know, 
uses message ids the same way we do. They do not translate in the same way 
usually, since they are simple applications where there is only one user with 
one locale, so they are free to translate immediately in the app and do so. 
So in other applications making something a message id translates 
immediately. Maybe this is the reason it feels so natural for Godefroid and 
Martijn to think about automatic translation. I like Zope 3's idiom though, 
which separates the declaration of something being translatable and actually 
translating something.

Regards,
Stephan
-- 
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training