Hi,
the space-before behaviour inside a table(-cell) changed.
Have a look at output0.20.5.pdf and output0.91.pdf.
Which is right?
Regards,
Joachim
addresses
address
companyString/company
name title=1
surnameJoachim/surname
lastnameUnger/lastname
/name
streetString/street
Thanks for the reply.
I will certainly post an example when I get it done. The first cut will just
be functional, and needs some feedback from the customer to get the layout
and details right.
Regarding Tables in FOP, I was reading Dave Pawson's book XSL-FO from
O'Reilly. His quote is:
Hi,
for the last few month I worked with xml structures like these:
para
For these tasks the menu
italicTest/italic
provides the function
italicMask/italic
/para
Until now the text was formated (see below) in the order of appearance
in the tree! That was at least for my
I can just about guarantee that the trouble is not Saxon (which I use every
day). The trouble lies in your stylesheet, where I strongly suspect you are
applying templates by selecting nodes rather than applying all templates
(something like xsl:apply-templates select=italic/ rather than
I am having some trouble gettiong an instream svg
image into my fop document, and hope that soemone in this formum might
help.
I have an xml document, which contains several svg
images, as well as other content. Some of the images were created from a
template developed through Microsoft
Joachim,
as described in [1] reusing Fop instances is discouraged in 0.90 and
later. I'm currently working on a few changes that will address
performance considerations around reusable objects in FOP. The Fop
instance (and to a certain degree the FOUserAgent instance) are designed
to be one-use
0.91, of course. :-) What you're seeing here is the effect of the
(now implemented) conditionality sub-property on space-before and
space-after. Its default is discard which causes spaces at the
beginning or at the end of a so-called reference area (which the
table-cell generates) to be discarded.
As you've already seen, these are only warnings. You can ignore them
without further consequence.
The reason for the warning is that FOP currently expects that all
namespaces used in an FO document be known to it. In your case, this
backfired. Nils Meier raised a similar topic on fop-dev earlier
