Re: [DOCS] PDF build issue with 9.0 Alpha5
Some time ago I sucessfully built pdf, but today I got pg-h...@mira:~/cvs/HEAD/pgsql/doc/src/sgml$ make postgres-A4.pdf openjade -D . -D . -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d ./stylesheet.dsl -t tex -V tex-backend -i output-print -i include-index -V texpdf-output -V '%paper-type%'=A4 -o postgres-A4.tex-pdf postgres.sgml openjade:./stylesheet.dsl:621:2:E: flow object not accepted by port; only display flow objects accepted make: *** [postgres-A4.tex-pdf] Segmentation fault (core dumped) make: *** Deleting file `postgres-A4.tex-pdf' This is Ubuntu 9.10 Linux mira 2.6.33-020633-generic #020633 SMP Thu Feb 25 10:10:03 UTC 2010 x86_64 GNU/Linux Oleg On Fri, 2 Apr 2010, Tom Lane wrote: "Erik Rijkers" writes: I can build 'make postgres-A4.pdf' against cvs without problem. Fails for me :-(. Whose distribution of jadetex are you using, and what version exactly? I've pretty much convinced myself that the string consumption is the fault of the FlowObject macros in jadetex.ltx. regards, tom lane Regards, Oleg _ Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru), Sternberg Astronomical Institute, Moscow University, Russia Internet: [email protected], http://www.sai.msu.su/~megera/ phone: +007(495)939-16-83, +007(495)939-23-83 -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] [COMMITTERS] pgsql: Remove unnecessary xref endterm attributes and title ids The
[email protected] (Peter Eisentraut) writes: > Log Message: > --- > Remove unnecessary xref endterm attributes and title ids > The endterm attribute is mainly useful when the toolchain does not support > automatic link target text generation for a particular situation. In the > past, this was required by the man page tools for all reference page links, > but that is no longer the case, and it now actually gets in the way of > proper automatic link text generation. The only remaining use cases are > currently xrefs to refsects. I won't miss the need to write endterm, but what's the "remaining use cases" exactly? You need to explain to other people what's the new dispensation, if you don't want it to get messed up again. regards, tom lane -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] PDF build issue with 9.0 Alpha5
"Erik Rijkers" writes: > Here is how much of TeX's memory you used: > 246467 strings out of 246489 > 1749307 string characters out of 1824395 Mph. So your installation is creating a slightly smaller number of strings, but you're still on the hairy edge of failure (another half dozen flow objects and it'd croak). regards, tom lane -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] PDF build issue with 9.0 Alpha5
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= writes:
> I was trying to build PDF docs for 9.0 Alpha5, and I got this message:
> ! TeX capacity exceeded, sorry [number of strings=245830].
I've found a possible solution for this. The bulk of the strings are
being created by jadetex.dtx: it makes two control sequences for each
flow object in the document. One of these is a page number and the
other seems to have no purpose except to prevent creating duplicate
hyperref anchors. However, diking out the latter doesn't create any
obvious ill effects --- either we have no occurrences in our docs of a
pattern that would result in a duplicate, or there isn't any real
adverse consequence of having a dup. (And in any case it's hard to
envision an adverse consequence that's worse than complete failure to
build the document.)
There turns out to be a very easy way to inject the code change, which
is to create a file "jadetex.cfg" in the doc/src/sgml directory,
containing the modified version of the relevant TeX macro.
(Note: in the vpath case we'd probably need to link it into the build
directory; I haven't experimented with that.) Put this in the file:
\def\FlowObjectSetup#1{%
\ifDoFOBSet
\ifLabelElements
\ifx\lab...@empty\let\label\element\fi
\fi
\ifx\lab...@empty\else
\bgroup
\ifNestedLink
\else
\hy...@anchorstart{\label}\hyper@anchorend
\PageLabel{\Label}%
\fi
\egroup
\let\lab...@empty
\let\eleme...@empty
\fi
\fi
}
For comparison, the original definition we're replacing is
\def\FlowObjectSetup#1{%
\ifDoFOBSet
\ifLabelElements
\ifx\lab...@empty\let\label\element\fi
\fi
\ifx\lab...@empty\else
\expandafter\ifx\csname x...@\label\endcsname\@madelink
\else
\bgroup
\ifNestedLink
\else
\hy...@anchorstart{\label}\hyper@anchorend
\PageLabel{\Label}%
\expandafter\gdef\csname x...@\label\endcsname{ }%
\fi
\egroup
\let\lab...@empty
\let\eleme...@empty
\fi
\fi
\fi
}
This should work with either jadetex 3.12 or 3.13, and probably older
versions but I don't have source code handy to look at. 3.12 dates
back to 2002 so it's probably old enough anyhow.
I haven't tried to build anything except PDF output with this
substituted code, so it's possible that it interferes with other
output formats.
Comments?
regards, tom lane
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
