looks exactly like the tree we need when written to a
file.
Humm... need to thyink about that one for a while...
$ -Original Message-
$ From: Michiel Verhoef [mailto:[EMAIL PROTECTED]
$ Sent: donderdag 27 juni 2002 8:02
$ To: '[EMAIL PROTECTED]'
$ Subject: RE: Weird behaviour of Apache fop
file and then feed this
to fop.
$ -Original Message-
$ From: Oleg Tkachenko [mailto:[EMAIL PROTECTED]
$ Sent: donderdag 27 juni 2002 11:36
$ To: [EMAIL PROTECTED]
$ Subject: Re: Weird behaviour of Apache fop
$
$
$ So, just transform to string and give the string to fop, no
$ big deal
to change the XML, but you can change what you do with
it :)
Charlie
-Original Message-
From: Michiel Verhoef [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 27, 2002 4:43 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Weird behaviour of Apache fop
Unfortunately we're in a non Java environment
]
$ Sent: maandag 24 juni 2002 21:46
$ To: [EMAIL PROTECTED]
$ Subject: Re: Weird behaviour of Apache fop
$
$
$ Michiel Verhoef wrote:
$ Hi all,
$
$ Currently we have a weird problem: when converting an XML
$ file (or rather,
$ an XML-ified HML source) to a FO file and
$ converting
Your xsl stylesheet is so bizarre... What are you using all these CDATA
sections for? Why are you using
![CDATA[fo:block/fo:block]]
instead of just
fo:block/fo:block ?
Actually your xsl stylesheet works if and only if transformation result (fo
document) is serialized and then reparsed again,
the way you suggested and see what happens
(although that's how I started out)
Michiel
$ -Original Message-
$ From: Oleg Tkachenko [mailto:[EMAIL PROTECTED]
$ Sent: maandag 24 juni 2002 17:12
$ To: [EMAIL PROTECTED]
$ Subject: Re: Weird behaviour of Apache fop
$
$
$ Your xsl stylesheet
Michiel Verhoef wrote:
Hi all,
Currently we have a weird problem: when converting an XML file (or rather,
an XML-ified HML source) to a FO file and
converting this resulting FO file to a PDF all things are fine. However,
when we try to convert the XML with the exact
same XSL script into a PDF we