Post any defects you find in the released or beta versions of the ImageMagick software here. Include the ImageMagick version, OS, and any command-line required to reproduce the problem. Got a patch for a bug? Post it here.
You syntax is not really correct for IM 6 (-monochrome should be after the pdf), but that should not really matter. I don't think -antialias is meaningful in this usage, I think it is only for drawing text. But it should not hurt to have it.
But in IM 6.7.7.6 beta on Mac OSX Tiger, I do not have any trouble with doing the following:
# create pdf
convert logo: logo.pdf
# process pdf to tiff using -monochrome
convert -density 300x300 -units pixelsperinch logo.pdf -monochrome logo2.tiff
The result is binary. Note that -monochrome will produce dither pattern.
Apparently 6.7.7-2 has a bug involving monochrome TIFF images, and the bug was solved in 6.7.7-4 (or at least that's what I understood -- I might be wrong). I am building from the MacPorts version (because I am not savvy enough to build manually) and unfortunately they don't have anything newer than 6.7.7-2. For now, I downgraded to 6.7.6-9, which works without problems.
Anyway, thank you for your comments about the switches.
fmw42 wrote:You syntax is not really correct for IM 6 (-monochrome should be after the pdf
Actually from my recent studies in preparation for IMv7 changes, I learned that in one case monochrome was being used as a setting, and not as a pure operator it should be. In PDF reading.
This I thought was silly and really should be removed as a setting, or replaced with the appropriate '-type' setting.
In any case Fred is right. Monocrome should be after the PDF, and is essentially a 'dither with black and white colors only'. In a quantization sense... a dithered 'threshold'.