Subject: Re: sgml cleanup: unescaped '>' characters
From: Peter Eisentraut <peter_e@gmx.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Josh Kupershmidt <schmiddy@gmail.com>, pgsql-docs
	<pgsql-docs@postgresql.org>
In-Reply-To: <201109012131.p81LVfW09259@momjian.us>
References: <201109012131.p81LVfW09259@momjian.us>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 02 Sep 2011 17:37:49 +0300
Message-ID: <1314974269.29051.3.camel@fsopti579.F-Secure.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On tor, 2011-09-01 at 17:31 -0400, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > On tor, 2011-09-01 at 14:17 -0400, Bruce Momjian wrote:
> > > > That still leaves open why we bother about escaping <.
> > > 
> > > The problem is that I often add SGML that has:
> > > 
> > >         if (1 < 0) ...
> > > 
> > > I need something to warn me about those, especially in the release
> > > notes.
> > 
> > Why do you need to be warned about that?
> 
> If I have:
> 
> 	if (1 < fred)
> 
> it will think "fred" is a SGML tag, no?

No, a < followed by a space is not a tag, it's character data.  If it
thought it were a tag, it would complain.