On 1 May 2010 15:40, Andreas Jung <li...@zopyx.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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

If it's not a matter of configuration I can make a bug report.

> - -aj
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkvcPUcACgkQCJIWIbr9KYzw8ACgvySZqOCv2eN8WZPEu2Iifvwz
> XiAAnj5FGC8gD92HerPslMNFIrVN4zWR
> =EInK
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Zope maillist  -  z...@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 )
>
>



-- 
Peter Bengtsson,
work www.fry-it.com
home www.peterbe.com
hobby www.issuetrackerproduct.com
fun crosstips.org
_______________________________________________
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