ISSUE-129: Why is content language processing not equivalent to HTTP Content-Language?
Why is content language processing not equivalent to HTTP Content-Language?
- State:
- CLOSED
- Product:
- html
- Raised by:
- Addison Phillips
- Opened on:
- 2011-07-23
- Description:
- 4.2.5.3 Pragma directives
http://www.w3.org/TR/html5/semantics.html#pragma-directives
The content language processing is not equivalent to HTTP Content-Language (and is noted as such). Why? - Related Actions Items:
- No related actions
- Related emails:
- [html] Issue: why is "content language" pragma processing not equivalent to HTTP Content-Language? marked as i18n (from sysbot+gh@w3.org on 2016-05-03)
- Review of tracker issues for best practices (Part IV) (from addison@lab126.com on 2015-03-31)
- Re: [I18N-ACTION-150] Review of HTML open issues (from ishida@w3.org on 2014-02-21)
- [I18N-ACTION-150] Review of HTML open issues (from addison@lab126.com on 2014-02-18)
- Re: HTML5 Comment disposition (from w3@norbertlindenberg.com on 2012-03-20)
- I18N-ISSUE-129: Why is ontent language processing not equivalent to HTTP Content-Language? [HTML5-prep] (from sysbot+tracker@w3.org on 2011-07-23)
Related notes:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22719
Addison Phillips, 18 Jul 2013, 01:28:19Display change log