Solved the issue!

#PDF #FOP #XSLT

Hi dita experts, as title says, I'm trying to automatically generate title for <screenshots> every time when it comes up in my documentation. It should be same as section titles, but not the titles li

#PDF #FOP #XSLT

Not really sure, it was the decision authors made together, I'm just there as technical support.

#FOP #XSLT #PDF

The real question is why are you messed that deep? That number of levels must be frustrating to authors and readers. Julio J. Vazquez

#FOP #XSLT #PDF

Hi, By default 6th level don't have bold as font-style. I think you have to modify following attribute set (that corresponds to 6th level) to change font-style as you want. <xsl:attribute-set name="to

#FOP #XSLT #PDF

Looking at the FOP 2.4 code I can see the call sequence and the coding error that is almost certainly the cause of the runtime failure (the code as written makes an assumption that doesn't hold in thi

#FOP #PDF

I can reproduce the failure using FOP run directly from Oxygen against the FO file, which I think is FOP 2.3. Probably an FOP bug--the block is within a list block, which might be contributing to the

#FOP #PDF

Hi Eliot. I haven't tried using the latest version of FOP. I'm honestly not sure how to make that switch. Just swapping out the jar files or even the FOP plugin did not work. All kinds of "missing..."

#FOP #PDF

Can you post the FO for a page that ends with the code block? The message sounds like maybe an FOP bug. Have tried using the latest version of FOP? 2.4 was recently released (which includes support fo

#FOP #PDF

PDF2 customization, OT 2.5.4, FOP. Codeblocks are not breaking across pages. When a codeblock is/would be the last thing on a page and it can't fit entirely on the page, the build breaks with a "Posit

#FOP #PDF