-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Bengtsson wrote:
> On 1 May 2010 15:40, Andreas Jung <li...@zopyx.com> wrote:
> Peter Bengtsson wrote:
> 
>>>>> "the unicode conflict resolver"?
>>>>> My app does not have any non-ascii characters until user input is
>>>>> added which it's programmed to work with.
>>>>> The problem was that '&nbsp;' inside the TALES expression was converted 
>>>>> to 0xa0
>>>>
> The traceback speaks of 0xc2.
> 
>> I know. There is no such character in my source code. Somewhere TAL
>> converts '&nbsp;' to 0xc2

I can not believe that this is related to &nbsp. The numeric entity
representation for that is &#160; which related to 0xa0. That's
confusing me...please reduce this to a minimal test.

Andreas




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvcRBAACgkQCJIWIbr9KYzfogCgz5/AZ2OLhjhCDDE2heNcMgn+
gM4AnRRRBOf6VjFh0Cvxd9TQSt5zBMOf
=VTl7
-----END PGP SIGNATURE-----

<<attachment: lists.vcf>>

_______________________________________________
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to