Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA18454
	for <docs@postgresql.org>; Wed, 16 Jun 1999 10:28:50 -0400 (EDT)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id OAA30377;
	Wed, 16 Jun 1999 14:30:45 GMT
Sender: lockhart@hub.org
Message-ID: <3767B515.135F96C5@alumni.caltech.edu>
Date: Wed, 16 Jun 1999 14:30:45 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Momjian <maillist@candle.pha.pa.us>
CC: PostgreSQL-documentation <docs@postgresql.org>
Subject: Re: \ref in docs
References: <199906161420.KAA23392@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> In the developers documentation, I am seeing \ref like:
>   Figure \ref{parsetree} shows the parse tree built by the grammar rules
>   Note that every Sort and SeqScan node appearing in figure \ref{plan} has
> I can't figure out what they should be.  The developers manual from
> Stephan's stuff is really good.

Yes it is. I apparently forgot to resolve the rest of these latex-isms
into docbook-isms for referring to tables or graphics. In most cases
they were referring to internal tabular or listing info, so are
trivial to resolve; I had originally thought that they were referring
to graphics which I wasn't finding elsewhere.

There are probably a few other problems lurking in there; the markup
transformation was a pretty big job...

                 - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California