- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Apr 2019 19:38:44 +0000
- To: public-i18n-archive@w3.org
aphillips has just created a new issue for https://github.com/w3c/i18n-activity: == Clarify about language negotiation == 5.2.6 Multilanguage https://cdn.staticaly.com/gh/w3c/wot-thing-description/TD-TAG-review/index.html?env=dev#multilanguage > Note that in protocols such as HTTP that have an ability to negotiate content based on languages, those terms (e.g. description and title) intended for carrying texts in a default language SHOULD be used instead of MultiLanguage container when the texts are served as a result such negotiation. It's not clear to me what this text intends should happen. While HTTP provides `Accept-Language` and `Content-Language` headers to assist with language negotiation and indeed some systems do use these to perform language negotiation, there is no specific standard here. I think the intention is that _if_ a service or thing has successfully negotiated language with the requesting party, _then_ the `description` or `title` (or other natural language text bearing fields) should use that language/locale for the response. It's not clear to me that returning a `Multilanguage` would be an error, which is what this normative language suggests. Note this paragraph is marked "at risk". --- **WHEN CREATING A NEW ISSUE DO SO ABOVE THIS PARAGRAPH, REPLACING THE PROMPTS, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** When this issue is raised in the github/bugzilla/mail of the WG that owns the spec, use the text above this para as the basis for that comment. Then edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue, but leave the remaining text below this para unaltered. **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/680 using your GitHub account
Received on Thursday, 18 April 2019 19:38:49 UTC