XSL-FO causing Fop 0.94 to go into an infinite Loop (Urgent)

Hi Attached here is an XSL-FO that causes the FOP 0.94 to go into an infinite loop. This is causing serious problems in our application. I narrowed down the problem to an fo:block /fo:block element placed within the footnote. This block element contains the character Â. This character

How to omitt a sequence

I have the following setup: 1. sequence for index page 2. sequence for the toc 3. sequence for the content Now when the content doesn't contain any element XY I don't want the toc page to be created at all. I surrounded the toc sequence like that: xsl:if test=count(XY) 0 fo:page-sequence

font problem ugrading from 0.93 to 0.94

Hi, I am having trouble upgrading from 0.93 to 0.94. Is there any significant change regarding font handling in 0.94? I get a java.lang.RuntimeException: Cannot load font. No font URIs available. I use a handrolled URIResolver, which shows no problems reading the fonts from the

Re: XSL-FO causing Fop 0.94 to go into an infinite Loop (Urgent)

Hi, Ankur Narain Bhardwaj ,Gurgaon wrote: Hi Attached here is an XSL-FO that causes the FOP 0.94 to go into an infinite loop. This is causing serious problems in our application. I narrowed down the problem to an fo:block /fo:block element placed within the footnote. This block

Re: How to omitt a sequence

MichaelNie wrote: snip/ xsl:if test=count(XY) 0 fo:page-sequence master-reference=PageMaster fo:flow flow-name=xsl-region-body fo:block xsl:call-template name=toc / /fo:block /fo:flow /fo:page-sequence /xsl:if If at

Re: Attribute Extension

You can let FOP ignore your extension namespace by registering it in the FopFactory: FopFactory fopFactory = fopFactory.ignoreNamespace(http://foo.com/mynamespace;); Or is this functionality you hacked into the old FOP and you have to reimplement it now? Jeremias Maerki On 15.11.2007

Re: Attribute Extension

Our software uses the old version of FOP, and I am attempting to upgrade to the new version. Unfortunately, several custom attributes were added to the xml. fo:block-container annotation container-name overflow-to smallest-font-size fo:simple-page-master page-group

Re: font problem ugrading from 0.93 to 0.94

Alexander Lohse wrote: Hi, I am having trouble upgrading from 0.93 to 0.94. Is there any significant change regarding font handling in 0.94? Yes, Font autodetection was added which saw some major changes in the way Font Configuration works. There was also a change around the handling or

Re: Attribute Extension

This is functionality that was hacked into the old framework. Now I am stuck cleaning up the mess. I would like to implement all of the functionality with extensions so we avoid this problem in the future. I did see some conversations in the mail archive about attribute extensions. Are there

Re: Attribute Extension

Well, there are limits what can be done with extensions. At the moment, it is mainly possible to access extension attributes from within the existing code (built-in extensions). If your extensions affect the workings of layout managers, for example, you might need to extend them and register them

Fop layout question

Gentlepeople Assume the following fo structure fo:block-container width=600pt top=0pt overflow=hidden left=0.0pt height=280pt absolute-position=fixed fo:block linefeed-treatment=ignore fo:block margin-top=aa text-align=left line-height=bb fo:inline

Re: Capturing FOP logging message event in an embedded application using FOP 0.94

On Nov 14, 2007, at 13:24, Michael Tracey Zellmann wrote: Hi Sorry for the late reply... Thanks for the response. I am trying to think of a way to still succeed. What I want to do is to send all logging messages from anything related to FOP to their own file. In the logging.properties,