Jeremias Maerki wrote:
Sounds like you XML parser doesn't provide namespace information. You
may have to enable that feature. What XML parser and XSLT implementation
do you use? FOP is by default using Apache Xerces and Xalan which work
fine.
I use the software pretty out of the box so they're
[EMAIL PROTECTED] wrote:
I have a little problem to detect page breaks using xsl:fo...
You cannot detect page break, you are not programming in xsl-fo. You should
think in declarative way instead, e.g. just declare that odd pages should have
gray border on the right, even pages - on the left
Santtu Pajukanta wrote:
I use the software pretty out of the box so they're Xerces and Xalan.
Here's what it outputs when I try to process
xml-fop/docs/examples/markers/glossary.xml:
D:\Java\tools\fop-0.20.5rc\docs\examples\markersfop glossary.xml
glossary.pdf
[INFO] Using
I haven't used Illustrator myself before but have you tried playing
around with the export setting such as convert text to graphics or not
embedding but only referencing the fonts?
If you download Batik standalone and start Squiggle (the SVG browser)
can it display the generated SVG? If no, then
David and Harm,
I've just found the bugs, I think. I've fixed them in CVS and checked
them against 3 different SVG files generated by OpenOffice. They work
fine now. Either download FOP from CVS or wait until version 0.20.5rc2
which should be out on Monday.
Technical background:
I've found 0 0 0
Sorry for the delay. I've looked up that private discussion with Claes
Bergsten. The theory is that that particular Xerox PDF RIP has a bug in
the PDF to PostScript conversion which causes the subsequent PostScript
RIP to choke on PDF XObjects (which are normally used to hold images).
You don't
J.Pietschmann wrote:
That's the command line for formatting a FO document into PDF. Why
do you expect FOP to apply a style sheet without even naming it on
the command line?
Use
fop -xml glossary.xml -xsl glossary.xsl -pdf glossary.pdf
You might alsoo want to look into the FOP documentation, in
