expose PdfString's start and end bytes positions in Stream #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will make possible the implementation of document signature, because to do so we need to exclude this specific byte range from the hash digest.
There is no other way to properly know that byte range without doing lots of changes as it has been done in empira/PDFsharp-1.5#11
Exposing this range will be enough to allow the development of a PdfSharp extension that support document signing (I'll do it).
If you're ready to consider it though, I can also do a pull request to directly embed this feature into the official PdfSharp repo.
If you do not merge this pull request, and neither consider consider accepting a pull request for a signature feature, I'll create a fork anyway.
Please let me know your thougts about this topic.