Finn Bock wrote:
The loop can be stopped when we temporary run out of FO tree nodes
and restarted again when new nodes has been added. I suppose that the
FO tree can then be viewed as a stream of FO nodes.
[Victor]
This model probably works fine if you never need to look ahead, but there
are nu
The loop can be stopped when we temporary run out of FO tree
nodes and restarted again when new nodes has been added. I
suppose that the FO tree can then be viewed as a stream of FO nodes.
[Victor]
This model probably works fine if you never need to look ahead, but there
are numerous examples (w
sounds good to me... +1
On Dec 12, 2004, at 8:01 AM, Glen Mazza wrote:
Team,
Silly confirmation question here -- is the 1.1 XSL
Spec's fo:bookmark-tree, fo:bookmark, and
fo:bookmark-title [1] basically the same thing as our
fox:bookmarks, fox:outline, and fox:title,
respectively? (i.e., they're f
Team,
Silly confirmation question here -- is the 1.1 XSL
Spec's fo:bookmark-tree, fo:bookmark, and
fo:bookmark-title [1] basically the same thing as our
fox:bookmarks, fox:outline, and fox:title,
respectively? (i.e., they're for off-document PDF
bookmarks?) Its mandated location [2] in the FO i
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-fop has an issue affecting its community integration.
This issue affects 1 pr
