What you want is not implemented, yet. "auto" currently causes the image to be set to the image's intrinsic size. No checks are done to ensure the image fits in the available area. The code will need to be refined to support this.
On 23.05.2006 14:10:26 Ståle Undheim wrote: > I have done a little search, and found this message on the mailinglist: > http://article.gmane.org/gmane.text.xml.fop.user/17545/match=external+graphic+scaling+50+attempts > > Here is what I want: > If my image is smaller than the available width, do nothing. If its > bigger, scale it down. > > However, no combination of properties unless I set explicit width seems > to work for larger images. Something thats not a good solution since I > am converting from a docbook document to pdf. > > I did some debugging, and to me it looks like the > "block-progression-dimension" and "inline-progression-dimension" always > get set to auto in the java objects, no matter what I specifiy in the fo > file. This is what is suggested you should do in the above mentioned > mail, but its not working for me. > > This is the sequence I use inside a page: > <fo:flow flow-name="xsl-region-body"> > <fo:block>Image:</fo:block> > <fo:block> > <fo:external-graphic > src="path-to-large-image" > width="auto" > height="auto" > content-width="scale-to-fit" > content-height="scale-to-fit" /> > </fo:block> > </fo:flow> > > Are there any rules I can apply that will work for all images as I > described above, that is implemented in FOP 0.92beta? Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
