i18n not working at all

[pylons]

i18n not working at all

[rockyburt]

Well there's still some context missing, like are you using the same message domain in both raw code and the jinja2, etc. But regardless, I just committed a demo app that shows how to use i18n:
https://github.com/Pylons/pyramid_jinja2/tree/master/pyramid_jinja2/demo

To run the demo locally simply type:

python -m pyramid_jinja2.demo.__init__

The resulting web page will demonstrate translating english to french.

[packardb]

I want to use the same message domain for both raw code and jinja2 (casting). Also, i use render_to_response() in my view to render the template however this doesn't seem to be the problem.

[rockyburt]

As of pyramid_jinja2 0.6.2 the only domain checked during jinja2 rendering is "messages". So the real issue here is that you want to use a domain other than "messages" ?

[packardb]

This is bad, it's the only test i haven't done yet (using messages instead of my app's name as domain). I don't really mind using messages, but it would be nice if pyramid_jinja2 would somewhat "inherit" the domain from somewhere ... Until then, i'll use messages. It really sucks because setup.cfg is created with appname as message domain

[rockyburt]

Ok so I just made some more commits for this stuff... it's now possible to override the default domain with the 'jinja2.i18n.domain'.
config = Configurator(settings={'jinja2.i18n.domain': 'myappname'})

I've also updated the paster template that comes with pyramid_jinja2 to setup the default domain to be the name of the app for use with jinja2 templates. Can you try latest git clone to see if it works for you?

[rockyburt]

As soon as we close this issue I will be releasing a new version of pyramid_jinja2 so please confirm if the changes I made help you do what you need.

[packardb]

Seems to be working as expected. Thank you.