On 9 Oct, 2010, at 12:10 , Wolfgang Hugemann wrote: > This is caused by the relative ordering of the 'density' statement and > the input file. Try the following simple example: > > convert -size 200x200 xc:blue test.pdf > > This will embed a raster image of 200x200 pixels into a PDF. > Then try > > convert test.pdf -density 200x100 post.tif > convert -density 200x100 test.pdf pre.tif > > It will turn out that post.pdf will have 200x200 pixels and pre.pdf will > have will have 556x278 pixels. > > In the first command, the PDF is read assuming equal resolution in x- > and y-direction and the resolution of the TIF ist set to 200x100. > > In the latter case, the PDF is read assuming a resolution of 200x100 > (instead of the 72x72 standard resolution), resulting in dimensions of > 200*200/72 = 556 in the x-direction and 200*100/72 = 278 in the y-direction.
Thanks for you help. I am using Paperclip for Rails (which uses imagemagick) to convert the images. Since the solution with changing the filename position does work I just wrote my own processor for Paperclip and moved the filename position. I was just curios why that was happening. > > Greetings from Münster, Germany cool ... did spend quite some time in Muenster. Greetings from Vienna. Cristian Livadaru > Wolfgang Hugemann > _______________________________________________ > Magick-users mailing list > [email protected] > http://studio.imagemagick.org/mailman/listinfo/magick-users _______________________________________________ Magick-users mailing list [email protected] http://studio.imagemagick.org/mailman/listinfo/magick-users
