This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#documentEncoding Comment: "interpreted as a character encoding" is not linked to a defined algorithm Posted from: 96.10.240.189
Step 4 of one of the inner steps of the "determining the character encoding" algorithm states: "If the attribute's name is "charset", let charset be the attribute's value, interpreted as a character encoding." I am trying to implement this algorithm, and I don't understand the phrase "interpreted as a character encoding." Does this require some additional processing beyond returning the discovered value as-is?
The attribute's value is a string. A character encoding is a mapping of byte sequences to Unicode codepoints. So the attribute's value (the character encoding name) has to be interpreted as a character encoding to use it. It doesn't mean anything more than that. Does that make sense? Is there better (but still accurate) terminology that I can use?
OK. I can't think of better terminology. I just wanted to make sure I wasn't missing something.