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

Unicode terminology #36

Closed
xfq opened this issue Dec 10, 2022 · 2 comments · Fixed by #38
Closed

Unicode terminology #36

xfq opened this issue Dec 10, 2022 · 2 comments · Fixed by #38
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@xfq
Copy link
Member

xfq commented Dec 10, 2022

1.1 Stylistic Conventions
https://w3c.github.io/uievents-code/#style-conventions

Unicode character encodings are shown as: U+003d.

Unicode code point, rather than "Unicode character encodings", should be more accurate here. Moreover, i18n generally recommends using "A"–"F" (rather than "a"–"f") for the code point values.

@xfq xfq added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Dec 10, 2022
@annevk
Copy link
Member

annevk commented Dec 10, 2022

It should reference and use the style of https://infra.spec.whatwg.org/.

@aphillips
Copy link

Adding some clarification to this issue.

As @xfq notes, "Unicode character encodings" is incorrect in this context. A Unicode character encoding would be something like UTF-8, UTF-16, etc. You actually mean Unicode code point.

Guidelines on quoting characters can be found in our Best Practices doc here.

I endorse @annevk's comment also. Note that the specific location in Infra is here. I will update our guidance to include that location and for mutual consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants