- From: Marcos Cáceres <notifications@github.com>
- Date: Mon, 29 Jan 2018 06:08:19 +0000 (UTC)
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 29 January 2018 06:09:18 UTC
Speaking out loud here: the merchant will have the `Accept-Language` header by default, which in turn will allow them to set the language of the body element (this is generally applicable i18n guidance for any website). Additionally, setting the language through a user-configurable option i in the site itself is usually a better solution... alternatively, some sites also use Geo IP solutions, which can be annoying, but mostly "good enough". As @domenic suggests, it feels like the right thing to do here is for us just recommend the payment sheet use the document language. Let's see how we go with that for, say, 1-2 years. If we find that it's insufficient, then let's add the API part... we have the text ready to go when we need it 😇 I'll make the appropriate changes to #656. -- 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/650#issuecomment-361148971
Received on Monday, 29 January 2018 06:09:18 UTC