On Mittwoch, 8. Februar 2017 16:33:17 Michael Merickel wrote:
> I got the renderer working via the following diff. Unfortunately the
> translator is still not invoked which leads me to believe that there is
> something wrong with the i18n tags in the chameleon templates, but I don't
> know enough a
Hi Michael,
I will look into this right now.
Thanks for your care. Much appreciated.
Cheers,
Pete
On Mittwoch, 8. Februar 2017 16:33:17 Michael Merickel wrote:
> I got the renderer working via the following diff. Unfortunately the
> translator is still not invoked which leads me to believe tha
I got the renderer working via the following diff. Unfortunately the
translator is still not invoked which leads me to believe that there is
something wrong with the i18n tags in the chameleon templates, but I don't
know enough about chameleon to dive in there. Hopefully this was helpful
though.
d
I noticed that the renderer is not being used. The
`deform.Form.set_default_renderer(render)` is commented out. Uncommenting
it doesn't solve the problem but it's definitely an issue as the
zpt_renderer isn't actually being used as a result.
On Wed, Feb 8, 2017 at 4:14 PM, Michael Merickel wrote:
The issue is *usually* that the TranslationString instance hasn't been run
through `request.localizer.translate(..)`. Now, why not? I haven't dug in
to try and figure that out yet.
On Wed, Feb 8, 2017 at 3:55 PM, Hans-Peter Jansen wrote:
> Hi,
>
> I've used a good part of the day for getting i18
Hi,
I've used a good part of the day for getting i18n fixed in deformdemo,
but failed so far. :(
While all debug instrumentation show green lights, the translation
strings aren't picked up for some reason:
2017-02-08 22:49:07,717 DEBUG [deformdemo:63][waitress] locale_name from
default_locale