RE: [docbook-apps] QandA sets misaligned when using FOP 0.20.5

["Nelson, Dean" <dean.nelson@eecradar.com>]

FOP 0.93 fixed this issue along with the updated stylesheets (1.71.1).

Dean Nelson   
Sr. Software Engineer
Enterprise Electronics Corp
http://www.EECradar.com   

"Obstacles are those frightful things you see when you take your eyes
off your goal." - Henry Ford


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed.  If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited.  If you have received this e-mail in error, please notify
the sender by replying to this  message and delete this e-mail
immediately.




-----Original Message-----
From: Bob Stayton [mailto:bobs@sagehill.net] 
Sent: Wednesday, January 10, 2007 6:21 PM
To: Nelson, Dean; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] QandA sets misaligned when using FOP 0.20.5


Hi Dean,
You need to use DocBook XSL 1.71.1 and set the stylesheet parameter 
fop1.extensions=1 to avoid that error.  Since 0.93 just came out, it 
remains to be seen how well it works with DocBook XSL, but my initial
tests 
are encouraging.  This is a long-awaited release, and it makes me more 
inclined to fix FOP-related issues.  Bug reports welcome (best reported
on 
the DocBook SourceForge site).

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Nelson, Dean" <dean.nelson@eecradar.com>
To: "Bob Stayton" <bobs@sagehill.net>;
<docbook-apps@lists.oasis-open.org>
Sent: Wednesday, January 10, 2007 8:03 AM
Subject: RE: [docbook-apps] QandA sets misaligned when using FOP 0.20.5


Ok - I have been leary of the FOP betas but since it is now production 
level, is Docbook XSL 1.70.1 completely compatible with it?

The reason I ask is that 0.93 produces the following error when I use
FOP 
0.93

Jan 10, 2007 9:56:44 AM org.apache.fop.cli.Main startFOP
SEVERE: Exception
java.lang.IllegalStateException: Flow 'xsl-region-body' does not map to
the 
region-body in page-master 'blank'.  FOP presently does not support
this.
        at 
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168)
        at
org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
        at org.apache.fop.cli.Main.startFOP(Main.java:160)
        at org.apache.fop.cli.Main.main(Main.java:191)


I'm not a XSL or FO guru, but it appears that FOP is more stringent on
some 
things than 0.20.5 is. Would moving to 1.71.1 fix this problem?

Dean

-----Original Message-----
From: Bob Stayton [mailto:bobs@sagehill.net]
Sent: Tue 1/9/2007 9:59 PM
To: Nelson, Dean; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] QandA sets misaligned when using FOP 0.20.5

The qandaentry elements are formatted with a fo:list-item.  The problem
is 
the fop-0.20.5 does not ignore the space-before property in the 
list-item-body, when the spec says it should.  Try the newly released
fop 
0.93.  It handles list-blocks better.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net



----- Original Message ----- 
From: Nelson, Dean <mailto:dean.nelson@eecradar.com>
To: docbook-apps@lists.oasis-open.org
Sent: Tuesday, January 09, 2007 6:57 PM
Subject: [docbook-apps] QandA sets misaligned when using FOP 0.20.5

Does anyone know why the QandA stylesheets misalign the question number 
with FOP 0.20.5 going out to PDF? They end up with the numbers on the
line 
above the question.

This is using the standard Docbook XSL 1.70.1 fo/docbook.xsl sheet.

This came up before and I tried to fix it, but came up empty. It works 
right with XEP and the standard sheets.

Dean Nelson
Sr. Software Engineer
Enterprise Electronics Corp
http://www.EECradar.com <http://www.eecradar.com/>

"Obstacles are those frightful things you see when you take your eyes
off 
your goal." - Henry Ford


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to

which it is addressed.  If the reader of this e-mail is not the intended

recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited.  If you have received this e-mail in error, please notify
the 
sender by replying to this  message and delete this e-mail immediately.