This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28030 - UTF-8 Mismatch
Summary: UTF-8 Mismatch
Status: RESOLVED WONTFIX
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: HEAD
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL: http://www.slomp.com
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-15 00:05 UTC by Jacob
Modified: 2015-08-23 07:19 UTC (History)
1 user (show)

See Also:

Attachments

Description Jacob 2015-02-15 00:05:10 UTC 
This is the warning I get.

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


I tested with the website www.slomp.com
Comment 1 Michael[tm] Smith 2015-02-15 16:28:20 UTC 
Hi, Thanks for reporting this. I've confirmed it occurs with http://www.slomp.com/ but it's caused by the legacy validator code, not the HTML5 validator code. So to avoid it, you can use http://validator.w3.org/nu/ directly.
Comment 2 Jacob 2015-02-15 17:53:29 UTC 
(In reply to Michael[tm] Smith from comment #1)
> Hi, Thanks for reporting this. I've confirmed it occurs with
> http://www.slomp.com/ but it's caused by the legacy validator code, not the
> HTML5 validator code. So to avoid it, you can use
> http://validator.w3.org/nu/ directly.

Ah OK, what I did find out is that my <meta charset="UTF-8"> was in the code twice, that caused the issue.

So it might be better if the text reads;

Warning, <meta charset> has been specified twice or so?
Comment 3 Michael[tm] Smith 2015-08-23 07:19:16 UTC 
See comment 1