chore: Change PDF text extraction logics #10420
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR intended to reduce diffs when running snapshot tests.
What's changed in this PR
1. Use
ContentOrderTextExtractor.GetTextinstead ofTextpropertyTextproperty don't returns new line chars.And it cause snapshot diffs between the lines.
By using
ContentOrderTextExtractor.GetTextAPI.It can gets human readable text content.
2. Normalize ligature chars
When getting text from PDF file.
Some chars are concatenated as ligature chars.
So manually replacing these chars.
It's normally replaced by
string.Normalizemethod. But when usingGlobalization Invariant Mode. it's not works as expected.