You're right... makes we wonder if we violated some design rule. The
alternative would be some double code, which isn't good either.
Lets say we change this, then not only we'd have some double code, but
some existing code by our users might no longer work...
You can open an issue in JIRA and attach a patch / diff file there. But
it might be a difficult decision.
Tilman
Am 15.05.2018 um 15:00 schrieb Constantine Dokolas:
Hi all!
I'm currently implementing a library that intercepts content stream
operators from a document's pages in order to produce a filtered version
(as a different document). To this, I'm writing an extension to
PDFGraphicsStreamEngine (as suggested by the documentation) and using
processOperator() to do "my stuff".
Certain operators (MoveTextSetLeading, NextLine, ShowTextLine and
ShowTextLineAndSpace), in order to trigger the (multiple) corresponding
events, take the shortcut of calling processOperator() for "bogus"
operators that are in fact *not present* in the content stream.
I suggest the devs replace such calls with temporary OperatorProcessor
instantiations and process(...) calls on them. I'd be happy to contribute
the related changes, but I'm not sure how.
I'd like to voice my appreciation for this project. It has solved many
problems for me and I greatly appreciate the devs' effort.
Regards,
Constantine
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
