On 4/27/07, T.G. Mutato <thro...@gmail.com> wrote:

I think the bottom line here is that specifying pixel dimensions (if you want to display an image "as-is") isn't too useful with FOP since there's no way to way to tell FOP to ignore the dpi info. So far just setting the dpi to 96 in the image files themselves seems to be the only way to get them to display properly.

Have you tried changing the source-resolution and target-resolution values in the FOP config file?

<!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi --> <source-resolution>72</source-resolution> <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi --> <target-resolution>72</target-resolution>

Not sure if this actually makes a difference here, but I've never changes these settings, so I'm just curious.

Colin

On 4/27/07, Chris Chiasson <chr...@chiasson.name> wrote: > Assuming the matrix of pixels for an image is fixed, changing the dpi > of the picture is like telling the receiving application that the > image takes up different physical sizes: > > example: > A 100 pixel by 100 pixel picture at 100 dpi (in both horizontal and > vertical directions) = 1 inch by 1 inch picture. > > Supplying the same pixels and saying the picture is at 300 dpi will > give a 1/3 inch by 1/3 inch picture. > > This doesn't happen in web browsers because they ignore picture dpi, AFAIK. > > So, it makes sense that your 300 dpi picture is smaller if it has the > same pixel content as the other pictures. > > I assume you already knew all of this and that the scaling attributes > of DocBook are confusing to you. In that case, can we start over? I am > lost. >

--------------------------------------------------------------------- To unsubscribe, e-mail: [1]docb...@lists.oasis-open.org For additional commands, e-mail: docb...@lists.oasis-open.org

References

Visible links 1. mailto:docb...@lists.oasis-open.org