-
-
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
parse XSLT::Stylesheet using the libxslt-preferred options #1940
Comments
@menafkasap Thanks for reporting this issue, and apologies for my slow reply. I've tracked this down to the parse options used for the XSL file. I think what we should be doing here is using these same options for the XSL files within Nokogiri (e.g., in the |
PR submitted at #2221. Will land in v1.12.x. |
…t-using-preferred-options parse XSLT stylesheets using libxslt-preferred options --- **What problem is this PR intended to solve?** See #1940 where some XSL transformations ended up producing slightly different results from `xsltproc` **Have you included adequate test coverage?** Yes! **Does this change affect the behavior of either the C or the Java implementations?** This behavior appears to be libxslt-specific, and so the test only runs for CRuby; though the document ends up being parsed with the new options on both implementations.
The content in CDATA isn't affected by
disable-output-escaping
Two files shared below don't produce the same output with xsltproc and nokogiri.
FILES
test.xsl
test.xml
test.rb
OUTPUTS
xsltproc test.xsl test.xml
./test.rb test.xsl test.xml
The text was updated successfully, but these errors were encountered: