Re: broken index references

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: broken index references
Date: 2013-12-01 01:34:54
Message-ID: 20131201013454.GF11181@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Sat, Nov 30, 2013 at 05:23:14PM -0500, Josh Kupershmidt wrote:
> > Sorry to be looking at this late, but I just tested the 9.3.1 PDF at:
> >
> > http://www.postgresql.org/files/documentation/pdf/9.3/postgresql-9.3-US.pdf
> >
> > and the link on page 1748 that links to section 31.14 worked fine:
> >
> > For additional environment variables, see Section 31.14.)
>
> [... jogging my memory ... ] I think the problem was specifically with
> links of the form:
>
> <xref linkend="..." endterm="...">
>
> having the "endterm" attribute specified -- your example didn't have
> an "endterm". For an example, see the next page (p. 1749 according to
> our page numbering, under the "Meta-Commands" sub-heading), for the
> link to "SQL Interpolation" at the end of this paragraph:
>
> <para>
> If an unquoted colon (<literal>:</literal>) followed by a
> <application>psql</> variable name appears within an argument, it is
> replaced by the variable's value, as described in <xref
> linkend="APP-PSQL-interpolation" endterm="APP-PSQL-interpolation-title">.
> </para>
>
> which at least in my PDF reader just sends one back to Page 1.

Yes, I confirm that failure on Debian. Thank you. Anyone want to
suggest a cause?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2013-12-02 21:15:00 Re: Data Partition Encryption documentation
Previous Message Josh Kupershmidt 2013-11-30 22:23:14 Re: broken index references