Fix snippets for XQuery 3.1 #420
Merged
Conversation
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
|
@wolfgangmm I'm curious to know: Is the snippets.xml used to generate the source of xquery.snippets? In testing this PR, my edits - which were only to xquery.snippets - had the desired effect in eXide. But I just stumbled upon snippets.xml and realized that perhaps I should be editing that and somehow generating the xquery.snippets file from it. I'm happy to adjust the PR, but I would appreciate any guidance on how to generate the xquery.snippets file. I wasn't able to find anything in source about this. Alternatively, we could delete the snippets.xml file. Thanks! |
line-o
approved these changes
Feb 21, 2022
|
@line-o Thank you! |
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 snippet with the XQuery version declaration contained a syntax error.
The snippet with the HTML5 serialization is updated to conform to the XSLT and XQuery Serialization 3.1 spec, at https://www.w3.org/TR/xslt-xquery-serialization-31/#HTML_VERSION. While eXist is forgiving about
output:method="html5", this formulation will throw an error in Saxon and BaseX.