[i18n-activity] Missing available language/locales feature? (#1468)

aphillips has just created a new issue for https://github.com/w3c/i18n-activity:

== Missing available language/locales feature? ==
Human Readable Metadata

> Another possibility to set the default language is through a language negotiation mechanism, such as the Accept-Language header field of HTTP. In cases where the default language has been negotiated, an @language member MUST be present to indicate the result of the negotiation and the corresponding default language of the returned content. When the default language has been negotiated successfully, TD documents SHOULD include the appropriate matching values for the members title and description in preference to MultiLanguage objects in titles and descriptions members. Note however that Things MAY choose to not support such dynamically-generated TDs nor to support language negotiation (e.g., because of resource constraints). 

This section discusses the "default language". The above quote is only an example of some of the discussion. 

There is no feature that allows a Thing to indicate what languages are available for language-negotiation or what locales are available. Having a list of available languages or available locales (and these are not necessarily the same thing) would allow the user-agent calling the Thing's interfaces to provide an appropriate `Accept-Language` header or otherwise tailor the request so that the end-user's experience most closely matches their language and locale preferences.

While a multilanguage map is somewhat indicative of available languages, it is often the case that the localization depends on language fallback to avoid bloating the data. In other words, instead of providing separate translations for various (for example French) locales like `fr-FR`, `fr-BE`, `fr-CA`, `fr-CH`, etc., there is only a language value for `fr` (French) provided. However, specifying a fully qualified locale gives a better overall experience, since regional locale variations affect the formatting of numbers, dates, etc.


This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html

1. Create the review comment you want to propose by replacing the prompts above these instructions, but **LEAVE ALL THE INSTRUCTIONS INTACT** Then ask the i18n WG to review your comment.

2. Set a label to identify the spec: this starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staff contact to help.

3. After discussion with the i18n WG, raise an issue in the repository of the WG that owns the spec. Use the text above these instructions as the starting point for that comment, but add any suggestions that arose from the i18n WG. In the other WG's repo, add an 'i18n-needs-resolution' label to the new issue. If you think any of the participants in layout requirements task force groups would be interested in following the discussion, add also the appropriate i18n-\*lreq label(s).

4. Replace the text 'url_for_the_issue_raised' below with a link to the issue you raised in the other WG's repository. Do NOT remove the initial '§ '. Do NOT use []() notation - just paste the URL.

5. Remove the 'pending' label, and add a 'needs-resolution' tag to this tracker issue. If you added an \*lreq label, add the label 'spec-type-issue' and a label to indicate the relevant typographic feature(s), eg. 'i:line_breaking'. The latter represent categories related to the Language Enablement Index, and all start with i:.

6. Edit this issue to **REMOVE ALL THE INSTRUCTIONS**, ie. the two lines that are '---' and all the text between.

End of instructions.

**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:**

§ url_for_the_issue_raised

Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1468 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 10 February 2022 17:45:11 UTC