From owner-freebsd-www@FreeBSD.ORG Fri Mar 4 11:35:40 2005 Return-Path: Delivered-To: freebsd-www@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D028916A4CE for ; Fri, 4 Mar 2005 11:35:40 +0000 (GMT) Received: from shrike.submonkey.net (cpc4-cdif3-6-1-cust116.cdif.cable.ntl.com [82.23.41.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4746043D62 for ; Fri, 4 Mar 2005 11:35:40 +0000 (GMT) (envelope-from setantae@submonkey.net) Received: from setantae by shrike.submonkey.net with local (Exim 4.44 (FreeBSD)) id 1D7B5n-000LNz-5F; Fri, 04 Mar 2005 11:35:39 +0000 Date: Fri, 4 Mar 2005 11:35:39 +0000 From: Ceri Davies To: "Devon H. O'Dell" Message-ID: <20050304113539.GN27332@submonkey.net> Mail-Followup-To: Ceri Davies , "Devon H. O'Dell" , www@FreeBSD.org References: <1109934321.3926.52.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QwZB9vYiNIzNXIj" Content-Disposition: inline In-Reply-To: <1109934321.3926.52.camel@localhost.localdomain> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.8i Sender: Ceri Davies cc: www@FreeBSD.org Subject: Re: Tags like
and our current doctype X-BeenThere: freebsd-www@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Project Webmasters List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 11:35:41 -0000 --+QwZB9vYiNIzNXIj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 04, 2005 at 12:05:21PM +0100, Devon H. O'Dell wrote: > >From what I recall, tags like
are self closing in the HTML 4.0 and > 4.01 doctypes, i.e.
is redundant and confuses (or is supposed to > anyway) the parser into thinking the last tag was closed. >=20 > However, if I change this to
, even with our doctype, it freaks out. > I suppose that the parser doesn't really care what our doctype is, it > just wants the content to be XML-compliant. >=20 >
is XML compliant, if you have the right entity definition. >=20 > So I see two possible options for the future: >=20 > 1) Figure out how to make the parser like
and keep our current > doctype (or upgrade to HTML 4.01/Strict), or >=20 > 2) Hop over to XHTML 1.0/Transitional, which will allow us to utilize > features of XHTML (and let us keep
, which is valid in XHTML) > while still having our Content-type as text/html (this isn't allowed for > any other XHTML doctype) #2 is best. I made a patch ages and ages ago for this (not a full patchset, mind you) that might even vaguely apply still; search the archives for a post from me with a subject containing "XHTML" and you should find it. At the time the response was a mixture of mild resistance and apathy, however; it was felt that fixing this wasn't worth the CVS churn as I recall (yes, that surprised me too). Ceri --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --+QwZB9vYiNIzNXIj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCKEgLocfcwTS3JF8RAhcmAJwJPPChRnsrFLtlGsHjsGWNr8bH8QCeKJqk Db1FzoTEfY9h7gYuz0omIuY= =fvgQ -----END PGP SIGNATURE----- --+QwZB9vYiNIzNXIj--