- From: Peter K. Sheerin <pete@petesguide.com>
- Date: Fri, 14 Sep 2001 09:52:12 -0700
- To: "Gerald Oskoboiny" <gerald@w3.org>, <www-validator@w3.org>
> I updated the public validator site tonight, http://validator.w3.org/ The way that the BOM is supported in this public release changed from earlier versions on the testing port, and I'm not sure the it's really quite right. Validating my site petesguide.com I get this: Warning: UTF-8 'BOM' detected and removed. (See the explanation for details.) Explanation: ------------------ "UTF-8 'BOM' detected and removed" The document contained an UTF-8 encoded Unicode Byte Order Mark (BOM) as the first character and we have removed it before parsing. Many XML Processors do not allow it. To be on the safe side you should avoid using the BOM in UTF-8 encoded documents. Note that the BOM in UTF-16 encoded documents is required and handled by all conforming XML Processors. ------------------ There is no mention that the BOM is perfectly valid, and the spec allow it (even encourage it), and may make people they are doing something wrong, without indicating that such XML parsers are broken. And how about terminology? The page in question follows all the specs perfectly, yet the validator displays a warning before the successful validation message and logo. I'm trying to use petesguide as an example of advanced and perfect coding (browsers that choke, be damned), but this wording makes it look like I'm doing something wrong, rather than the XML parsers. Suggestions: 1) Move this "warning" below the success message. 2) Can you use a different word, such as "caution"? Warning is a bit too strong. 3) Can you change the wording to more clearly reflect that the BOM is allowed to be there, but that some browsers/parsers may have problems, and that it's the fault of those programs, not the author's coding?
Received on Friday, 14 September 2001 12:52:22 UTC