I think you will have better luck if you post this kind of question to the XSL
list at http://www.mulberrytech.com/xsl/xsl-list/index.html, but that
notwithstanding, I looked over your file to see if I could help.
I had some problem with the encoding, so in order to proceed I removed the
Can someone give me some guidance on this error message? Thanks.
[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser
[INFO] FOP 0.20.5
[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser
[INFO] building formatting object tree
[INFO] setting up fonts
[INFO] [1]
[ERROR]
You have shown what you expect to appear in the XSL-FO document, but not what
actually does appear there. Consequently, it's hard to say where you are going
wrong. With what information you have supplied, the second construction (the
one using copy-of) appears to be the correct one.
Show what
I had a similar problem when printing to a laser printer. I solved it by
placing a white rectangle behind the image.
rect fill=white x=0 y=-400 width=1600 height=1600 /
--
Charles Knell
[EMAIL PROTECTED] - email
-Original Message-
From: Zmitko, Jan [mailto:[EMAIL PROTECTED]
Sent:
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
--
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
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
I've just had a look at CML. What a nightmare! Take this element, for example,
CML.TAB ID=table1 NAME=NET ATOMIC CHARGES ROWS= 12 COLUMNS=3
COL.NAMES=ELEMENT CHARGE DENSITY COL.REFS=CML.COR.NOTATION CML.THE.CHARGE
CML.THE.AEDENSITY COL.TYPES=STRING FLOAT FLOAT
C -0.102123
Since MathML is XML and SVG is XML, the natural way to convert one to another,
as I see it, is with with XSLT. Are you looking for a ready-made Java package
with classes to produce a variety of SVG formats, or are you looking for a
general approach?
--
Charles Knell
[EMAIL PROTECTED] - email
From an efficiency point of view, wouldn't it be better to have a select
(that filters odd elements) in the xsl:apply-templates so that the second
template gets called 1/2 the total number of cityInstal?
If you did that, then you would have to make an empty template for the
complementary set
Your XSLT processor still has to examine each cityInstal element to select
only those that match the select statement. Without empirical testing we still
don't know which is more efficient (faster).
--
Charles Knell
[EMAIL PROTECTED] - email
-Original Message-
From: Cinzia [EMAIL
It's the same pattern.
xsl:template match=country
xsl:if test=position() mod 2 =1
fo:table-row
fo:table-cellfo:blockxsl:value-of select=cityInstal
//fo:block/fo:table-cell
fo:table-cellfo:blockxsl:value-of select=stateInstal
//fo:block/fo:table-cell
I' recently back to working with FOP. I have a document that consists of a
number of tables with widely-varying numbers of rows. Sometimes several tables
will fit entirely onto a single page, with others will span several pages. The
problem I'm having involves those cases where a table almost
I know that if a table has 20 or more rows, it won't fit on a single page. I
deal with such large tables in my XSLT like this:
xsl:template match=table
xsl:variable name=page-break-flag
xsl:choose
xsl:when test=count(child::column) gt; 19page/xsl:when
I recently downloaded FOP version 0.94, upgrading from 0.92beta. My build.xml
file now fails when I execute the fop task, giving this error:
build.xml:105: java.lang.NoClassDefFound
Error: org/apache/xmlgraphics/util/Service
It seems that something has changed in FOP that breaks the Ant FOP
Maybe you want this, instead.
xsl:if test=@statusImageURL
fo:block
fo:external-graphic src=[EMAIL PROTECTED]/
xsl:value-of select=@status/
/fo:block
/xsl:if
--
Charles Knell
[EMAIL PROTECTED] - email
-Original Message-
From: Daling Xu [EMAIL PROTECTED]
Sent: Fri,
Please disregard. I didn't read your message closely enough.
--
Charles Knell
[EMAIL PROTECTED] - email
-Original Message-
From: [EMAIL PROTECTED]
Sent: Fri, 30 Nov 2007 14:01:45 -0500
To: fop-users@xmlgraphics.apache.org
Subject: RE: anything wrong with this XSL snippet
19 matches
Mail list logo