Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix customTextRenderer not working on documents without marked content #1531

Merged
merged 2 commits into from
Jun 12, 2023

Conversation

MattL75
Copy link
Contributor

@MattL75 MattL75 commented Jun 9, 2023

Fixes #1530

@wojtekmaj I think this is a good approach for now. I don't think there can be a mix of marked and unmarked content (at least not any use cases that make sense). So one or the other should work. Added a test for this case as well. Feel free to reformat :)

I confirmed with the document in the ticket, the highlighting occurs in the test project.

@MattL75 MattL75 changed the title fix: solve custom text renderer with untagged docs fix: #1530 solve custom text renderer with untagged docs Jun 9, 2023
@MattL75 MattL75 marked this pull request as ready for review June 9, 2023 18:06
@MattL75
Copy link
Contributor Author

MattL75 commented Jun 9, 2023

#1530

@corystevens
Copy link

I can confirm that this fixes my issue.

@wojtekmaj wojtekmaj changed the title fix: #1530 solve custom text renderer with untagged docs Fix customTextRenderer not working on documents without marked content Jun 12, 2023
@wojtekmaj wojtekmaj merged commit 11027c1 into wojtekmaj:main Jun 12, 2023
@wojtekmaj
Copy link
Owner

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

customTextRenderer is not called with various valid PDFs
3 participants