RFC 3282 (rfc3282) - Page 3 of 8

Content Language Headers

RFC 3282                Content Language Headers                May 2002


2.1 Examples of Content-language values

   Voice recording from Liverpool downtown

      Content-type: audio/basic
      Content-Language: en-scouse

   Document in Mingo, an American Indian language which does not have an
   ISO 639 code:

      Content-type: text/plain
      Content-Language: i-mingo

   A English-French dictionary

      Content-type: application/dictionary
      Content-Language: en, fr (This is a dictionary)

   An official European Commission document (in a few of its official
   languages):

      Content-type: multipart/alternative
      Content-Language: da, de, el, en, fr, it

   An excerpt from Star Trek

      Content-type: video/mpeg
      Content-Language: i-klingon

3. The Accept-Language header

   The "Accept-Language" header is intended for use in cases where a
   user or a process desires to identify the preferred language(s) when
   RFC 822-like headers, such as MIME body parts or Web documents, are
   used.

   The RFC 822 EBNF of the Accept-Language header is:

      Accept-Language = "Accept-Language" ":"
                             1#( language-range [ ";" "q" "=" qvalue ] )

   A slightly more restrictive RFC 2234 ABNF definition is:

      Accept-Language = "Accept-Language:" [CFWS] language-q
                        *( "," [CFWS] language-q )
      language-q = language-range [";" [CFWS] "q=" qvalue ] [CFWS]
      qvalue         = ( "0" [ "." 0*3DIGIT ] )
                     / ( "1" [ "." 0*3("0") ] )



Alvestrand                  Standards Track