On Thu, Dec 16, 2010 at 12:47 PM, Chris McDonough wrote:
> On Thu, 2010-12-16 at 12:42 -0800, Iain Duncan wrote:
> > Oops I copied a traceback from one of my attempts at fixing it.
> >
> >
> >
> > Tres, that worked, thanks. I'm curious why it's necessary though. It
> > seems to me it should "just
On Thu, 2010-12-16 at 12:42 -0800, Iain Duncan wrote:
> Oops I copied a traceback from one of my attempts at fixing it.
>
>
>
> Tres, that worked, thanks. I'm curious why it's necessary though. It
> seems to me it should "just work" right? Can anyone explain further
> why that step is necessary
Oops I copied a traceback from one of my attempts at fixing it.
Tres, that worked, thanks. I'm curious why it's necessary though. It seems
to me it should "just work" right? Can anyone explain further why that step
is necessary once a view is wrapped? ( related note, wrapper views are
awesome, th
Alternatively, enable implicit decoding using
``default_encoding="utf-8"`` (in the template constructor). This is
enabled on Plone, for instance.
\malthe
On 16 December 2010 14:47, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/15/2010 10:18 PM, Iain Duncan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/15/2010 10:18 PM, Iain Duncan wrote:
> Not sure where I'm supposed to ask this now, here? Pyramid list?
>
> I have view with a chameleon template that contains utf-8 unicode special
> chars. It renders fine when rendered on it's own from a view
Not sure where I'm supposed to ask this now, here? Pyramid list?
I have view with a chameleon template that contains utf-8 unicode special
chars. It renders fine when rendered on it's own from a view. As soon as I
wrap that view with a wrapper view, I get errors with the wrapper choking on
the un
