[z3-five] Re: some i18n issues

[Philipp von Weitershausen]

yuppie wrote:
> Currently two basic zope3 i18n features don't work with Five:
> 
> - TAL handles MessageIDs like normal strings, loosing domain and mapping
> data
> 
> - self.request.locale is not available

This is something that I would like to bring to Zope 2.9. It would be
very hard to do from Five. But as you said, let's leave this issue aside
for now.

> I didn't have a closer look at the second issue, so this is about
> MessageIDs:
> 
> On the yuppie-tal-backports branch in the Zope repository is a fix for
> this. Don't know if we can get the fix in the Zope 2.8.1 release, but at
> least the fix is not available in Zope 2.7.

There's only so much we can do to support Zope 2.7. Martijn and I agreed
that Five 1.1 will be the last version to support Zope 2.7 and its
old-style ExtensionClass. It might even be the last version to support
Zope X3 3.0.

> On the yuppie-i18nfixes branch in the Five repository is a workaround
> for forms that translates 'label' and 'update' *before* they are passed
> to the page template. This workaround works without the TAL fix but is
> not necessary with the fixed TAL.
> 
> 
> So I don't know what to merge where:
> 
> 1.) Should we try to get the TAL fix in Zope 2.8.1?

+1. This solves the problem at its root. And it should be considered a
bugfix because Zope 2.8 claims to integrate Zope X3.

> 2.) Should we monkey patch TAL in older Zope versions?

-0. From looking at the diff of your change, the monkey patch would
probably be huge and therefore risky. So, unless someone really needs
this in Zope 2.7 (I'm mainling talking about the Nuxeo guys here because
they seem to be running a lot of Five in action), we should skip this.

> 3.) Do we need the workaround? And if yes, in which five versions?

Being the most limited solution, I think the workaround in Five should
be the last option.

> Besides that I propose to set up 'zope' domain translations by default.
> Five forms need that, and I don't think products using forms should be
> responsible for setting up that domain.

+1


Thanks for looking into this.

Philipp