On Wed, Oct 13, 2010 at 01:56:58PM +0100, Chris Withers wrote:
> On 13/10/2010 13:47, Marius Gedminas wrote:
> > On Wed, Oct 13, 2010 at 08:53:08AM +0100, Chris Withers wrote:
> >> In Zope 2.12, try putting the following in a TTW ZPT:
> >>
> >>
> >
> > Are you sure you didn't mean
> >
> >
>
>
On 13/10/2010 13:47, Marius Gedminas wrote:
> On Wed, Oct 13, 2010 at 08:53:08AM +0100, Chris Withers wrote:
>> Hi All,
>>
>> In Zope 2.12, try putting the following in a TTW ZPT:
>>
>>
>
> Are you sure you didn't mean
>
>
Ah, d'oh! Thanks for the catch!
> The way XML works, all entities in
On Wed, Oct 13, 2010 at 08:53:08AM +0100, Chris Withers wrote:
> Hi All,
>
> In Zope 2.12, try putting the following in a TTW ZPT:
>
>
Are you sure you didn't mean
? Because I am pretty sure your TALES namespace does not contain
a variable named "›".
> ...nothing more, nothing less.
>
>
On 13/10/2010 11:19, Charlie Clark wrote:
> Maybe your question is actually why is the XML entity being converted to
> character data at all?
I guess so...
My naive experience is that this "just works" in Zope 2.9 and "just
breaks" in 2.12.
> Maybe your question is actually why is the XML entit
Am 13.10.2010, 09:53 Uhr, schrieb Chris Withers :
> Any ideas where the non-ascii character is in the above?
Either this is a trick question or I'm just not getting it.
203a is the hex value of the decimal 8250.
>>> hex(8250)
'0x203a'
Maybe your question is actually why is the XML entity being
Hi All,
In Zope 2.12, try putting the following in a TTW ZPT:
...nothing more, nothing less.
On save, I get:
Compilation failed
: 'ascii' codec can't encode
character u'\u203a' in position 0: ordinal not in range(128)
If I try and view the template, unsurprisingly, I get:
Module ZPublisher
