Gérard Talbot <ne***********@gtalbot.org> wrote:
You may want to open an account at W3C and add a comment here:
- - I certainly would appreciate this since this unknown parse mode warning
is a regression IMO.
I'm not particularly enthusiastic about bug reporting systems that
require the reporter to register just to help the maintenance of some
software. I understand concerns with spamming, but forced registration
makes spamming the volunteer helper's problem, which means less
volunteers.
Anyway, if someone wishes to contribute to fixing the problem, I'd
suggest mentioning that the message is verbally wrong (as well as
questionable in general). It's not a matter of unknown parse mode. The
validator knows the two parse modes well. It's just unwilling to make a
choice between them without making noise about it. "Unresolved parse
mode" would be a bit better.
Afaics the validator should parse in 2 stages, first to retrieve the
url to the custom DTD, after which there should be no ambiguity about
parsing the document as SGML or XML, so why does the w3c validator
issue the warning?
As far as I know, the validator is a conglomerate that uses an old SGML
parser and a newer XML parser, and the DTD parsing is handled by them as
well. Therefore it needs to select the parser at an early stage. And
apparently it defaults to SGML parsing for text/html. You can even feed
XHTML to it that way.
If it first tried to parse the DTD as an SGML DTD and switch to XML
parsing if errors are found in the DTD, we would probably get even
stranger error messages than today if there is an error in the DTD - or
just a feature that exceeds the capacity limitations of the validator.
They still haven't fixed the GRPCNT limitation, or added reporting of DTD
problems, so for a document like
http://www.cs.tut.fi/~jkorpela/html/nobr.html I still get "Failed
validation, 0 error".
So instead of reporting problems with the W3C validator, I use the WDG
validator.
--
Yucca,
http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring:
http://www.cs.tut.fi/~jkorpela/www.html