Date: Wed, 12 Nov 2003 03:36:23 +0900
Subject: Re: [HACKERS] Changes to Contributor List
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Michael Glaesemann <grzm@myrealbox.com>
To: pgsql-www@postgresql.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <200311111011.35840.josh@agliodbs.com>
Message-Id: <F357CC85-1475-11D8-9A55-0005029FC1A7@myrealbox.com>

From: Michael Glaesemann <grzm@myrealbox.com>
Date: Wed Nov 12, 2003  3:34:28 AM Asia/Tokyo
To: Josh Berkus <josh@agliodbs.com>
Subject: Re: [pgsql-www] [HACKERS] Changes to Contributor List


On Wednesday, November 12, 2003, at 03:11 AM, Josh Berkus wrote:

> accidentially paste over a closing tag or a bracket and screw up the 
> whole
> page.  This will be even more the case if you want to adopt the 
> stricter
> XHTML.

Practically, only screw up in terms of whether or not the page still 
validates. Most browsers, with their built-in forgiveness that lets 
them handle the 95% of invalid markup that's out there, won't break any 
more with invalid XHTML than they would with the same (invalid) HTML. 
There are a few browsers that change their behavior slightly depending 
on the document declaration, but from what I gather, the differences a 
slight. And at the extreme, I don't know of any browers that attempt to 
validate the page against the DTD and refuse to display if if they 
don't.

This isn't an excuse to not write the best markup possible, of course.