[GUMP@brutus]: Project xml-fop (in module xml-fop) failed

2004-12-08 Thread Sam Ruby
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

Retrieve-marker and removal of leading and trailing spaces

2004-12-08 Thread Simon Pepping
Hi, I also noted a problem with the removal of leading and trailing spaces in connection with retrieve-marker: fo:static-content flow-name=xsl-region-after fo:block text-align=start fo:inline color=redfo:retrieve-marker retrieve-class-name=class retrieve-boundary=page

Another problem with Marker.rebind()

2004-12-08 Thread Simon Pepping
I noticed another problem with Marker.rebind(): When the same marker is retrieved more than once, the first rebind is overwritten with the second. See this example: fo:static-content flow-name=xsl-region-after fo:block text-align=start fo:inline color=redred: fo:retrieve-marker

Re: Retrieve-marker and removal of leading and trailing spaces

2004-12-08 Thread J.Pietschmann
Simon Pepping wrote: The spaces before `and' and after `blue:' are removed. This is probably due to the fact that the space removal mechanism does not recognize that fo:retrieve-marker elements may generate text. Whitespace/linefeed handling should run after rebinding the retrieved marker content

RE: Another problem with Marker.rebind()

2004-12-08 Thread Victor Mote
Simon Pepping wrote: Both markers are printed in blue. Perhaps it would be a solution to clone the subtree below the marker to retrieve-marker, and rebind that copy. That would be another example of layout dependent data in the FO tree. If every Just by way of clarification, this is no

Re: Another problem with Marker.rebind()

2004-12-08 Thread Peter B. West
Victor Mote wrote: Simon Pepping wrote: Both markers are printed in blue. Perhaps it would be a solution to clone the subtree below the marker to retrieve-marker, and rebind that copy. That would be another example of layout dependent data in the FO tree. If every There is a certain wry

Re: Another problem with Marker.rebind()

2004-12-08 Thread Glen Mazza
- Original Message - From: Peter B. West [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 8:20 PM Subject: Re: Another problem with Marker.rebind() Oh, I'm sorry, it involves re-thinking the building of the FO tree, using stream parsing. Peter, are you

Re: Another problem with Marker.rebind()

2004-12-08 Thread Peter B. West
Glen Mazza wrote: Oh, I'm sorry, it involves re-thinking the building of the FO tree, using stream parsing. Peter, are you saying that a pull parser is more computationally powerful than a SAX Parser--or is it just much more convenient? I don't think pull parsers can do more than SAX Parsers

AW: Embedding XMP in FO

2004-12-08 Thread Victor Röder
Hi Jeremias, you haven't told us what branch you are on. Are you on the maintenance branch or on FOP HEAD? I suppose I'm working with the 0.20.5 code base... These hints are targeted at FOP HEAD code but some can be applied to the maintenance branch, too, although the whole mechanism is