Fix PST RTF bodies, controller error handling #252
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
* Replace outdated option to print without header/footer
…issue with repeating errors
Better handles RTF bodies for PST files
Update pdf-chrome derivative
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.
Type of Contribution
What does this implement/fix? Explain your changes.
Should substantially improve reading RTF bodies from PST files. Also addresses #250 and improves Chrome docs for MacOS users thanks to @jtruitt1.
Link to issue?
#250
Pull Request Checklist
Please check if your PR fulfills the following requirements:
How has this been tested?
Operating System: Win10
Python Version: 3.9
Licensing