W3C home > Mailing lists > Public > www-validator-cvs@w3.org > July 2014

[Bug 26347] New: Suppress "Internal encoding declaration ... disagrees with the actual encoding of the document (UTF-8)" error when user uses "Check by text input"

From: <bugzilla@jessica.w3.org>
Date: Tue, 15 Jul 2014 23:55:55 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-26347-169@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26347

            Bug ID: 26347
           Summary: Suppress "Internal encoding declaration ... disagrees
                    with the actual encoding of the document (UTF-8)"
                    error when user uses "Check by text input"
           Product: Nu Markup Checker
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: General
          Assignee: mike+validator@w3.org
          Reporter: kurosawa-takeshi@mitsue.co.jp
        QA Contact: www-validator-cvs@w3.org

Nu Markup Checker reports an error "Internal encoding declaration shift_jis
disagrees with the actual encoding of the document (UTF-8)" in following
conditions.

1. Select "Check by text input"
2. Paste html which has non utf-8 encoding declaration.
3. Click "Check"

I think this error is not reasonable. Because

- Nu Markup Checker only accepts utf-8 input and user cannot change "actual
encoding of the document"
- Nu Markup Checker reports a warning (Legacy encoding shift_jis used.
Documents should use UTF-8.) for same document when user uses "Check by file
upload"

W3C Markup Validator reports "info" in same condition. I think it is
reasonable.
http://validator.w3.org/

> Using Direct Input mode: UTF-8 character encoding assumed
> Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.

To recap, I think Nu Markup Checker should reports warning (same as "file
upload") or info (same as W3C Markup Validator).

Sample HTML:

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="shift_jis">
<title>Shift_JIS</title>
</head>
<body>
<p>Shift_JIS</p>
</body>
</html>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 15 July 2014 23:55:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:57 UTC