1762 2005-07-19 22:58:50 +0000 UTF-8 BOM in XHTML breaks CSS validator 2007-06-28 00:43:13 +0000 1 1 1 Unclassified CSSValidator XHTML1.0 CSS Validator PC Windows XP RESOLVED FIXED http://www.w3.org/International/tests/test-utf8-signature/withbom-nocharset.html P2 normal --- 1 phrosty ot www-validator-cvs oldest_to_newest 4941 0 phrosty 2005-07-19 22:58:50 +0000 A UTF-8 BOM in XHTML breaks the CSS validator, see the "Valid CSS" link at the bottom of the URL provided. 4943 1 bjoern 2005-07-19 23:11:20 +0000 Indeed (in fact, that's probably a known issue, but I am not sure whether someone filed a bug already). We might be able to fix this by upgrading to a more recent version of Xerces. 4992 2 ylafon 2005-07-20 10:10:55 +0000 Xerces version is currently 2.6.2, can you check again? 4994 3 bjoern 2005-07-20 12:05:41 +0000 Okay, it seems this happens if Content-Type:text/html with no charset parameter and a BOM. So this is probably the result of how the HTML parser with its XHTML sniffing interact with xerces. The Validator might be transcoding to UTF-8 before it passes the document to Xerces and in a character stream a bom may indeed not appear. It seems to work for application/xhtml+xml and text/html with a charset parameter in the HTTP header. 4995 4 phrosty 2005-07-20 13:14:12 +0000 that did it - declared it as utf-8 in the http header and it now works. 5137 5 ylafon 2005-07-22 10:13:10 +0000 (In reply to comment #3) > Okay, it seems this happens if Content-Type:text/html with no charset parameter > and a BOM. So this is probably the result of how the HTML parser with its XHTML > sniffing interact with xerces. The Validator might be transcoding to UTF-8 > before it passes the document to Xerces and in a character stream a bom may > indeed not appear. It seems to work for application/xhtml+xml and text/html > with a charset parameter in the HTTP header. The current code does this if the mime type has a charset parameter use it, if not, then if the mime type is text/html -> use iso-8859-1 13941 6 ot 2007-02-09 17:45:50 +0000 changing URL to be test case on i18n web site 15712 7 ot 2007-06-28 00:43:13 +0000 switching to tagsoup library as html parser has made this issue moot. (there are still issues with BOM-toting CSS files, but will open another bug for them)