pdf_text: add raw argument for page::raw_order_layout
#138
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
Member
|
This has landed on CRAN in pdftools 3.6.0 |
Contributor
Author
|
Wonderful, thanks for all of your great work, @jeroen |
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.
This PR adds argument
rawtopdf_text()(andpoppler_pdf_text()) to allow selectingpage::raw_order_layoutinstead ofpage::physical_layout.I have several workflows that rely on parsing legacy PDF documents using
pdftotextcommand line tool-rawflag and then reading the output into R. I currently can't usepdftools::pdf_text()for these use cases because the pages have a complex multi-column format that is much easier to handle in the stream order raw layout rather than the physical layout.I love the pdftools package and use it frequently. Thanks for your consideration!