Am 20.04.2015 um 13:00 schrieb Thomas Chojecki:
Hi Tilman,
I tried yesterday to understand why there was the need for a
VisualSignatureParser and there is no one. I've ran several visual
signature tests today and it make no differents between the
VisualSignatureParser and the PDFParser. So this part can be replaced
refactored.
Did you want to fix this?
Yes, I will work on this tomorrow and ping you when done.
Best regards
Thomas
PS: In the other mail you said that there are some getItem() calls
instead of getDictionaryObject() calls. I think I didn't know it
better 6 years ago, so I've used getItem(). So this can be also fixed.
Also the twice call can be removed.
Ok, I will do this.
And yes the code is some kind of messy at some points and need to be
cleaned up. I planed some time ago to refactor the code but it would
make sense to refactor the COSWriter first. For signatures / real
incremental updates a List / Set based writer would be a better
solution. The recursive parser has to many restrictions so there is
some kind of hacking in the signature implementations that does not
make sense.
That one I won't do... COSWriter is one of the classes I haven't looked
at yet :-(
Tilman
Zitat von Tilman Hausherr <[email protected]>:
Hi Thomas,
Why is the VisualSignatureParser needed, i.e. why can't we just use
the COSParser (and maybe add a method setVisualSignature(File pdf))?
My question is related to the question "parseCOSStream defined twice"
by Andrea Vacondio. There are two calls of the sequential version;
the one in PDFStreamParser I will remove soon because streams don't
exist in content streams, the other one is in VisualSignatureParser.
Tilman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
