W3C home > Mailing lists > Public > www-validator@w3.org > February 2000

Re: XHTML DTD problem?

From: Bless Terje <link@rito.no>
Date: Tue, 8 Feb 2000 17:35:01 +0100
Message-ID: <22FD5BD2DBC5D211BE0D0008C7A4E87FD9B44A@odin4.rito.no>
To: "'Braverman, David'" <DBraverman@ingprime.com>, "'www-validator@w3.org'" <www-validator@w3.org>
>The following DTD, taken straight from the W3 website:
>
><!DOCTYPE html
>   PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
>   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
>
>Does the following to the validator:
>
>Uh oh! I got the following unknown error:
>/usr/local/bin/nsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-st
>rict.dtd:236:
>27:E: omitted tag minimization parameter can be omitted only 
>if "OMITTAG NO"
>is specified on the SGML declaration Please make sure you specified the
>DOCTYPE properly! 
>
>Am I doing something wrong?

I'm not really sure why you are getting that particular error. You should be
getting a "Doument type unkown"-style error. The problem is that you are
serving the document up as "application/octet-stream" when it should be
"text/html". You've probably forgotten to add a mapping from ".xhtml" files
to a "text/html" content type. Try renaming it "Experiment.html" and
revalidate.

http://validator.w3.org/check?uri=http://193.157.66.108/Experiment.html


Of course, since the validator doesn't have a mapping for XHTML, you can't
serve it as the IMO better alternative "text/xhtml". Try comparing:

http://validator.w3.org/check?uri=http://193.157.66.108/Experiment.xhtml
http://193.157.66.108/check?uri=http://193.157.66.108/Experiment.xhtml

Both are validating the same file, which is being served as text/xhtml, but
the W3C version doesn't have a mapping from text/xhtml to "XHTML". In all
fairness to Gerald, I was the one that provided that particular config file
in the first place, but it would seem that "someone" got so hung up on
masquerading XHTML as HTML that they just plain forgot to add the necessary
mapping. :-)


OTOH, the validator doesn't really grok XHTML served as XML either. In
general, there seems to be a great many caveats in the code whenever XML
enters the pivture.
Received on Tuesday, 8 February 2000 11:35:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:13:53 GMT