W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2013

[Bug 20547] [QT3TS] fn-unparsed-text-lines-040

From: <bugzilla@jessica.w3.org>
Date: Wed, 02 Jan 2013 20:13:36 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20547-523-39FgQVie7h@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20547

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
Yes, we could include the encoding as an explicit argument. The only question
is whether that would spoil the intent of the test. The alternative might be to
have two alternate results, one for processors that correctly infer the
encoding using implementation-defined heuristics, and one for processors that
fall back to UTF-8. (I'm not sure if the spec allows for the possibility that
implementation-defined heuristics will be invoked and will give the wrong
answer...)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 2 January 2013 20:13:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 2 January 2013 20:13:37 GMT