W3C home > Mailing lists > Public > www-validator@w3.org > April 2015

Re: Proposal: Remove W21 "Byte-Order Mark found in UTF-8 File"

From: Michael[tm] Smith <mike@w3.org>
Date: Sat, 11 Apr 2015 00:49:57 +0900
To: Takeshi Kurosawa <taken.spc@gmail.com>
Cc: www-validator@w3.org
Message-ID: <20150410154957.GN1547@sideshowbarker.net>
Takeshi Kurosawa <taken.spc@gmail.com>, 2015-03-30 22:12 +0900:
> Archived-At: <http://www.w3.org/mid/CAHL3uyOYXriVpJx6rUP8fgc_SryaPKWD5HHRsOPsSF=E+9ucRw@mail.gmail.com>
> 
> Hi all,
> 
> I would like to propose removing W21 "Byte-Order Mark found in UTF-8
> File" warning from the W3C Markup Validator.
...
> I understand that the W3C Markup Validator doesn't support HTML5
> directly. However I would like to saythe  the situation described in
> the message was changed. As far as I know, the major browsers support
> BOM.
...
> Proposals
> 
> A. Remove W21 from the W3C Markup Validator.
> 
> B. If A is not possible, bypass W21 check for HTML5 documents as HTML5
> requires that User Agents recognize the BOM

I agree that it should be removed but there’s near-zero likelihood it
actually ever will be, since I’m not going to touch the legacy validator
code myself and nobody else has made any updates to it for several years
now, and nobody is likely to in the future either. It’s a legacy tool. The
solution to your problem is to just use http://validator.w3.org/nu/
directly instead. And if you can’t switch over completely to doing that
right now, then the root problem you need to fix is that you need to remove
whatever obstacle is preventing you from switching over completely to just
using http://validator.w3.org/nu/ Making further updates to the legacy
validator at this point would just be fixing the wrong problem.

  —Mike

-- 
Michael[tm] Smith https://people.w3.org/mike

Received on Friday, 10 April 2015 15:50:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:18:13 UTC