Stephan Richter wrote:
On Sunday 08 May 2005 14:45, Philipp von Weitershausen wrote:
Also, please note that it is *very* difficult to implement new
attributes in TAL, so someone would have to sign up implementing this; it
would certainly not be me.
Now *that's* a valid point. But it touches a probl
Philipp von Weitershausen wrote:
Stephan Richter wrote:
On Friday 06 May 2005 10:11, Dmitry Vasiliev wrote:
Opinions?
Dimitry, I am sorry. There was already a papal's edict on the issue:
http://mail.zope.org/pipermail/zope3-dev/2004-September/012186.html
That means, message ids must be translated
Philipp von Weitershausen wrote:
Dmitry Vasiliev wrote:
- Should we do automatic translation for msgid's inside a TALES
expression?
IMO we shouldn't do automatic translation at all.
How then we want to translate TALES expressions like "some text ${msgid}"?
The only way now is explicit translate()
On Sunday 08 May 2005 14:45, Philipp von Weitershausen wrote:
> > Also, please note that it is *very* difficult to implement new
> > attributes in TAL, so someone would have to sign up implementing this; it
> > would certainly not be me.
>
> Now *that's* a valid point. But it touches a problem that
On Sunday 08 May 2005 14:45, Philipp von Weitershausen wrote:
> > Also, we need a solution now, not one that goes through the proposal
> > process first.
>
> If the future of the Zope 3 development process means that for every
> thing we discuss a solution needs to be found *that* instance, then I
Stephan Richter wrote:
On Sunday 08 May 2005 10:01, Philipp von Weitershausen wrote:
Thoughts?
I don't mind the two semantics. I just think that if tal:content and an
explicit message id in i18n:translate is specified, an error should be
raised. I bet you it does already.
Nope. I added a ZPTPage
On Sunday 08 May 2005 10:01, Philipp von Weitershausen wrote:
> Thoughts?
I don't mind the two semantics. I just think that if tal:content and an
explicit message id in i18n:translate is specified, an error should be
raised. I bet you it does already.
Also, we need a solution now, not one that
Stephan Richter wrote:
On Friday 06 May 2005 10:11, Dmitry Vasiliev wrote:
Opinions?
Dimitry, I am sorry. There was already a papal's edict on the issue:
http://mail.zope.org/pipermail/zope3-dev/2004-September/012186.html
That means, message ids must be translated explicitely using i18n:translate.
Dmitry Vasiliev wrote:
Stephan Richter wrote:
On Friday 06 May 2005 12:11, Godefroid Chapelle wrote:
Stephan also have pointed that automatic translation doesn't allow
somebody to disable translation on purpose for some piece of content.
Right. That's one reason why it's bad.
Can someone explain
Dmitry Vasiliev wrote:
Philipp von Weitershausen wrote:
Godefroid Chapelle wrote:
Jim, some other people and I argued that this kind of automation is
bad anyway and instead of introducing more translation magic, TAL
shouldn't do any automatic translation at all.
So, in my opinion, do_insertText_
Stephan Richter wrote:
On Friday 06 May 2005 12:11, Godefroid Chapelle wrote:
Stephan also have pointed that automatic translation doesn't allow
somebody to disable translation on purpose for some piece of content.
Right. That's one reason why it's bad.
Can someone explain this use case a bit deepe
Philipp von Weitershausen wrote:
Godefroid Chapelle wrote:
Jim, some other people and I argued that this kind of automation is
bad anyway and instead of introducing more translation magic, TAL
shouldn't do any automatic translation at all.
So, in my opinion, do_insertText_tal() should raise a
D
On Friday 06 May 2005 12:11, Godefroid Chapelle wrote:
> >> Stephan also have pointed that automatic translation doesn't allow
> >> somebody to disable translation on purpose for some piece of content.
> >
> > Right. That's one reason why it's bad.
>
> Can someone explain this use case a bit deeper
Godefroid Chapelle wrote:
Jim, some other people and I argued that this kind of automation is
bad anyway and instead of introducing more translation magic, TAL
shouldn't do any automatic translation at all.
So, in my opinion, do_insertText_tal() should raise a
DeprecationWarning if it encounter
Philipp von Weitershausen wrote:
Dmitry Vasiliev wrote:
Recently Stephan and me have a discussion on the IRC about purpose of
i18n:translate attribute for tags with dynamic content through
tal:content attribute. Stephan pointed out that i18n:translate in this
case is just a marker for call trans
Dmitry Vasiliev wrote:
Recently Stephan and me have a discussion on the IRC about purpose of
i18n:translate attribute for tags with dynamic content through
tal:content attribute. Stephan pointed out that i18n:translate in this
case is just a marker for call translate() later. But later I discove
16 matches
Mail list logo
