Issue 71: Encodings and unicode
http://code.google.com/p/html5lib/issues/detail?id=71
Comment #3 by jgraham.html:
It turns out the spec now requires that we ignore all ascii punctuation
in the
encoding name, so this now works.
Issue attribute updates:
Status: Fixed
--
You received th
Issue 71: Encodings and unicode
http://code.google.com/p/html5lib/issues/detail?id=71
Comment #2 by dirk.holtwick:
But I usually would expect the Python encodings to be used as "parse"
is implemented
a Python method ;)
--
You received this message because you are listed in the owner
or CC fi
Issue 71: Encodings and unicode
http://code.google.com/p/html5lib/issues/detail?id=71
Comment #1 by jgraham.cantab:
right, at the moment we only accept encodings and aliases specified in
http://www.iana.org/assignments/character-sets I'm not sure what is
actually needed
for web-compatibility.
Issue 71: Encodings and unicode
http://code.google.com/p/html5lib/issues/detail?id=71
New issue report by dirk.holtwick:
If the parameter "encoding" is passed to the parser it will be tested
against a list in constants. That leads to the problem that the encoding
"utf8" is not recognized because
