Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAllow non-HTML-encoded entities #404
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
bterlson
Feb 24, 2016
Member
Spec.html should be utf-8 encoded and html entities should only be used when needed. Eg. a < b should be fine, although I could be wrong about that. I plan on doing this work along with the big Ecmarkdown 3.0 conversion post-snapshot.
|
Spec.html should be utf-8 encoded and html entities should only be used when needed. Eg. a < b should be fine, although I could be wrong about that. I plan on doing this work along with the big Ecmarkdown 3.0 conversion post-snapshot. |
bterlson
added
the
editorial change
label
Feb 24, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ljharb
Feb 24, 2016
Member
awesome - we might want to set up a travis task to specifically lint for all the things we don't want included in spec.html - like html entities, or internal slots with non-uppercase code points, etc?
|
awesome - we might want to set up a travis task to specifically lint for all the things we don't want included in spec.html - like html entities, or internal slots with non-uppercase code points, etc? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Sure, I would love for npm test to actually do something useful ;) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
musgravejw
Apr 19, 2018
Contributor
Trying to follow up on this thread, would this issue require tests and/or a feature in ecmarkdown?
|
Trying to follow up on this thread, would this issue require tests and/or a feature in ecmarkdown? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Sure, but ecmarkup input isn’t valid html already :-) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mathiasbynens
Apr 19, 2018
Member
Right. I was pointing out that the case for which ecmarkup doesn’t have to do anything special is a > b rather than a < b. (re: @bterlson’s comment)
|
Right. I was pointing out that the case for which ecmarkup doesn’t have to do anything special is |
ljharb commentedFeb 23, 2016
Things like
<would be much nicer to work with as<inspec.html- is this something ecmarkup/ecmarkdown could handle for us?