Hello Kevin,
Yes, I considered using it. But when I did, I was already happy being
successful with a new instance for each page, which I think is not a
very costly operation in the context it is used in. I only think a hint
to the cumulative effects of processContent() in api doc and/or "the
b
Sure, I'd be happy to add a note to to the processContent() method. Did you
happen to note the reset() method?
--
View this message in context:
http://itext-general.2136553.n4.nabble.com/PdfContentStreamProcessor-and-changes-in-graphics-state-tp4403123p4405492.html
Sent from the iText - General
Hi Kevin,
thank you for your answer.
Perhaps it would be nice, if this could be mentioned at a promiment
place in the api docs and / or in the itext book. The examples I have
found tend to look as if ProcessContent() was something like a "per page
action" that begins with a tabula rasa at each
This is intentional and by design. PdfContentStreamParser is stateful -
create a new one for each page.
--
View this message in context:
http://itext-general.2136553.n4.nabble.com/PdfContentStreamProcessor-and-changes-in-graphics-state-tp4403123p4404506.html
Sent from the iText - General mailing
Hello,
I use PdfContentStreamProcessor and a listener to extract text from
certain rectangles on pdf pages, for instance a customer number always
appearing at the same position on the pages of a file.
I assumed I could use a single PdfContentStreamProcessor object and call
ProcessContent() wit
