Open
Conversation
Author
|
Added a new commit to parse the cs tags when they occur |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add a dictionary mapping to handle
ISO-8859-1encoding for the RTF files.Our company deals in parsing laws, statutes and regulations for various countries and all the US states.
While parsing the RTF file on the Arizona code website. We came across a file that could not be parsed by the library due to an unknown encoding mapping.
We have added the missing encoding from our end and tested the code. The link for the file is here. https://apps.azsos.gov/public_services/Title_12/12-07.rtf