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 ... The other is lack of language/direction metadata.

The note after bullet point 18 at https://www.w3.org/TR/payment-request/#show-method is a step in the right direction (thank you), but it munges these two things together in a way that is unclear.  Here is a proposal for 2 separate notes, that describe the 2 issues.  Since you appear to be in a hurry, i am posting some suggested text now, before the i18n WG has a chance to review it, but i will ask the group to follow up after our telecon later this afternoon.

**Note: Metadata for international text display**
The API does not currently provide a way for developers to declare the language and base direction for any item of text in the payment sheet that is presented to end users.  Instead, the API relies on information inherited from the document. The working group is considering how to add this metadata to the next version of this API.  In the meantime, issues may arise when using this API to display text in various languages. 

**Note: Localization of the payments user interface**
The API does not currently provide a mechanism for developers to localize information presented to end users. The working group is considering support for requesting a specific localization of the user interface and of individual PaymentItems and user-facing error messages in a future version of this API.



-- 
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-931238787