w3c / i18n-request

Horizontal review requests are made via issues in this repo, and tracked by our radar.
https://github.com/orgs/w3c/projects/91/views/1
1 stars 7 forks source link

Secure Payment Confirmation 2022-08-12 > 2022-09-16 #190

Closed ianbjacobs closed 1 year ago

ianbjacobs commented 2 years ago

Name of your specification

Secure Payment Confirmation

URL of your specification

https://www.w3.org/TR/2022/WD-secure-payment-confirmation-20220812/

When does the review need to be finished?

2022-09-16

What has changed since any previous review?

Diff since around the time of the FPWD review: https://github.com/w3c/secure-payment-confirmation/compare/8c18586..7204dc0d#diff-6f5a1d8263b0b0c42e2716ba5750e3652e359532647ac934c1c70086ae3cedda

Please point to the results of your own self-review

https://github.com/w3c/secure-payment-confirmation/issues/202

Where and how should the i18n WG raise issues?

https://github.com/w3c/secure-payment-confirmation/issues

Pointer to any explainer for the spec

https://github.com/w3c/secure-payment-confirmation/blob/main/explainer.md

Other comments

There is one remaining i18n issue about SPC (https://github.com/w3c/secure-payment-confirmation/issues/93) relating to display in browser UX of two strings. See our related pull request that we hope will close that issue. https://github.com/w3c/secure-payment-confirmation/pull/192