Re: [w3c/payment-request] Localization and string metadata for descriptions (#948)

There are really two problems here. One is the lack of a language negotiation mechanism (which is what PR#956 seems to be about??), which we all agree it out of scope for v1. In your email about "Preparing to advance PR API 1.0 to Candidate Rec" you reviewed all of the open issues (thanks for that!) you called out:

```
* Add dir/lang member on dictionaries whose content is displayed in browser UI
  https://github.com/w3c/i18n-activity/issues/251


  We closed this with Pull request 956:
  https://github.com/w3c/payment-request/pull/956


  Cf. Addison’s comments, including:
  https://github.com/w3c/payment-request/pull/956#discussion_r634453183

```

(Notice that my response focuses on the localization mechanism)

The other is lack of language/direction metadata. All of those threads appear to be dangling, at least in github. It's possible that we discussed this via email somewhere that I haven't spotted yet. But my review this morning seems to suggest that a pull request might be waiting on our String-Meta doc to provide the necessary reference or that some other mechanism would be agreed. I thought at one point that Marcos had addressed with a pull request, but that seems to have been pulled back. The recent discovery of webAuthn's problematic encoding (see above) fell out of that too.

Probably this is too late to do anything about and possibly you're right we agreed to it, but it seems like we all overlooked that lack of a localization mechanism != lack of metadata fields? Hence today's comments...

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/948#issuecomment-916415023