Re: [DOCS] broken index references
On Fri, Mar 29, 2013 at 04:25:17PM -0700, Josh Kupershmidt wrote: > On Sat, Mar 23, 2013 at 11:12 AM, Tom Lane wrote: > > A different PDF-output problem that I've been noticing for awhile is that > > certain intra-page links don't work. The only clue I've found about it > > is the warnings in the TeX log, for instance: > > I could have overlooked a working example.. but as far as I've seen, > every link of the form: > > > > just goes to Page 1 in the PDFs. I checked against a recent 9.2-A4.pdf > from the website and my own 9.3-A4.pdf built on Debian; the psql page > (psql-ref.sgml) has a number of such links. The links seem to work OK > in the HTML version, though. 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.) -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] broken index references
On Sat, Nov 30, 2013 at 2:53 PM, Bruce Momjian wrote: > On Fri, Mar 29, 2013 at 04:25:17PM -0700, Josh Kupershmidt wrote: >> On Sat, Mar 23, 2013 at 11:12 AM, Tom Lane wrote: >> > A different PDF-output problem that I've been noticing for awhile is that >> > certain intra-page links don't work. The only clue I've found about it >> > is the warnings in the TeX log, for instance: >> >> I could have overlooked a working example.. but as far as I've seen, >> every link of the form: >> >> >> >> just goes to Page 1 in the PDFs. I checked against a recent 9.2-A4.pdf >> from the website and my own 9.3-A4.pdf built on Debian; the psql page >> (psql-ref.sgml) has a number of such links. The links seem to work OK >> in the HTML version, though. > > 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: 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: If an unquoted colon (:) followed by a psql variable name appears within an argument, it is replaced by the variable's value, as described in . which at least in my PDF reader just sends one back to Page 1. Josh -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] broken index references
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: > > > > 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: > > > If an unquoted colon (:) followed by a > psql variable name appears within an argument, it is > replaced by the variable's value, as described in linkend="APP-PSQL-interpolation" endterm="APP-PSQL-interpolation-title">. > > > 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 http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] misleading lang_name case in CREATE FUNCTION doc.
>Von: Peter Eisentraut [pete...@gmx.net] >>On 11/13/13, 9:02 AM, Marc Mamin wrote: >> something like :? >> >> The name of the language that the function is implemented in. >> Can be 'sql', 'c', 'internal', or the name of a user-defined procedural >> language. >> Single quotes are optional, they required correct case when used. >That would make the deprecated syntax more prominent than the >non-deprecated one. We want to get rid of the single quotes. Ok, next try :) The name of the language that the function is implemented in. Can be sql, c, internal, or the name of a user-defined procedural language. Single quotes are deprecated. They require correct case when used. regards, Marc Mamin -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
