On 2002.05.01 16:34 Bernd Brandstetter wrote:
So, I have two questions/suggestions:
1) Wouldn't it be possible to let FOP create the output in two steps like
for instance (La)TeX does. Doing a dry run first only to calculate the
page references, store them somewhere, and then produce the actual out
Bernd Brandstetter wrote:
memory would have to be available on every box. From what I've read on the
list, I'm sure this is due to excessive usage of forward references and
large (partly nested) tables spanning multiple pages. However, this is an
absolute requirement for our documentation.
From
> No. A forward reference is for example a fo:page-number-citation
> referring to a page after the current page, like in the
> overused "page X of Y" construct.
>
No offense, but if it's over-used, then it's probably because end users ask
for it. As a project lead I really wouldn't look forward t
John Bourke wrote:
Hi Bernd,
You seem to be in much the same predicament as I am. I have large tables on
recurring pages and like you I'm running out of memory. Does anybody no of a
way to implement tables without eating memory and what exactly do forward
references mean?
Is that like using the xpa
Hi Bernd,
You seem to be in much the same predicament as I am. I have large tables on
recurring pages and like you I'm running out of memory. Does anybody no of a
way to implement tables without eating memory and what exactly do forward
references mean?
Is that like using the xpath following comman
