Re: [w3c/browser-payment-api] Add section on internationalization (#53)

Per the comments from @nickjshearer and @rsolomakhin in w3c/webpayments#84, I don't believe there are any requirements here for an API in an interactive user-agent.

All browser APIs that receive information to display from the web page rely on the web page to know what language they are showing to the user. The page decides what language to provide. Native UI is presented to the user in the language that they have chosen for their browser or OS; we typically don't let pages influence this.

So in `PaymentRequest`, the only information provided in a natural language is for display only (e.g., labels on displayItems/total). Processing of Accept-Language headers, etc. is outside the scope of the API.

I propose we close #53 until we find any I18N requirements that we need to add to the spec.

---
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/browser-payment-api/issues/53#issuecomment-215705679