W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2012

[Bug 19572] fn-unparsed-text-038

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Oct 2012 16:32:33 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19572-523-1fm8V7r1oh@http.www.w3.org/Bugs/Public/>

--- Comment #1 from Tim Mills <tim@cbcl.co.uk> ---
I partially agree - I'm assuming your processor isn't using the information in
resource/@encoding, which could lead to FOUT1200.

However, I'd rather target the test to hit FOUT1190 alone.

I have added a new file which contains a utf-8 byte order mark at the
beginning, but is invalid UTF-8.

Would you agree that this should only trigger FOUT1190?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 19 October 2012 16:32:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:40 UTC