Support custom element and newline separators in LocationTextExtractionStrategy #41
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Hi @schallb , Would you mind signing the Contributor License Agreement? |
Author
|
Hello,
please find signed CLA attached to finish the PR
BR
Gesendet: Freitag, 6. Februar 2026 um 10:35
Von: "Vitali Prudnikovich" ***@***.***>
An: itext/itext-dotnet ***@***.***>
CC: schallb ***@***.***>,Mention ***@***.***>
Betreff: Re: [itext/itext-dotnet] Support custom element and newline separators in LocationTextExtractionStrategy (PR #41)
vitali-pr left a comment (itext/itext-dotnet#41)
Hi @schallb ,Thank you for your contribution!
Would you mind signing the Contributor License Agreement?The details are available at https://itextpdf.com/en/how-buy/legal/itext-contributor-license-agreementWe need it in order to be able to merge your PR.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Based on existing LocationTextExtractionStrategy i needed more possibilities to distinguish between a "planned" space in text and the separator that was inserted when a new junk is found.
Same applies to the line feed.
Therefore i extended the LocationTextExtractionStrategy to use my own separators like pipes or other special characters.