Andreia Oliveira wrote:
Thanks Chris.
I was hoping that I could solve my problem without migrating to a new Fop
version.
Can you please give me some instructions on the steps to perform this
migration? From were it can be downloaded and what do I have to properly
install it?
Andreia,
FOP
Hi all,
we've a project in which fop20.5 is already working for many year. now
we wants to add some new features and are not sure if it is possible to
use 20.5 and the trunk version in the same application.
all jars are in the same classpath
has someone some experience with this?
we
Thanks for answer, so i'll have a look at it.
Dirk
Jeremias Maerki wrote:
Yes, I do have experience with that. I've written a wrapper API for
XSL-FO implementations [1] where I support exactly that: Support
multiple FO implementations in the same VM. For that to work you have to
isolate the
Here is a trimmed-down model of the XML.
test-case-documents
directory @name=dir-1
directory @name=dir-1-1
file
nameTC_01/name
.. More elements here ..
/file
/directory
/directory
test-case-documents
This is the template in question:
xsl:template
This might be useful. It is a block of markup from the from the XSL-FO document
produced by the template.
fo:block text-align-last=justify
fo:in-lineTC_01fo:leader leader-pattern=dots/
fo:page-number-citation ref-id=TC_01/
/fo:in-line
/fo:block
--
On Mar 3, 2006, at 18:15, [EMAIL PROTECTED] wrote:
Hi Charles / Jay,
The quote below is from the fo:page-number-citation section of the
recommendation. I find the construction id trait puzzling. It
seems that the authors have gone out of their way to avoid the term
attribute,
Hmm...
I'm back. Just when I thought it was safe to go back into the water (cue
bass violin and muted trumpets);
fop 0.20.5 is processing the XSL-FO document without complaint. I've still got
some minor formatting issues to deal with, but I have one huge problem, no page
numbers appear in the
As you can see from my trimmed-down data model. I have no id attribute. That
issue is what I thought I was asking about when you replied:
It is certainly true that the value of ref-id can be an element rather than
an attribute.
So it appears that I misunderstand the question of what has to be
My bad, Charles.
I was thinking of the input file rather than the FO when I responded to your
initial question. Sorry about the confusion.
I would add the id attribute to the block (or table or whatever) that
contains the content of the source-document node you want to reference.
So, if I had a
All is forgiven! I got everything worked out. There were a lot more warts on
that toad than I thought, but I've knocked out every one.
Thanks again.
--
Charles Knell
[EMAIL PROTECTED] - email
-Original Message-
From: Jay Bryant [EMAIL PROTECTED]
Sent: Fri, 3 Mar 2006 14:12:48
10 matches
Mail list logo