Re: sgml cleanup - Mailing list pgsql-docs

From Brent Verner
Subject Re: sgml cleanup
Date
Msg-id 20011121232339.A28949@rcfile.org
Whole thread Raw
In response to Re: sgml cleanup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
On 21 Nov 2001 at 23:11 (-0500), Tom Lane wrote:
| Brent Verner <brent@rcfile.org> writes:
| >   In trying to get the doc/ tree in cvs to build, I noticed a _lot_ of
| > empty closing tags when I ran
|
| ?? I'm not seeing any of these problems.  Are you using the recommended
| docs toolchain?

I have no clue about the recommended docs toolchain.  I must not be,
since my docbook2man-spec.pl does not (seem to) accept command line
arguments.  I've built postgresql.tar, but man.tar is still giving
me fits. The built html files can be seen at
  http://rcfile.org/posthack/pgdocs/

What I am seeing from a fresh update (at 11:19 EST) is this.

sleepy:~/pgsql/doc/src
brent$ grep '</>' sgml/*  |wc -l
grep: sgml/CVS: Is a directory
grep: sgml/ref: Is a directory
   1639
sleepy:~/pgsql/doc/src
brent$ grep -Hn '</>' sgml/xoper.sgml
sgml/xoper.sgml:116:     operators <literal><</> and <literal>></> for a particular data type are usually each
others'
sgml/xoper.sgml:117:     commutators, and operator <literal>+</> is usually commutative with itself.
sgml/xoper.sgml:118:     But operator <literal>-</> is usually not commutative with anything.
sgml/xoper.sgml:179:     For example, <literal><</> and <literal>>=</> are a negator pair for most data types.
sgml/xoper.sgml:242:    make sense if you think about it.  <literal>=</> will typically accept only
sgml/xoper.sgml:243:    a small fraction of the rows in a table; <literal><></> will typically reject
sgml/xoper.sgml:244:    only a small fraction.  <literal><</> will accept a fraction that depends on
sgml/xoper.sgml:248:    <literal><=</> will accept a slightly larger fraction than <literal><</> for the same
sgml/xoper.sgml:251:    rough guess anyhow.  Similar remarks apply to <literal>></> and <literal>>=</>.
sgml/xoper.sgml:359:     joins.  On machines that meet the <acronym>IEEE</> floating point standard, minus
sgml/xoper.sgml:389:     that can only succeed for pairs of values that fall at the <quote>same place</>
sgml/xoper.sgml:413:     In practice you should only write SORT clauses for an <literal>=</> operator,
sgml/xoper.sgml:414:     and the two referenced operators should always be named <literal><</>.  Trying
sgml/xoper.sgml:436:  There must be <literal><</> and <literal>></> ordering operators having the same left and
sgml/xoper.sgml:438:  operators <emphasis>must</emphasis> be named <literal><</> and <literal>></>; you do


confused,
  brent

--
"Develop your talent, man, and leave the world something. Records are
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing."  -- Duane Allman

pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: sgml cleanup
Next
From: Bruce Momjian
Date:
Subject: Re: sgml cleanup