[Solved] Problem with ps to png multi-page output

Questions and postings pertaining to the usage of ImageMagick regardless of the interface. This includes the command-line utilities, as well as the C and C++ APIs. Usage questions are like "How do I use ImageMagick to create drop shadows?".
Post Reply
DaPony

[Solved] Problem with ps to png multi-page output

Post by DaPony »

I have got a problem with
ImageMagick 6.5.5-7 2009-09-07
on
Ubuntu 9.04 x64

I want to convert all pages of a ps to several png:

convert -density 600x600 Tmp.ps -trim +repage -bordercolor white -border 3 Tmp_page.png

Tmp.ps consists of 2 pages.

I expected to receive:

Tmp_page-0.png Tmp_page-1.png

I received:

Tmp_page.png

Tmp_page.png shows what I would have expected to be in Tmp_page-0.png

The command:

convert -density 600x600 Tmp.ps'[1]' -trim +repage -bordercolor white -border 3 Tmp_page.png

does not work either, I always get page 1, '[0]' in my png.

This problem did not occur about two or three months ago, when I wrote a
shell script that used Tmp_page-[[:digit:]]\+.png to catch the results.
I used Ubuntu 8.10 x64 and an ImageMagick version a few weeks before
version 6.5.5-7 2009-09-07 back then.

Have there been any changes to ImageMagick since maybe July 2009 or so
that could have caused this change in behaviour?
Last edited by DaPony on 2009-11-28T04:12:17-07:00, edited 1 time in total.
DaPony

Re: Problem with ps to png multi-page output

Post by DaPony »

I have found some time for further investigations on that issue.
I can provide additional information.

ImageMagick version 6.5.5-5 is unaffected by this change in behaviour (or bug, if this was unintended),
and works on my current system.
We can therefore assume that the issue was not caused by my system, but by changes in ImageMagick.

I have also discovered an appropriate entry in the changelog after 6.5.5-5:

2009-09-03 6.5.5-7 Cristy <quetzlzacatenango@image...>
# Support multi-page transparent Postscript and PDF.

It is very likely that this change has caused my problem.

I will use 6.5.5-5 as a workaround for now.

Any comment on wether this is a bug or an intended change in the CLI syntax
would be most appreciated.

Edit:
Eh... sorry for posting this at all.
Issue does not exist in version 6.5.8-1.
It seems it was a bug that was fixed in the meantime but not important enough to make it to the changelog...
at least I didn't find any entry after 6.5.5-7 that could be related to my problem.
Post Reply