Jay Berkenbilt <[email protected]> wrote: > 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.
I appreciate this bug being here and open as I just ran into this today. The open bug helped me understand the situation and confirmed I wasn't crazy. Interestingly this problem doesn't happen on libtiff 3.9.4. I hit the bug when migrating a service from a debian box running that version to one running libtiff 4.0.2. Since we have a working version to compare against, perhaps I'll get ambitious sometime and bisect the issue to figure out where it got introduced. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
