[graphicsmagick 0005153]: gm convert: No decode delegate for postscript

Mantis Bug Tracker via bug-notifications bug-notifications at lists.opencsw.org
Tue Mar 4 10:07:37 CET 2014

A NOTE has been added to this issue. 
Reported By:                wcohrs
Assigned To:                
Project:                    graphicsmagick
Issue ID:                   5153
Category:                   packaging
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Date Submitted:             2014-02-26 08:17 CET
Last Modified:              2014-03-04 10:07 CET
Summary:                    gm convert: No decode delegate for postscript
SunOS 5.10 Generic_150401-07 i86pc i386 i86pc

gm convert test.ps test.jpg
gm convert: No decode delegate for this image format (test.ps).

GraphicsMagick 1.3.18 2013-03-10 Q16 http://www.GraphicsMagick.org/

pkginfo | grep CSW | grep ghost
application CSWghostscript                   ghostscript - PostScript and
PDF interpreter
application CSWghostscript-fonts             ghostscript_fonts - Fonts and
AFMs for use with GhostScript
application CSWgs                            ghostscript_stub -
Transitional package. Content moved to CSWghostscript
application CSWgsfonts                       gsfonts_stub - Transitional
package. Content moved to CSWghostscript-fonts

the old version work

GraphicsMagick 1.3.12 2010-03-08 Q8 http://www.GraphicsMagick.org/

 (0010746) laurent (manager) - 2014-03-04 10:07
After some testing, it seems it's an expected behaviour, though it's not
The conversion of the transparent PNG rasterized from the PS to a JPG needs
parameters. Since the background in your PS is transparent, what you see is
the antialias of black letters over nothingness, ie, black. You need to
force a white background.

Like this, the output looks good:

convert -background white -flatten input.ps input.jpg

So you'd better force a white background to make it explicit, but of
course, I'd still advise to stick with PNG output.

So in summary:
  - there's definitely an issue with GraphicksMagic, and it appears to be
  - at this point, I don't have time to investigate it further
  - ImageMagick works and is an acceptable workaround.

More information about the bug-notifications mailing list