[Bug 19572] fn-unparsed-text-038

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19572

--- 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.