pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feed\ref in docs
3+ messages / 2 participants
[nested] [flat]
* \ref in docs
@ 1999-06-16 14:20 Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: Bruce Momjian @ 1999-06-16 14:20 UTC (permalink / raw)
To: Thomas G. Lockhart <lockhart@alumni.caltech.edu>; +Cc: PostgreSQL-documentation <docs@postgresql.org>
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.
--
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: \ref in docs
@ 1999-06-16 14:30 Thomas Lockhart <lockhart@alumni.caltech.edu>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Lockhart @ 1999-06-16 14:30 UTC (permalink / raw)
To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: PostgreSQL-documentation <docs@postgresql.org>
> 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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [DOCS] Re: \ref in docs
@ 1999-06-16 14:38 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
0 siblings, 0 replies; 3+ messages in thread
From: Bruce Momjian @ 1999-06-16 14:38 UTC (permalink / raw)
To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: PostgreSQL-documentation <docs@postgreSQL.org>
> > 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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~1999-06-16 14:38 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-06-16 14:20 \ref in docs Bruce Momjian <maillist@candle.pha.pa.us>
1999-06-16 14:30 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-06-16 14:38 ` Bruce Momjian <maillist@candle.pha.pa.us>
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