W3C home > Mailing lists > Public > www-validator-cvs@w3.org > February 2009

[Bug 6567] New: Transcoding should modify encoding in XML declaration, meta elements

From: <bugzilla@wiggum.w3.org>
Date: Thu, 12 Feb 2009 21:27:10 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-6567-169@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6567

           Summary: Transcoding should modify encoding in XML declaration,
                    meta elements
           Product: Validator
           Version: 0.8.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: check
        AssignedTo: dave.null@w3.org
        ReportedBy: ville.skytta@iki.fi
         QAContact: www-validator-cvs@w3.org


In addition to plain charset conversion, transcoding should also modify the
encoding in XML declaration, as well as <meta http-equiv> and <meta charset>
(HTML5), preferably the same way as doctype override does (leaves the existing
one there in comments).

Not doing the above replacements results in issues when the transcoded content
is passed to other validators that care about the encoding specified in one or
more of the above.  There's already a hack in place for XML::LibXML (bug 4867)
and some workarounds are attempted for the HTML5 validator in html5_validate()
which are not enough when there's a charset or doctype override in effect, but
I think it would be better to do this centrally (as part of the transcoding
process?) and get rid of the parser specific hacks and workarounds.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 12 February 2009 21:27:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:55:08 GMT