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: Thu, 03 Jan 2013 09:18:46 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20547-523-Ld3EmucZiq@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20547

--- Comment #5 from Michael Kay <mike@saxonica.com> ---
Adding encoding and/or media-type attributes might provide a solution. It's not
clear however that implementations are obliged to provide an API that allows
the application (in this case the test driver) to supply the media-type or
encoding of a resource in this way, so it's not the whole answer. I would be
inclined to add this information, and still add an alternative result for
implementations that use the fallback encoding.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 3 January 2013 09:18:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 January 2013 09:18:48 GMT