E4X xml-literal allowed xml-characters #294
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
…s implemented - ascii charset only
…ython implementation
bitwiseman
added a commit
that referenced
this pull request
Jun 14, 2013
E4X xml-literal allowed xml-characters
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.
Hi :)
js-beautify failed beautifying code with xml literals with entity-names og attribute-names containing:
-,.or_(special characters, allowed in the xml-standard but missing in the xml-matching regexp in js-beautify (I overlooked them when I implemented it previously)).The pull request has tests and fixes for both the JavaScript and Python implementation of js-beautify,