Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF

2005-12-15 Thread Jeremias Maerki
(some comments inline...) On 13.12.2005 22:02:52 JBryant wrote: Hi, Jeremias, Jay, if you'd like to help systematic testing here that would be fantastic. Please note that quite a few test cases already exist in test/layoutengine/standard-testcases (everything that starts with

Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF

2005-12-13 Thread JBryant
Hi, Jeremias, Jay, if you'd like to help systematic testing here that would be fantastic. Please note that quite a few test cases already exist in test/layoutengine/standard-testcases (everything that starts with external-graphic and instream-foreign-object). Please note that the size

Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF

2005-12-11 Thread Jeremias Maerki
PROTECTED] To: fop-users@xmlgraphics.apache.org Sent: Saturday, December 10, 2005 3:09 PM Subject: Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF On Dec 10, 2005, at 22:03, Andreas L Delmelle wrote: fo:external-graphic src=... width=auto content-width=auto

Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF - workaround found

2005-12-10 Thread Andreas L Delmelle
On Dec 10, 2005, at 00:34, [EMAIL PROTECTED] wrote: Hi Jay, After reading the spec, I thought of trying to make the image a fixed width, so I tried fo:external-graphic src=someimage.gif content-width=5.5in/ That makes images less than 5.5 inches wide be 5.5 inches wide, Errm... Now you're

Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF

2005-12-10 Thread Andreas L Delmelle
On Dec 10, 2005, at 00:14, [EMAIL PROTECTED] wrote: Hi Jay, See above: If you're not overriding the default resolution, this is caused by the fact that 528px is 7.33in in the default resolution. I don't think that's the issue. The algorithm in that template is if the image is more than

Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF

2005-12-10 Thread Andreas L Delmelle
On Dec 10, 2005, at 22:03, Andreas L Delmelle wrote: fo:external-graphic src=... width=auto content-width=auto height=auto content-height=scale-to-fit scaling=non-uniform / Correction: this is OK - width/height = auto means use content-size - content-height=scale-to-fit, so

Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF

2005-12-10 Thread Jay Bryant
see what I can do along that line. Jay Bryant Bryant Communication Services - Original Message - From: Andreas L Delmelle [EMAIL PROTECTED] To: fop-users@xmlgraphics.apache.org Sent: Saturday, December 10, 2005 3:09 PM Subject: Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF

0.90alpha1: content-width=scale-to-fit creates damaged PDF

2005-12-09 Thread JBryant
I wrote an extension function in Java for Saxon that gives me the width (and height, but that's less relevant) of an image. Then, if the width is greater than 5.5 inches (the space I have available for screen shots in this document format), the XSLT adds the content-width=scale-to-fit

Re: 0.90alpha1: content-width=scale-to-fit creates damaged PDF - workaround found

2005-12-09 Thread JBryant
An additional update to my testing: After reading the spec, I thought of trying to make the image a fixed width, so I tried fo:external-graphic src=someimage.gif content-width=5.5in/ That makes images less than 5.5 inches wide be 5.5 inches wide, but the PDF file created by FOP still blows up