Yes, that's what I'm doing now. Right now it's sort of tied to the TemplateLoader, though - at least the way deform uses Chameleon. So what I do is keep the zpt renderers around and assign to renderer.loader.kwargs['translate'] per request - not exactly a nice API to do that.
On Thu, Aug 11, 2011 at 7:07 PM, Malthe Borch <[email protected]> wrote: > On 11 August 2011 14:43, Robert Forkel <[email protected]> wrote: >> ok. i got chameleon 2.3 to work. but I still think I have to keep >> locale specific TeplateLoaders around to make caching work, because >> the registry key for a template does still not take locale into >> account, thus may retrieve a template with the wrong translator. >> Am I missing something? > > I think the idea is that the translation function is added at render > time by keyword argument to the template render function. In other > words, it's dynamically set for each rendering. > > \malthe > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
