Re: [pylons-devel] i18n state of affairs

2017-02-09 Thread Michael Merickel
On Thu, Feb 9, 2017 at 6:02 AM, Hans-Peter Jansen wrote: > There's one decision to make as the next step: > > Does the involved parties agree to leave the translation procedures > somewhat > outside the normal workflow and supply a i18n.sh script, accompanied with a > default

Re: [pylons-devel] i18n state of affairs

2017-02-09 Thread Hans-Peter Jansen
On Mittwoch, 8. Februar 2017 15:41:29 Michael Merickel wrote: > One more thing I should add since you mentioned jinja2 and you may not have > seen this yet: > > https://github.com/domenkozar/pyramid-cookiecutter-jinja2 > > The pyramid_jinja2 cookiecutter actually has some integrated i18n support

Re: [pylons-devel] i18n state of affairs

2017-02-08 Thread Michael Merickel
One more thing I should add since you mentioned jinja2 and you may not have seen this yet: https://github.com/domenkozar/pyramid-cookiecutter-jinja2 The pyramid_jinja2 cookiecutter actually has some integrated i18n support that works. We have thrown around some ideas on merging that into the

Re: [pylons-devel] i18n state of affairs

2017-02-08 Thread Hans-Peter Jansen
Hi Michael, On Mittwoch, 8. Februar 2017 12:22:27 Michael Merickel wrote: > On Wed, Feb 8, 2017 at 11:36 AM, Hans-Peter Jansen wrote: > > As a consequence, all these packages will depend on lingua then.. > > Do the packages actually need to depend on lingua? I see that your PR

Re: [pylons-devel] i18n state of affairs

2017-02-08 Thread Michael Merickel
On Wed, Feb 8, 2017 at 11:36 AM, Hans-Peter Jansen wrote: > As a consequence, all these packages will depend on lingua then.. > Do the packages actually need to depend on lingua? I see that your PR to deform doesn't add it, however deform expects it to in the dev environment