Editorial: replaced ≥ ∞ « “ ≤ — ≠ &r… #907
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
|
Could I get a quick review of this one? It's been sitting for a minute. @gibson042 @ryzokuken |
ptomato
added a commit
to tc39/proposal-temporal
that referenced
this pull request
Aug 8, 2024
ben-allen
force-pushed
the
remove-html-entities
branch
from
1b5126b to
155e000
Compare
…aquo; ” × with their corresponding non-ascii characters
ben-allen
force-pushed
the
remove-html-entities
branch
from
d1e3dc0 to
d7e2853
Compare
|
@gibson042 quick review? Mostly I want to make sure that my interpretation of 262's standard for html entities is correct. |
ptomato
approved these changes
Aug 14, 2024
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.
#634 observed that ECMA-262 had standardized on using HTML character entities rather than non-ASCII characters such as ≤ and ≥. However, in the time since that issue was raised 262 re-standardized on directly using the Unicode characters rather than using HTML entities.
This PR replaces the relevant HTML character entities with the Unicode characters they represent.