Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#214 closed editorial (wontfix)

Content-Language definition

Reported by: mnot@… Owned by:
Priority: normal Milestone: unassigned
Component: p3-payload Severity: Active WG Document
Keywords: Cc: Norbert.Lindenberg@…


2616 defines Content-Language as:

The "Content-Language" entity-header field describes the natural language(s) of the intended audience for the entity.

Some people have interpreted the "of the intended audience" as meaning that this header indicates the language of the user, not the language of the content. As a result (for better or worse), current practice in the i18n community is to ignore this header (although there are other reasons, e.g., the lack of accuracy in the event of multiple languages being present).

Proposal: remove "the intended audience for"

See also:

(raised by Norbert Lindenberg)

Change History (4)

comment:1 Changed 12 years ago by julian.reschke@…

I think it says what it says on purpose. Do we really want to change that?

comment:2 Changed 12 years ago by mnot@…

  • Cc Norbert.Lindenberg@… added

Perhaps we can adjust the text to make it more clear, without changing the meaning. Norbert, any further thoughts?

See also:

comment:3 Changed 12 years ago by fielding@…

  • Resolution set to wontfix
  • Status changed from new to closed

The Content-Language does define the intended audience for the page, as is detailed in the examples within that section. Its purpose corresponds to that of Accept-Language.

comment:4 Changed 12 years ago by addison@…

The W3C I18N Working Group supports closing this bug for the reason given by Roy Fielding. The resolution is recorded here:

Norbert requested that I update the bug on his behalf.

Note: See TracTickets for help on using tickets.