Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAKL9Lm44231 for ; Tue, 20 Nov 2001 16:09:22 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fAKL93c03949; Tue, 20 Nov 2001 16:09:03 -0500 (EST) To: Joe Conway cc: pgsql-docs@postgreSQL.org Subject: Cross-references (was [PATCHES] PQescapeBytea documentation patch) In-reply-to: <3BFABB2C.3020307@home.com> References: <3BFABB2C.3020307@home.com> Comments: In-reply-to Joe Conway message dated "Tue, 20 Nov 2001 12:21:00 -0800" Date: Tue, 20 Nov 2001 16:09:03 -0500 Message-ID: <3946.1006290543@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/57 X-Sequence-Number: 1130 [ redirected from patches to pgsql-docs ] Joe Conway writes: > I was trying (but gave up) to cross-reference back to the input escape > table in the User's Guide, but could not get the documentation to > compile with a cross-book xref (missing IDREF error). Can a cross-book > xref be done? AFAIK, not. If you look around you'll notice a bunch of vague cross- references like See the Administrator's Guide for details. This pretty much sucks but as long as we maintain the notion that the books should be separately buildable, I'm not sure there's a way to do better. As far as readers go, I don't see that there's any need for anything but the integrated document --- and we could do better cross-references in that setting than we are doing. The one good thing about the separate books is that you can build just one (to check the markup of a section you're working on) in a reasonable amount of time. Building the integrated doc seems to take forever :-( Anyone see a way out of this dilemma? regards, tom lane