Re: Obsolete elements -- trying again

pflynn@curia.ucc.ie (Peter Flynn)

Mail folder: html-archive
Next message: Daniel W. Connolly: "Re: Obsolete elements -- trying again "
Previous message: Leo _ _ _ _ _ _ _ _ _ _ _ _ _ _ Peace is not something you win. Peace is: "Obsolete elements -- trying again"
Maybe in reply to: Leo _ _ _ _ _ _ _ _ _ _ _ _ _ _ Peace is not something you win. Peace is: "Obsolete elements -- trying again"

Date: Fri, 26 Aug 94 12:37:18 EDT
Message-id: <9408261633.AA08887@curia.ucc.ie>
Reply-To: pflynn@curia.ucc.ie
Originator: html-wg@oclc.org
Sender: html-wg@oclc.org
Precedence: bulk
From: pflynn@curia.ucc.ie (Peter Flynn)
To: Multiple recipients of list <html-wg@oclc.org>
Subject: Re: Obsolete elements -- trying again
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Working Group (Private)

> I was wondering why XMP and LISTING are being made obsolete.  They are
> very useful when you want to return system error messages to the user
> during the execution of a script.  I can't use PRE because Lynx will get
> confused when there is an unadorned "<".
> 
> Is there any chance that the obsolete status of XMP and/or LISTING can
> be changed?

I was puzzled by this too: there are many times when you might want to
include verbatim text explicitly lifted from an external source which
may contain arbitrary ASCII or ISO 646 characters...

///Peter

PS: Leo, please fix your mail header...

From: "Leo _ _ _ _ _ _ _ _ _ _ _ _ _ _ Peace is not something you win. Peace is
Subject: Obsolete elements -- trying again
Sender: html-wg@oclc.org
Reply-To: "Leo