Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA20646 for ; Wed, 16 Jun 1999 10:38:33 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id KAA24088; Wed, 16 Jun 1999 10:38:20 -0400 (EDT) From: Bruce Momjian Message-Id: <199906161438.KAA24088@candle.pha.pa.us> Subject: Re: [DOCS] Re: \ref in docs In-Reply-To: <3767B515.135F96C5@alumni.caltech.edu> from Thomas Lockhart at "Jun 16, 1999 02:30:45 pm" To: Thomas Lockhart Date: Wed, 16 Jun 1999 10:38:19 -0400 (EDT) CC: PostgreSQL-documentation X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 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... Yes, I can imagine. It looks pretty good. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026