Re: [iText-questions] Uncompressed Image Data Problems

2014-02-25 Thread FDnC Red
Thank you Michael.  iTextSharp is a great community supporting each other.   Love it! On Monday, February 24, 2014 4:01 AM, Michael Demey wrote: Hi Darren, I added a fix based on your comment to the repository. Thanks for the heads up! It's in revision 6289. Kind regards, Michaël. FDnC

Re: [iText-questions] Uncompressed Image Data Problems

2014-02-24 Thread Michael Demey
Hi Darren, I added a fix based on your comment to the repository. Thanks for the heads up! It's in revision 6289. Kind regards, Michaël. FDnC Red schreef op 17/02/2014 21:10: > Sorry if this is a duplicate. > > I have noticed that iTextSharp does not like ImageMasks that have > uncompressed

Re: [iText-questions] Uncompressed Image Data Problems

2014-02-21 Thread iText Info
iText Info schreef op 21/02/2014 15:53: > FDnC Red schreef op 21/02/2014 15:19: >> The errors start, when splitting, on page 23. > > Object 344 is a stream dictionary with a negative length. > Have you ever seen a byte array of size -1? ;-) O wait, the size isn't -1, it's perceived as -1. The pro

Re: [iText-questions] Uncompressed Image Data Problems

2014-02-21 Thread iText Info
FDnC Red schreef op 21/02/2014 15:19: > The errors start, when splitting, on page 23. Object 344 is a stream dictionary with a negative length. Have you ever seen a byte array of size -1? ;-) -- Managing the Performance o

Re: [iText-questions] Uncompressed Image Data Problems

2014-02-21 Thread FDnC Red
Below is a dropbox link.  The PDF is 66MB.  The errors start, when splitting, on page 23. https://www.dropbox.com/s/9sio97bxmt34flo/TCSD_Bid-Docs_DRAWINGS_2014-01-21.pdf Thanks, Darr On Tuesday, February 18, 2014 12:58 AM, iText mailing list wrote: On 2/17/2014 9:10 PM, FDnC Red wrote: > I'

Re: [iText-questions] Uncompressed Image Data Problems

2014-02-17 Thread iText mailing list
On 2/17/2014 9:10 PM, FDnC Red wrote: > I'd like to submit this to the iTextSharp team but I'm not sure who that is. You've posted your bug report to the right address, but it would help us if you could share a PDF that demonstrates the problem. ---