Which Batik version in FOP 0.20.3

2002-06-07 Thread Vollmer, Thomas - CannonSA
Hi all, I'm using FOP 0.20.3 and I'm wondering which version of Batik (fop-0.20.3\lib\batik.jar) it comes with exactly. Can anyone provide some insight? Thanks, Thomas If this email is not intended for you, or you are not responsible for the delivery of thi

RE: Which Batik version in FOP 0.20.3

2002-06-07 Thread Vollmer, Thomas - CannonSA
cluded in that release. > Christian, will the readme file be in the next release? > I think it also needs to be updated with the versions of other jar > files. > > On Fri, 2002-06-07 at 02:53, Vollmer, Thomas - CannonSA wrote: > > Hi all, > > > > I'm using F

Problem with not stroking SVG text (AND BUG IN FOP 0.20.3)

2002-06-08 Thread Vollmer, Thomas - CannonSA
Hi all, I am trying to get FOP (0.20.3) to not stroke text when converting SVG to PDF. I've tried everything and can't get it to work. Here's the code I'm using to convert SVG to PDF: --- PDFTranscoder pdfTranscoder = new PDFTranscoder(); // Insertion Point (see below) try { FileInputStre

RE: Which Batik version in FOP 0.20.3

2002-06-10 Thread Vollmer, Thomas - CannonSA
x27;t remember if there where any changes between those > versions that > would cause problems. > > On Fri, 2002-06-07 at 19:47, Vollmer, Thomas - CannonSA wrote: [snip] > > Keiron, can you confirm that for the purposes of > FOP/Batik-integration it > > makes

RE: Problem with not stroking SVG text (AND BUG IN FOP 0.20.3)

2002-06-10 Thread Vollmer, Thomas - CannonSA
Keiron wrote: > try using: > addTranscodingHint > > you are removing transocding hints with the setTranscodingHints. Actually, that's not the case. Notice that I'm calling "public void setTranscodingHints(Map hints)" and NOT "public void setTranscodingHints(TranscodingHints hints)". The first d

RE: Problem with not stroking SVG text (AND BUG IN FOP 0.20.3)

2002-06-11 Thread Vollmer, Thomas - CannonSA
Keiron wrote: > I stand corrected. > It does need to be a BooleanKey to work properly. [...] > Once I fixed that it doesn't work anymore anyway. > > I think various changes in batik mean that it needs > to be handled differently. Not sure what you mean by that. Why won't making it a BooleanKey

RE: Problem with not stroking SVG text (AND BUG IN FOP 0.20.3)

2002-06-11 Thread Vollmer, Thomas - CannonSA
> -Original Message----- > From: Vollmer, Thomas - CannonSA [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 11, 2002 12:57 PM > To: '[EMAIL PROTECTED]' > Subject: RE: Problem with not stroking SVG text (AND BUG IN > FOP 0.20.3) > > > Keiron wrote: > &

RE: Problem with not stroking SVG text (AND BUG IN FOP 0.20.3)

2002-06-13 Thread Vollmer, Thomas - CannonSA
Keiron wrote: > As I said before. When converting FO to PDF it uses the Configuration. > When doing SVG to PDF it (should) uses the batik transocding hints. > > Whether it is stroked or not depends on how batik is setup with the > code. The transcoder that converts SVG to PDF sets it up in a > pa

RE: Problem with not stroking SVG text (AND BUG IN FOP 0.20.3)

2002-06-13 Thread Vollmer, Thomas - CannonSA
Keiron wrote: > > How is the current CVS trunk different from the 0.20.3 release > > in terms of this issue? > > The trunk is updated to work with the current batik (cvs). Ok, thanks. > The text is shapes or not depending on whether it is possible to use > plain text in the pdf document or not.

Why is there a margin at the top?

2002-06-18 Thread Vollmer, Thomas - CannonSA
Hi all, I'm using FOP 0.20.3 to create PDF from SVG and I'm encountering a problem with an unexpected margin at the top of the PDF page. I attached two small fo files and the resulting PDF files. As the attachments show it doesn't seem to be an SVG related problem. Even the text has a margin at

RE: Why is there a margin at the top?

2002-06-19 Thread Vollmer, Thomas - CannonSA
there a margin at the top? > > > Vollmer, Thomas - CannonSA wrote: > > I'm using FOP 0.20.3 to create PDF from SVG and > > I'm encountering a problem with an unexpected > > margin at the top of the PDF page. > ... > > I'm new to XSL-FO so I might be ov