- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Tue, 19 Mar 2002 22:03:20 +0000 (GMT)
- To: w3c-wai-ig@w3.org
> content negotiation. Content-Language in the HTTP Response identifies
> the actual language of the document returned.
Erm No!!
From RFC 2616:
The Content-Language entity-header field describes the natural
language(s) of the intended audience for the enclosed entity. Note
that this might not be equivalent to all the languages used within
the entity-body.
Content-Language = "Content-Language" ":" 1#language-tag
Note the 1# and the (s). Some more:
Language tags are defined in section 3.10. The primary purpose of
Content-Language is to allow a user to identify and differentiate
entities according to the user's own preferred language. Thus, if the
I.E. it is to help resource selection, not to control rendering.
body content is intended only for a Danish-literate audience, the
appropriate field is
Content-Language: da
...
Multiple languages MAY be listed for content that is intended for
multiple audiences. For example, a rendition of the "Treaty of
Waitangi," presented simultaneously in the original Maori and English
versions, would call for
Content-Language: mi, en
Received on Tuesday, 19 March 2002 17:03:24 UTC