[i18n-activity] HTTP Content-Language header for language declaration (#896)

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

== HTTP Content-Language header for language declaration ==
1.3. Languages and Typesetting
https://drafts.csswg.org/css-text-3/#content-language

> Note: Authors can tag content using the global lang attribute in HTML, the universal xml:lang attribute in XML, and the HTTP Content-Language header for content served over HTTP.

The i18n WG recommends always using document-internal declarations, even if the appropriate language is contained in the HTTP Content-Language header.  Obtaining the language from the HTTP header should only be a last resort fallback. See https://www.w3.org/International/questions/qa-http-and-lang (esp. https://www.w3.org/International/questions/qa-http-and-lang.en#http).

I think, therefore, the note should be reworded so that it doesn't imply that HTTP declarations are of equal validity to the lang attributes.  Really it should say something like: authors can use the lang or xml:lang attributes, and some browsers in some cases may be able to extract something useful from the HTTP information if those are lacking.  Personally, i'd be inclined to just drop the mention of the HTTP Content-Language.


---
Instructions: 

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

1. **CREATE A PROPOSED REVIEW COMMENT BY REPLACING THE PROMPTS ABOVE THIS PARAGRAPH, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** Then ask the i18n WG to review your comment.

2. After discussion with the i18n WG, raise this issue to the WG that owns the spec. Use the text above this para as the basis for that comment.

3. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue. Do NOT remove the initial '§ '.

4.  Edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. 



**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/896 using your GitHub account

Received on Wednesday, 29 April 2020 12:57:50 UTC