- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Jul 2021 09:17:25 +0000
- To: public-i18n-archive@w3.org
r12a has just created a new issue for https://github.com/w3c/i18n-drafts: == [questions/qa-http-and-lang] BRIEF_TITLE_GOES_HERE == [source] (https://www.w3.org/International/questions/qa-http-and-lang) [en] In https://github.com/whatwg/html/issues/6907#issuecomment-888284213 @annevk said: > Some of the information in that document seems inaccurate: > - User agents must obey <meta http-equiv=content-language>, that's not a "can". > - The HTTP Content-Language response header is used to determine the language of a node, if other information is not available. I think the first point relates to: > HTML5 did, however, make a concession for backwards compatibility. If there is a meta element with http-equiv set to Content-Language in the markup, and if there is no language attribute on the html tag, and if the meta element has a value that is a single language tag, then a browser can (not must) use that information to guess at the default language of the text on the page. Please view or discuss this issue at https://github.com/w3c/i18n-drafts/issues/310 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 July 2021 09:17:27 UTC