Skip to content
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

Non-ASCII characters are inconsistently represented #634

Closed
gibson042 opened this issue Dec 28, 2021 · 2 comments
Closed

Non-ASCII characters are inconsistently represented #634

gibson042 opened this issue Dec 28, 2021 · 2 comments
Labels
c: spec Component: spec editorial issues s: help wanted Status: help wanted; needs proposal champion Small Smaller change solvable in a Pull Request
Milestone

Comments

@gibson042
Copy link
Contributor

cf. #621 (comment) :

ECMA-262 prefers HTML character entities and ECMA-402 should follow suit. But we'll probably just update everything at once.

$ egrep --no-filename -ro \
  '[^][\n !"#$%&'\''()*+,./0-9:;<=>?@A-Z\\^_`a-z{|}~-]|&[[:alnum:]]*;' spec/ | \
  sort | uniq -c
     10 ×
     11 ≠
      3 ≤
      3 ≥
      9 §
     23 –
     16 𝔽
      5 &ge;
     84 &gt;
      3 &infin;
     79 &laquo;
      2 &ldquo;
      1 &le;
     87 &lt;
      1 &mdash;
      1 &ne;
     79 &raquo;
      2 &rdquo;
      1 &reg;
@ryzokuken ryzokuken added the c: spec Component: spec editorial issues label Dec 29, 2021
@sffc sffc added s: help wanted Status: help wanted; needs proposal champion Small Smaller change solvable in a Pull Request labels Dec 15, 2023
@sffc sffc added this to the ES 2024 milestone Dec 15, 2023
@ben-allen
Copy link
Contributor

In the time between when this issue was initially posted and now ECMA-262 has replaced HTML character entities (see: tc39/ecma262#2901) with the Unicode characters they represent. I've put up #907, which makes character representation in ECMA-402 consistent by using Unicode characters rather than HTML entities — the representation that 262 uses now, which is the opposite of the representation they standardized on back in 2021.

@ben-allen
Copy link
Contributor

Closed by #907

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: spec Component: spec editorial issues s: help wanted Status: help wanted; needs proposal champion Small Smaller change solvable in a Pull Request
Projects
None yet
Development

No branches or pull requests

4 participants