W3C home > Mailing lists > Public > www-validator-cvs@w3.org > May 2013

[Bug 22230] New: Incorrect error wording when forcing character encoding

From: <bugzilla@jessica.w3.org>
Date: Fri, 31 May 2013 20:14:24 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-22230-169@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22230

            Bug ID: 22230
           Summary: Incorrect error wording when forcing character
                    encoding
    Classification: Unclassified
           Product: Validator
           Version: HEAD
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: check
          Assignee: dave.null@w3.org
          Reporter: ori@avtalion.name
        QA Contact: www-validator-cvs@w3.org

When validating a page served with an HTTP header reporting an encoding of
'ascii', and a meta tag reporting an error of 'utf-8', warning W19 is shown:

> The character encoding specified in the HTTP header (ascii) is different
> from the value in the <meta> element (utf-8). I will use the value from the 
> HTTP header (ascii) for this validation. 

This is using the parameter charset=(detect+automatically)

However, if an encoding is forced with the parameter charset=utf-8, the wording
of W19 becomes confusing and incorrect:

> The character encoding specified in the HTTP header (ascii) is different from
> the value in the <meta> element (utf-8). I will use the value from the HTTP 
> header (utf-8) for this validation.

The warning manages to report the HTTP header encoding as being both 'ascii'
and 'utf-8'.

The warning assumes that the 'used' encoding was determined according to the
specification, and not forced by the validator.

I assume W18 and W20 have the same problem.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 31 May 2013 20:14:25 UTC

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