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

U+ notation incorrect #1641

Open
aphillips opened this issue Jul 9, 2021 · 0 comments
Open

U+ notation incorrect #1641

aphillips opened this issue Jul 9, 2021 · 0 comments
Assignees
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. @Risk Items that are at risk for L3 type:editorial
Milestone

Comments

@aphillips
Copy link

6.4.2. Language and Direction Encoding
https://www.w3.org/TR/webauthn-2/#sctn-strings-langdir

So the string “حبیب الرحمان” could have two different DOMString values, depending on whether the language was encoded or not. (Since the direction is unambigous a directionality marker is not needed in this example.)

  • Unadorned string: U+FEA2, U+FE92, U+FBFF, U+FE91, U+20, U+FE8E, U+FEDF, U+FEAE, U+FEA4, U+FEE3, U+FE8E, U+FEE7
  • With language “ar-SA” encoded: U+FEA2, U+FE92, U+FBFF, U+FE91, U+20, U+FE8E, U+FEDF, U+FEAE, U+FEA4, U+FEE3, U+FE8E, U+FEE7, U+E0001, U+E0061, U+E0072, U+E002D, U+E0053, U+E0041, U+E007F

The Unicode notation and code points used in the example are incorrect. The Arabic string should not use compatibility (presentational) code points. All code points should be represented by a minimum of 4 hex digits.

The correct notation should be:

U+062D U+0628 U+06CC U+0628 U+0020 U+0627 U+0644 U+0631 U+062D U+0645 U+0627 U+0646

And for the example:

U+062D U+0628 U+06CC U+0628 U+0020 U+0627 U+0644 U+0631 U+062D U+0645 U+0627 U+0646 U+E0001 U+E0061, U+E0072 U+E002D U+E0053 U+E0041 U+E007F
@aphillips aphillips added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Jul 9, 2021
@emlun emlun changed the title [Editorial] U+ notation incorrect U+ notation incorrect Jul 12, 2021
@equalsJeffH equalsJeffH added this to the L3-WD-01 milestone Jul 13, 2021
@nadalin nadalin added the @Risk Items that are at risk for L3 label Jun 27, 2023
@plehegar plehegar modified the milestones: L3-WD-01, L3-WD-02 Oct 4, 2023
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. @Risk Items that are at risk for L3 type:editorial
Projects
None yet
Development

No branches or pull requests

5 participants