W3C home > Mailing lists > Public > public-html-admin@w3.org > July 2013

[Bug 22819] New: The algorithm for extracting an encoding from meta should be used for parsing charset attribute.

From: <bugzilla@jessica.w3.org>
Date: Sat, 27 Jul 2013 22:50:36 +0000
To: public-html-admin@w3.org
Message-ID: <bug-22819-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22819

            Bug ID: 22819
           Summary: The algorithm for extracting an encoding from meta
                    should be used for parsing charset attribute.
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: alistair.potts@gmail.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

8.2.5.4.4 The "in head" insertion mode -

When the parser comes across a charset declaration, it makes sense for it to
use the same algorithm for extracting the charset as defined in the "algorithm
for extracting a character encoding from a meta element".

It does this for the http-equiv style charset declaration, but currently for
'charset=foo' style declaration it just says:

"If the element has a charset attribute, and getting an encoding from its value
results in a supported ASCII-compatible character encoding or a UTF-16
encoding..."

Specifically 'getting an encoding from its value' should be be unambiguous, as
with the http-equiv wording, because the algorithm is more robust. If it's not
used, and just the literal value of the attribute extracted, then there's the
possibility of a needless reparse and an incorrect inference from the charset
value.

Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 27 July 2013 22:50:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:57:24 UTC