I don't have an answer for why Python might be mis-handling the data,
but wanted to make a factual correction:
[EMAIL PROTECTED] writes:
> Some web feeds use decimal character entities that seem to confuse
> Python (or me). For example, the string "doesn't" may be coded as
> "doesn’t" which shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Some web feeds use decimal character entities that seem to confuse
> Python (or me). For example, the string "doesn't" may be coded as
> "doesn’t" which should produce a right leaning apostrophe.
> Python hates decimal entiti
On Wed, 09 Jul 2008 16:39:24 -0700, bsagert wrote:
> Some web feeds use decimal character entities that seem to confuse
> Python (or me).
I guess they confuse you. Python is fine.
> For example, the string "doesn't" may be coded as "doesn’t" which
> should produce a right leaning apostrophe. Py
Some web feeds use decimal character entities that seem to confuse
Python (or me). For example, the string "doesn't" may be coded as
"doesn’t" which should produce a right leaning apostrophe.
Python hates decimal entities beyond 128 so it chokes unless you do
something like string.encode('utf-8').
