> A big problem I can currently see is that all normal text has white
> color, so initially you see practically nothing. Selecting all text and
> applying black color brings the text to light.
Yes, i can confirm that behaviour. A simple example looks good in Word
97/2000,
but Wordpad displays the
Jeremias Maerki wrote:
> Yep, current CVS code generates working RTF code (on my machine). I've
> opened readme.fo (-->readme.rtf) in Wordpad and OpenOffice, for example.
> A big problem I can currently see is that all normal text has white
> color, so initially you see practically nothing. Select
Yep, current CVS code generates working RTF code (on my machine). I've
opened readme.fo (-->readme.rtf) in Wordpad and OpenOffice, for example.
A big problem I can currently see is that all normal text has white
color, so initially you see practically nothing. Selecting all text and
applying black
Incidentally, for 1.0, I had difficulty in getting RTF
to work with simple FO documents. It seems to
generate an RTF-based script, but Windows isn't
accepting it on my machine. Wordpad just opens it up
as text, showing the underlying RTF script-code. Has
anyone else tried the 1.0 RTF renderer?
No, the examples are quite ok actually. It's the Driver class that has a
problem in getContentHandler(). Sorry for not being clear enough. By the
way, you mentioned you're interested in RTF output which shoudn't be
affected by this problem. The code in ExampleObj2PDF should work fine if
you use RTF
OK ... Thanks.
Is it just that samples that are broken? I'm just looking for some "embedding FOP sample code" esp. for the Object to PDF.
If this is the case, is there code other places I could look at. (for example the command line tool "fop.bat")
Thanks,
-Will>>> [EMAIL PROTECTED] 11/