From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201109032047.p83KlnK01964@momjian.us>
Subject: Re: sgml cleanup: unescaped '>' characters
In-Reply-To: <1314974269.29051.3.camel@fsopti579.F-Secure.com>
To: Peter Eisentraut <peter_e@gmx.net>
Date: Sat, 3 Sep 2011 16:47:49 -0400 (EDT)
CC: Josh Kupershmidt <schmiddy@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Peter Eisentraut wrote:
> 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.

Sometimes it is '<' (in single quotes), which I thought would be a
problem.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +