Leonard,
I posted a sample of the XML we're seeing to the bottom of the original
msg here. It appears to be control code for the printer definitions.
Stack overflow usually indicates some looping condition - and that XML
has lots of child occurrences...
We're using the streaming reader methods; not from the filesystem. We
get a page at a time - that is how we know which page it's on when it
throws the exception. Also - that page contains the image created by
the Alchemy plug-in - and of course has the associated XML at that
point.
If I re-print the whole document using Adobe Reader 7 and CutePDF - then
CutePDF creates a new PDF without the XML in it - and we are able to
process that OK - that is why we are assuming the XML is the root cause
of the problem.
Thanks, DW
-----Original Message-----
I don't know about Image Alchemy, but
many Mac OS applications will write such metadata
into image files. I have not, however, seen that
go into the PDF itself - UNLESS it is inside the image data.
Can you provide a sample PDF demonstrating this?
>This causes iText to throw a ?stack overflow?
>exception when it hits that page in the PDF.
>
What do you mean "hits that page"? What specific API call in
iText?
LDR
------------------------------------------------------------------------
---
Leonard Rosenthol
<mailto:[EMAIL PROTECTED]>
Chief Technical Officer <http://www.pdfsages.com>
PDF Sages, Inc. 215-938-7080 (voice)
215-938-0880 (fax)
_______________________________________________
iText-questions mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/itext-questions
