From xemacs-m  Wed May  7 10:15:54 1997
Received: from amber.vis-av.com (amber.vis-av.com [206.119.44.2])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id KAA23321
	for <xemacs-beta@xemacs.org>; Wed, 7 May 1997 10:15:52 -0500 (CDT)
Received: (from derrell@localhost)
          by amber.vis-av.com (8.8.5/8.8.4)
	  id LAA29525; Wed, 7 May 1997 11:15:47 -0400 (EDT)
Date: Wed, 7 May 1997 11:15:47 -0400 (EDT)
Message-Id: <199705071515.LAA29525@amber.vis-av.com>
From: Derrell Lipman <derrell@vis-av.com>
To: wmperry@aventail.com
Cc: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: More html issues
In-Reply-To: <863erzs5h9.fsf@kramer.in.aventail.com>
References: <199705071445.KAA29449@amber.vis-av.com>
	<863erzs5h9.fsf@kramer.in.aventail.com>
X-Mailer: VM 6.30 under 20.2 XEmacs Lucid (beta4)
Reply-To: derrell@vis-av.com
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII

>>>>> "  William" == William M Perry <wmperry@aventail.com> writes:
>> <font color="#ffff00"></font>
>> 
>> which is not, of course, what I want since then the font change
>> doesn't affect anything.

  William>   This is due to the fact the <p> is not allowed in <font>.
  William> PSGML is doing the right thing.

Oops.  VERY careful reading of the 3.2 spec reveals that <font> is a
TEXT-level attribute, and not a BLOCK-level attribute, and, although I
disagree strongly with that decision, I see that <p> is not allowed
within <font>.  (Why in the world did they do it that way?????)

Sorry about that.

Derrell

