7778 2009-09-30 20:00:47 +0000 "interpreted as a character encoding" is not linked to a defined algorithm 2010-10-04 14:55:51 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other CLOSED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#documentEncoding P3 normal LC 1 contributor ian ian mark mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 27959 0 contributor 2009-09-30 20:00:47 +0000 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 27960 1 mark 2009-09-30 20:11:24 +0000 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? 28478 2 ian 2009-10-18 22:26:34 +0000 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? 29230 3 mark 2009-10-30 19:20:15 +0000 OK. I can't think of better terminology. I just wanted to make sure I wasn't missing something.