[Bug 8088] New: Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR">

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8088

           Summary: Change back the meaning of <meta http-equiv="Content-
                    Language" content="FOO, BAR">
           Product: HTML WG
           Version: unspecified
          Platform: All
               URL: http://www.whatwg.org/specs/web-apps/current-
                    work/multipage/semantics.html#attr-meta-http-equiv-
                    content-language
        OS/Version: All
            Status: NEW
          Keywords: disputedSpec
          Severity: major
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: xn--mlform-iua@xn--mlform-iua.no
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


http://www.w3.org/mid/op.u2gd6bq7idj3kv@simon-pieterss-macbook.local

According to the draft,  <meta http-equiv="Content-Language" content="en" >
"sets the document-wide default language".  As a consequence (?), the draft
permits only one language tag in the content attribute.

This represents a deviation from how it otherwise is used and specified - e.g.
in HTML 4.

The draft must say that it defines the languages of the intended audiences, and
that it may be used in content negotiation and in search engines etc. And it
must permit several languages to be specified.

If the spec wants to express a way to decide the "document-wide default
language", then one could define another META element variant for that purpose.
Or one could define that the first listed language in the list of languages
inside "content", represents the documument-wide lanuage.  Thus, in in this
example, the document-wide language is "en": <meta
http-equiv="Content-Language" content="en,fr,sp" >

References: http://www.w3.org/International/tutorials/language-decl/


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 27 October 2009 17:32:30 UTC