-
-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: overhaul SAX::Parser encoding handling #3288
Merged
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
"it's" means "it is", "its" means "belonging to it"
We'll use this in an upcoming commit to simplify the sax parsers
and polyfill xmlSwitchEncodingName. We'll need this functionality in the next commit.
Previously, encoding overrides were not implemented for XML::SAX::Parser#parse_memory (as reported in #918) and XML::SAX::Parser#parse_file. However, this commit goes further and significantly simplifies and unifies the two SAX::ParserContext implementations and the two SAX::Parser implementations. This commit also allows Encoding objects and encoding names to be passed into the SAX::ParserContext methods, and the XML memory and file methods now accept and properly use passed encodings. Finally, this commit also backfills a lot of test coverage for the XML and the HTML4 sax parser encoding. Closes #918
This was referenced Jul 7, 2024
flavorjones
force-pushed
the
918-sax-parser-encoding
branch
from
July 7, 2024 20:39
2e99210
to
f67b294
Compare
bihorco36
added a commit
to puzzle/prawn-markup
that referenced
this pull request
Dec 16, 2024
Due to changes in nokogiri 17, the SAX parser now needs a default encoding: sparklemotion/nokogiri#3288
bihorco36
added a commit
to puzzle/prawn-markup
that referenced
this pull request
Dec 16, 2024
Due to changes in nokogiri 17, the SAX parser now needs a default encoding: sparklemotion/nokogiri#3288
bihorco36
added a commit
to puzzle/prawn-markup
that referenced
this pull request
Dec 17, 2024
Due to changes in nokogiri 17, the SAX parser now needs a default encoding: sparklemotion/nokogiri#3288
bihorco36
added a commit
to puzzle/prawn-markup
that referenced
this pull request
Dec 17, 2024
Due to changes in nokogiri 17, the SAX parser now needs a default encoding: sparklemotion/nokogiri#3288
bihorco36
added a commit
to puzzle/prawn-markup
that referenced
this pull request
Dec 17, 2024
Due to changes in nokogiri 17, the SAX parser now needs a default encoding: sparklemotion/nokogiri#3288
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.
What problem is this PR intended to solve?
Previously, encoding overrides were not implemented for XML::SAX::Parser#parse_memory (as reported in #918) and XML::SAX::Parser#parse_file.
However, this commit goes further and significantly simplifies and unifies the two SAX::ParserContext implementations and the two SAX::Parser implementations.
This commit also allows Encoding objects and encoding names to be passed into the SAX::ParserContext methods, and the XML memory and file methods now accept and properly use passed encodings.
Finally, this commit also backfills a lot of test coverage for the XML and the HTML4 sax parser encoding.
Closes #918
Have you included adequate test coverage?
Yes.
Does this change affect the behavior of either the C or the Java implementations?
Yes, but they are more consistent with each other.