- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 16 Mar 2007 09:13:54 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4372 ------- Comment #5 from colin@colina.demon.co.uk 2007-03-16 09:13 ------- What I had in mind is that there is no need for a rule for this - it is implicit in supporting a particular version of HTML. If a user requests version 4.0 HTML serialization, but specifies for doctype-public the fpi for version 3.2, then there is a contradiction in the users xsl:output statements. So the user has simultaneously requested both version 3.2 and 4.0. But I guess this is a slightly different error from just specifying version 3.2 in the version attribute (and the implementation only supports 4.0). Nevertheless, I would feel perfectly justified in issuing an error message saying that doctype-public requests a public identifier for a version of HTML not supported by this implementation (of course, I dont have your problem of thousands of users likely to complain :-). Still, as I write this, I see another problem. Supposing the implementation supports both 4.0 and 3.2. In that case, a different error message is appropriate (and appears not to be necessarliy authorized by the current spec. )
Received on Friday, 16 March 2007 09:14:01 UTC