"Marc F. Clemente" <[email protected]> wrote: > And after nearly four years the bug is still open. > > . . .
I'm very sorry that this bug is still open after four years. However, you may notice that the bug is marked as forward to upstream, and the bug can be found upstream at http://bugzilla.maptools.org/show_bug.cgi?id=2078. The problem is that there is very light work on libtiff upstream right now as no one is focused on it as a primary focus. For the most part, bugs in utilities like this only get fixed if someone supplies a patch, even though this bug is caused by something inside the library. I am not personally in a position to study this enough to generate a patch, particularly since there are other alternatives available. My recommendation would be to use a different tool to generate PDF files from tiff files. A disproportionate number of the debian bugs reported against the tiff software in the years since I've been maintaining it have been with tiff2pdf. I don't think that particular tool was well written. It seems to make a lot of incorrect assumptions. Instead, I would recommend that you use a different tool for creating PDF files from tiff files. Imagemagick and graphicsmagick can both convert tiff to PDF and write to stdout. You can use "convert file.tiff PDF:-" or "gm convert file.tiff PDF:-" instead to do the conversion. I think this will generally give you better results. GraphicsMagick creates better PDF files than ImageMagick since it uses better compression on the image, so my recommendation if you want to create PDF files to stdout from tiff files is to use gm convert as in the example above. I hope this helps. I can continue leave this bug open if you want, though, realistically, it's not likely to get addressed. Perhaps someone will contribute a completely rewritten tiff2pdf someday that won't have this problem. -- Jay Berkenbilt <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
