-
Notifications
You must be signed in to change notification settings - Fork 253
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
Edge case: does not decode example string on w3 spec #50
Comments
Good catch! Thanks for the excellent bug report. |
Got bitten by this too, but can't find what would be the way to fix it in he... |
Surely this has been fixed by now... |
128th character in ASCII table which looks like a small square when printed with this code |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was testing encode/decode via https://mothereff.in/html-entities while cross-referencing the spec, and I noticed that
he
is not able to decode certain named references correctly. On the w3 spec page, it lists this example string,I'm ¬it; I tell you
, which should be parsed intoI'm ¬it; I tell you
with a parse error.he
returns the string un-parsed. It appears thathe
is not able to parse legacy named references if there are one or more alphanumeric characters after the legacy named reference followed by a semicolon;
character.he
parses correctly if the tail of alphanumeric characters ends with a character other than semicolon.The text was updated successfully, but these errors were encountered: