Add html5 character encoding mappings

[dcramer]

Add html5 character encoding mappings

[dan-blanchard]

@sigmavirus24 Is this something you fixed? I'm trying to migrate old issues over to our new repo.

[sigmavirus24]

@dan-blanchard no, the issue in that commit refers to sv24-archive#8

[dan-blanchard]

@mlissner I don't actually see this mapping you speak of in the latest version of the HTML5 spec:
http://www.w3.org/html/wg/drafts/html/master/single-page.html#character-encodings

That said, I do think always returning CP1252 instead of Latin-1 is advisable because it gets you the quotes and things that Latin-1 doesn't, and one almost never encounters documents that purposefully have the replaced control characters in them.

[mlissner]

Well... My internet connection is so slow here I can't download the whole
spec, but it might be in chapter eight? I can get the TOC, but downloading
past chapter four is killing me.

Anyway, yeah, I filed this bug after encountering a page that was reporting
Latin-1 when it had cp1252 characters, and I realized there's almost no
reason to ever return Latin-1 anymore.
On Dec 21, 2013 3:16 AM, "Dan Blanchard" [email protected] wrote:

@mlissner https://github.com/mlissner I don't actually see this mapping
you speak of in the latest version of the HTML5 spec:

http://www.w3.org/html/wg/drafts/html/master/single-page.html#character-encodings

That said, I do think always returning CP1252 instead of Latin-1 is
advisable because it gets you the quotes and things that Latin-1 doesn't,
and one almost never encounters documents that purposefully have the
replaced control characters in them.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-31011860
.