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.

Sign up for GitHub

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

Jump to bottom

Examples should include non-ASCII [editorial] #594

Closed
r12a opened this issue Sep 27, 2017 · 5 comments
Closed

Examples should include non-ASCII [editorial] #594

r12a opened this issue Sep 27, 2017 · 5 comments
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
Milestone
PropRec

Comments

@r12a
Copy link

r12a commented Sep 27, 2017

[This review was done against https://www.w3.org/TR/2016/WD-webauthn-20160531/#iface-account, and the comment was raised by Addison Phillips. The i18n WG agreed to forward as a WG comment.]

Section 3.3 contains several examples of user and organizational names (rpDisplayName, displayName, etc.). The examples should include some non-English or non-Latin example.
@r12a r12a added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Sep 27, 2017
@aphillips aphillips mentioned this issue Sep 27, 2017
Closed
@emlun
Copy link
Member

emlun commented Oct 3, 2017

It looks like §3.3 in WD1 (2016-05-31) corresponds to PublicKeyCredentialEntity and its subtypes in WD7 (2017-08-11).

@AngeloKai
Copy link
Contributor

Sounds good. We can do at PR time for completeness. Thank you for the review!

@equalsJeffH @nadalin @YubicoDemo for tracking.

@AngeloKai AngeloKai added this to the PR milestone Oct 25, 2017
@rlin1 rlin1 mentioned this issue Nov 9, 2017
Closed
@samuelweiler samuelweiler added the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label Jan 19, 2018
@samuelweiler
Copy link
Member

adding a completely inappropriate privacy-cons label for testing purposes. Nothing to see here; move along. (But please leave the label here for now.)

@equalsJeffH
Copy link
Contributor

fyi: we did add non-usascii chars to "name:" values in examples. can we close this?

@emlun emlun mentioned this issue Feb 28, 2018
Merged
@aphillips
Copy link

I'm satisfied with this result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
Projects
None yet
Milestone
PropRec
Development

No branches or pull requests
6 participants
@aphillips @equalsJeffH @emlun @r12a @AngeloKai @samuelweiler