Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 269EFB5DBF9 for ; Sat, 27 Aug 2011 17:48:59 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 12331-05 for ; Sat, 27 Aug 2011 20:48:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mail.postgresql.org (Postfix) with SMTP id 46C97B5DBF7 for ; Sat, 27 Aug 2011 17:48:47 -0300 (ADT) Received: (qmail invoked by alias); 27 Aug 2011 20:48:47 -0000 Received: from a88-115-218-165.elisa-laajakaista.fi (EHLO [10.0.0.102]) [88.115.218.165] by mail.gmx.net (mp035) with SMTP; 27 Aug 2011 22:48:47 +0200 X-Authenticated: #495269 X-Provags-ID: V01U2FsdGVkX1/lLzUEGgXlN1+QyavmHy8tmoaZDx6V0sGUrRtIUh OGDT6ykubVOi52 Subject: Re: sgml cleanup: unescaped '>' characters From: Peter Eisentraut To: Josh Kupershmidt Cc: pgsql-docs In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Sat, 27 Aug 2011 23:48:45 +0300 Message-ID: <1314478125.2349.39.camel@vanquo.pezone.net> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.403 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.504 X-Spam-Level: X-Archive-Number: 201108/26 X-Sequence-Number: 6916 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 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.