Hello Hanno,
Le 29/01/10 09:46, Hanno Schlichting a écrit :
On Fri, Jan 29, 2010 at 2:12 AM, Damien Baty damien.b...@gmail.com wrote:
Does anyone have feedback about i18n with BFG?
Personally I'd suggest to use Babel instead of zope.i18n. [...]
I will certainly take a look at it.
On Fri, Jan 29, 2010 at 10:09 AM, Damien Baty damien.b...@gmail.com wrote:
Le 29/01/10 09:46, Hanno Schlichting a écrit :
Personally I'd suggest to use Babel instead of zope.i18n. [...]
I will certainly take a look at it. Thanks. What is the status of your
zope.babel [1] package: any plan to
Le 29/01/10 10:17, Hanno Schlichting a écrit :
[...]
With BFG you don't have any of those backwards compatibility
concerns, so zope.babel won't make any sense in this environment.
I must be missing something, here. Let's restrict the use case to
template i18n. In my BFG app, I use Chameleon.
On Fri, Jan 29, 2010 at 11:09 AM, Damien Baty damien.b...@gmail.com wrote:
I must be missing something, here. Let's restrict the use case to
template i18n. In my BFG app, I use Chameleon. And Chameleon is pretty
tied up to zope.i18n (cf. chameleon.core.i18n), isn't it?
Ah right. Chameleon has
On 29 January 2010 11:51, Hanno Schlichting ha...@hannosch.eu wrote:
Ah right. Chameleon has a hard dependency on zope.i18n right now, I
forgot. Not working with BFG nor Chameleon in any projects doesn't
help to remember these things :)
There's no hard dependencies in Chameleon at this time.
