Fix issues with unicode ANSI skipping #31
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
The current implementation of unicode ANSI replacement sequences is slightly wrong - according to https://www.biblioscape.com/rtf15_spec.htm * A scope delimiter (i.e. "{" or "}") should end the current skippable data * Control words or symbols should be considered a single skipped character (and in my testing with MS office, they're ignored) * Any binary data is also considered a single skipped character
ztravis
force-pushed
the
bugfix/unicode-skip
branch
from
6bfda82 to
b4f4a44
Compare
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.
The current implementation of unicode ANSI replacement sequences is slightly wrong - according to https://www.biblioscape.com/rtf15_spec.htm