docbook-apps message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Fop unable to render tables ? (without intervention ?)
- From: "Kerry, Richard" <richard.kerry@siemens.com>
- To: <docbook-apps@lists.oasis-open.org>
- Date: Mon, 17 Dec 2007 14:12:55 -0000
I have a DocBook
document which I wish to convert to pdf and I'm having a problem with Fop
rendering the tables.
I've used the Xsl
stylesheet to convert it to Xsl-Fo. Originally with no parameters
set. I then use Fop version 0.94 to generate pdf.
The DocBook document
contains several tables, one in particular is very large, and will stretch over
several pages of the final document (another is perhaps just a little over the
size that should fit on one page).
The two symptoms I
had were :
1. There were
many error messages from Fop.
2. The tables
in the pdf file were attempting to display on one page each, which seems
wrong.
The Fop error
messages were as follows :
17-Dec-2007 13:34:19
org.apache.fop.fo.FONode attributeWarning
WARNING: Warning(994/42): fo:table,
table-layout="auto" is currently not supported by FOP
Once for each
table.
Then
17-Dec-2007 13:34:20
org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm
updateData2
WARNING: Line 1 of a paragraph overflows the available area.
(fo:block, location: 2481/70)
Many times.
Possibly once per expected resulting page.
I am assuming that
these error messages indicate the reasons why the large tables were not rendered
properly.
So what I'd like to
know is :
How can I stop this
happening ?
Do I need to do
something to change table-layout to something other than "auto", and if so how
do I pass this in ?
I expected that
tables would just go through on the nod, and work without intervention, as they
would seem to be a very common part of a technical document.
Uncertainly,
Richard.
PS.
Fop is version 0.94,
which I think is the latest.
Xsl template
processing is being done by Saxon 6.5.5, which I believe is the most recent
Saxon-6.
I've also done the
xsl processing using Saxon 9.0.0.1j, which gives almost exactly the same xsl-fo
file output, except that it can be told to indent its output which I don't
believe Saxon-6 can (see question by me last week), and I don't care to try
reading unindented xml........
PPS
When I say
"Originally with no parameters set." I mean that in order to stop getting
messages about not being able to fetch the draft picture I'm now setting
"draft.mode=no", and I'm now also setting "paper.type=A4" as I'm in
Europe. As well as "!indent=yes", which only afects Saxon-9, to get the fo
indented.
Richard
Kerry
Colledia Control
Engineer
Siemens
IT Solutions and Services Ltd
Room 457 Design Building, BBC
Television Centre, Wood Lane, London, W12 7RJ
T: +44 (0)20
82259063 F: +44 (0)20 8576 8182 M: +44 (0)7921 244993
Email: richard.kerry@siemens.com
Website: www.siemens.co.uk/it-solutions
This e-mail contains
confidential information and is for the exclusive use of the addressee/s.
If you are not the addressee, then any distribution, copying or use of this
e-mail is prohibited. If received in error, please advise the sender and delete
it immediately. We accept no liability for any loss or damage suffered by
any person arising from use of this e-mail.
Siemens IT Solutions
and Services Limited
Registered
No: 1203466 England
Registered Office: Faraday House, Sir William Siemens
Square, Frimley, Camberley, GU16 8QD
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]