| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: sgml cleanup: unescaped '>' characters |
| Date: | 2011-09-03 20:47:49 |
| Message-ID: | 201109032047.p83KlnK01964@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2011-09-03 22:22:24 | Re: sgml cleanup: unescaped '>' characters |
| Previous Message | Peter Eisentraut | 2011-09-02 14:37:49 | Re: sgml cleanup: unescaped '>' characters |