From: Peter Eisentraut <peter_e@gmx.net>
To: Josh Kupershmidt <schmiddy@gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: sgml cleanup: unescaped '>' characters
Date: Sat, 27 Aug 2011 23:48:45 +0300
Message-ID: <1314478125.2349.39.camel@vanquo.pezone.net> (raw)
In-Reply-To: <CAK3UJRENGTA97ZEhguS6CzjqQgqU-D8fpFdh54tHT-1xfx2LpQ@mail.gmail.com>
References: <CAK3UJRENGTA97ZEhguS6CzjqQgqU-D8fpFdh54tHT-1xfx2LpQ@mail.gmail.com>
On ons, 2011-08-24 at 23:28 -0400, Josh Kupershmidt wrote:
> I found myself rewriting the ./src/tools/find_gt_lt script in Perl
> this evening, since the existing script was quite broken (the main
> problem is it's not capable of understanding CDATA or sgml comment
> sections, and hence produces a bunch of noise).
>
> The rewritten version picked up a few stylistic inconsistencies in the
> SGML, such as:
> * breaking the trailing '>' of an SGML marker across lines. AFAIK
> this is legal, but is a bit inconsistent and just confuses simplistic
> tools like find_gt_lt
The cases you show don't appear to be terribly useful, but I think on
occasion this can be necessary to work around some arcane whitespace
rules in SGML or XML. (Just look at the generated HTML; it uses this
technique throughout.)
> * using single quotes instead of double quotes to surround a node
> attribute, as in <orderedlist numeration='loweralpha'>
It would be better if the tool could handle that, because sometimes you
want to use single quotes if the value contains double quotes.
> as well as seemingly-invalid SGML, such as using '>' unescaped inside
> normal SGML entries.
Unescaped > is valid, AFAIK.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: peter_e@gmx.net, schmiddy@gmail.com
Subject: Re: sgml cleanup: unescaped '>' characters
In-Reply-To: <1314478125.2349.39.camel@vanquo.pezone.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox