Legacy ImageMagick Discussions Archive

The TIFF conversion worked fine for us with ImageMagick 6.2.6-8 the current release. The PNG coder is fixed in ImageMagick 6.2.7 Beta. Thanks for bringing this problem to our attention.

Post a URL to your original image, the image annotated with the tahoma.ttf font, and the image produced by Gimp. We will try to reproduce the problem and account for the differences in the font. ImageMagick and Gimp both use the Freetype rendering engine so it should produce identical results.

Post a URL to your TIFF image here. We need to reproduce the problem before we can offer any advice.

Variable inPixel can be NULL if your image is an odd height or width. Either check for this condition and bail or use num_row-1 and num_cols-1 in your loops.

The -background option is a setting not an operator. Try this instead:

• convert a.png -fill red -draw "color 0,0 reset" a.jpg

You found a bug in the PNG coder. The conversion seems to work fine for other formats such as MIFF, GIF, PBM, etc. We will apply a patch to ImageMagick 6.2.7 Beta. The only workaround we can think of is to compensate for the inversion with the -negate option.

A patch will be available tommorrow in ImageMagick 6.2.7-0 Beta. We restored the behavior such that the first image will always be the pre-combined layer.

In the future post to only one forum.

MagickToMime() is exported in the libMagick library. Not sure why but it looks like you build is missing -lMagick which would include the libMagick library and resolve the missing symbol.

Try adding -depth 8 to your command line to force 8 bits-per-pixel. You might also try upgrading to the latest release of ImageMagick 6.2.6-8.

Add -background none near the beginning of the command line or leave xc:none and add -composite near the end of the command line.

Remove xc:none from your command line.

Luckily very few people use the 32 bits-per-pixel version of ImageMagick. Fixed in ImageMagick 6.2.7 Beta. Thanks.

Try

• cd ImageMagick-6.2.6
  ./configure --disable-shared
  make clean
  make
  make -k -i install

Did you build ImageMagick from source or are you using the pre-compiled binaries? If the latter, it will always check the Windows registry since it was built with UseInstalledMagick defined. ImageMagick will look in the execution path of the program for any dll's to load only if UseInstalledMagick i...

We have a patch for the problem you posted. We'll try to get updated Windows binaries out in the next few weeks.