- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Mar 2021 14:35:37 +0000
- To: public-i18n-archive@w3.org
aphillips has just created a new issue for https://github.com/w3c/i18n-activity: == payment-request lacking language negotiation mechanism == (throughout the spec, some examples follow) https://www.w3.org/TR/2020/CR-payment-request-20201203/#payererrors-dictionary https://www.w3.org/TR/2020/CR-payment-request-20201203/#paymentshippingoption-dictionary https://www.w3.org/TR/2020/CR-payment-request-20201203/#show-method Throughout the payment-request spec we note that natural language text values are returned. From our teleconference of 2021-03-25 we decided to group a number of pending issues into two buckets: * The need for language and direction metadata on natural language items (already tracked in payment-request 327) * The need for localizability of natural language fields (e.g. the ability to have more than one language present) * The need for a language negotiation mechanism so that the the API caller can receive natural language messages such as errors or labels in their preferred language/locale (if available) This issue tracks the last of these. **This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:** ยง link_to_issue_raised Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1373 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 March 2021 14:36:13 UTC