On 21/08/2012 0:51, Alex Betin wrote: > I know that you usually attribute it to broken TIFF files, but should > not such exception be handled by framework?
It's always a tradeoff: TIFF producers should produce correct TIFF files. If TIFF consumers are tolerant towards incorrect TIFF files, TIFF producers can abuse that goodwill by not caring about producing correct TIFF files. By not tolerating incorrect TIFF files can improve the ecosystem and force TIFF producers to comply ;-) On the other hand: we care about our customers, and we want to help them as good as we can. I've tested the files and I can reproduce the problem. I don't intend to have a closer look at it though, at least not until a support ticket was issued for it, or until I have absolutely no other work to do ;-) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
