- From: Addison Phillips <notifications@github.com>
- Date: Tue, 20 Apr 2021 09:27:56 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 20 April 2021 16:28:08 UTC
I'm nervous about saying this addresses #650 and #952 because it is "merely" a recommendation that the language of the native interface match that of the document's node. I think this could be improved by being slightly more explicit. I18N has recommendations (and definitions) in our document [LTLI](https://www.w3.org/TR/ltli/#i18n-terminology), particularly around [here](https://www.w3.org/TR/ltli/#ltli-format-like-doc-language). Perhaps the text would be sufficiently stronger if worded something like this: > The user interface SHOULD be presented using the language and locale-based formatting that matches the |document|'s [=document element|document element's=] [=Node/language=], if any, or an appropriate fallback locale if that is not available. Note that I didn't define what "an appropriate fallback locale" would be, leaving that up to the implementation, including allowing the user agent to fall back to its own localization/runtime locale. I am "okay" with the text as is, but my disquiet is that it can be easily overlooked. Thoughts? -- 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/pull/944#issuecomment-823419388
Received on Tuesday, 20 April 2021 16:28:08 UTC