fix: replace \u0002, \u0003 in common text #521
Merged
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.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
5.pdf
Motivation
some digital pdf will produce \u002, \u003 in markdown result. This cause by pymupdf , wen just replace these special chars.
\u0000 (NUL): Null character
\u0001 (SOH): Start of Header
\u0002 (STX): Start of Text
\u0003 (ETX): End of Text
\u0004 (EOT): End of Transmission
\u0005 (ENQ): Enquiry
\u0006 (ACK): Acknowledge
\u0007 (BEL): Bell (causes an alert sound)
\u0008 (BS): Backspace
\u0009 (HT): Horizontal Tab
\u000A (LF): Line Feed (New Line)
\u000B (VT): Vertical Tab
\u000C (FF): Form Feed
\u000D (CR): Carriage Return
\u000E (SO): Shift Out
\u000F (SI): Shift In
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:
After PR:
ed and all committers have signed the CLA in this PR.