1 - 2 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
language
Click on the red underlined text to get to the source
... URI,
as defined in section 3.2. Resources may be available in multiple
representations (e.g. multiple languages, data formats, size,
resolutions) or vary in other ways.
...
... Language Tags ...
...
A language tag identifies a natural language spoken, written, or
otherwise conveyed by human beings for communication of information
...
...
A language tag identifies a natural language spoken, written, or
otherwise conveyed by human beings for communication of information
to other human beings. Computer languages ...
... language spoken, written, or
otherwise conveyed by human beings for communication of information
to other human beings. Computer languages are explicitly excluded.
HTTP uses language tags ...
... languages are explicitly excluded.
HTTP uses language tags within the Accept-Language and Content-
Language ...
... language tags within the Accept-Language and Content-
Language fields.
The syntax and registry ...
... The syntax and registry of HTTP language tags is the same as that
defined by RFC 1766(-> 3282draft | 3066(-> 4647 | 4646)) [1 ...
... defined by RFC 1766(-> 3282draft | 3066(-> 4647 | 4646)) [1]. In summary, a language tag is composed of 1
or more parts: A primary language tag and a possibly empty series of
...
... 1]. In summary, a language tag is composed of 1
or more parts: A primary language tag and a possibly empty series of
subtags:
...
... tags are case-
insensitive. The name space of language tags is administered by the
IANA. Example tags ...
... where any two-letter primary-tag is an ISO 639 language abbreviation
and any two-letter initial subtag is an ISO 3166 country code ...
... | Accept-Encoding ; Section 14.3
| Accept-Language ; Section 14.4
| Authorization ; Section 14.8
...
... | Content-Encoding ; Section 14.12
| Content-Language ; Section 14.13
| Content-Length ; Section 14.14
...
... representations may be of the same media type, but use different
capabilities of that type, be in different languages, etc.
Any response containing an entity ...
... negotiation. Selection is based on the available representations of
the response (the dimensions over which it can vary; e.g. language,
content-coding, etc.) and the contents of particular header fields in
...
... user agent MAY include request header fields (Accept,
Accept-Language, Accept-Encoding, etc.) which describe its
preferences for such a response.
...
... Charset (section 14.2), Accept-Encoding (section 14.3), Accept-
Language (section 14.4), and User-Agent (section 14.42). However, an
origin server is not limited to these dimensions and MAY vary the
...
... Agent-driven negotiation is advantageous when the response would vary
over commonly-used dimensions (such as type, language, or encoding),
when the origin server is unable to determine a user agent ...
...
Warnings also carry a warning text. The text may be in any
appropriate natural language (perhaps based on the client's Accept
headers ...
... Accept-Language ...
...
The Accept-Language request-header field is similar to Accept, but
restricts the set of natural languages ...
... Language request-header field is similar to Accept, but
restricts the set of natural languages that are preferred as a
response to the request.
...
... range = ( ( 1*8ALPHA *( "-" 1*8ALPHA ) ) | "*" )
Each language-range MAY be given an associated quality value which
represents an estimate of the user's preference for the languages ...
... language-range MAY be given an associated quality value which
represents an estimate of the user's preference for the languages
specified by that range. The quality value defaults to "q=1". For
...
... example,
Accept-Language: da, en-gb;q=0.8, en;q=0.7
would mean: "I prefer Danish, but will accept British English and
...
...
would mean: "I prefer Danish, but will accept British English and
other types of English." A language-range matches a language-tag ...
... other types of English." A language-range matches a language-tag if
it exactly equals the tag ...
... prefix is "-".
The special range "*", if present in the Accept-Language field,
matches every tag not matched by any other range ...
... tag not matched by any other range present in the
Accept-Language field.
Note: This use of a prefix ...
... prefix matching rule does not imply that
language tags are assigned to languages in such a way that it is
always true that if a user understands a language ...
... matching rule does not imply that
language tags are assigned to languages in such a way that it is
always true that if a user understands a language with a certain
...
... language tags are assigned to languages in such a way that it is
always true that if a user understands a language with a certain
tag, then this user will also understand all languages ...
... language with a certain
tag, then this user will also understand all languages with tags
for which this tag ...
... language-tag by the
Accept-Language field is the quality value of the longest language-
range ...
... tag by the
Accept-Language field is the quality value of the longest language-
range in the field that matches the language ...
... range in the field that matches the language-tag. If no language-
range in the field matches the tag ...
... range in the field matches the tag, the language quality factor
assigned is 0. If no Accept-Language header ...
... tag, the language quality factor
assigned is 0. If no Accept-Language header is present in the
request, the server SHOULD assume that all languages ...
... Language header is present in the
request, the server SHOULD assume that all languages are equally
acceptable. If an Accept-Language header ...
... request, the server SHOULD assume that all languages are equally
acceptable. If an Accept-Language header is present, then all
languages ...
... Language header is present, then all
languages which are assigned a quality factor greater than 0 are
acceptable.
...
... It may be contrary to the privacy expectations of the user to send an
Accept-Language header with the complete linguistic preferences of
the user in every request. For a discussion ...
... client applications make the choice of
linguistic preference available to the user. If the choice is not
made available, then the Accept-Language header field must not be
given in the request.
...
... Content-Language ...
... entity-header field describes the natural
language(s) of the intended audience for the enclosed entity. Note
that this may not be equivalent to all the languages ...
... language(s) of the intended audience for the enclosed entity. Note
that this may not be equivalent to all the languages used within the
entity-body.
...
... tag
Language tags are defined in section 3.10. The primary purpose of
Content-Language is to allow a user to identify and differentiate
...
... 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
...
... Content-Language is to allow a user to identify and differentiate
entities according to the user's own preferred language. Thus, if the
body content is intended only for a Danish-literate audience, the
appropriate field is
...
... Language: da
If no Content-Language is specified, the default is that the content
is intended for all language audiences. This may mean that the sender ...
... If no Content-Language is specified, the default is that the content
is intended for all language audiences. This may mean that the sender
...
... sender
does not consider it to be specific to any natural language, or that
the sender does not know for which language ...
... language, or that
the sender does not know for which language it is intended.
Multiple languages ...
... language it is intended.
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
...
... Language: mi, en
However, just because multiple languages are present within an entity
does not mean that it is intended for multiple linguistic audiences.
...
... entity
does not mean that it is intended for multiple linguistic audiences.
An example would be a beginner's language primer, such as "A First
Lesson in Latin," which is clearly intended to be used by an
English-literate audience. In this case, the Content-Language ...
... language primer, such as "A First
Lesson in Latin," which is clearly intended to be used by an
English-literate audience. In this case, the Content-Language should
only include "en".
...
... only include "en".
Content-Language may be applied to any media type -- it is not
limited to textual documents.
...
... header.
The warn-text should be in a natural language and character set that
is most likely to be intelligible to the human user ...
... response. This decision may be based on any available knowledge,
such as the location of the cache or user, the Accept-Language field
in a request, the Content-Language field in a response, etc. The
...
... cache or user, the Accept-Language field
in a request, the Content-Language field in a response, etc. The
default language is English and the default character set ...
... in a request, the Content-Language field in a response, etc. The
default language is English and the default character set is ISO-
...
... Accept request-headers can reveal information about the user to all
servers which are accessed. The Accept-Language header in particular
can reveal information the user would consider to be of a private
...
... header in particular
can reveal information the user would consider to be of a private
nature, because the understanding of particular languages is often
strongly correlated to the membership of a particular ethnic group.
...
... User agents which offer the option to configure the contents of an
Accept-Language header to be sent in every request are strongly
encouraged to let the configuration process include a message which
...
... privacy would be for a user agent
to omit the sending of Accept-Language headers by default, and to ask
the user whether it should start ...
... headers by default, and to ask
the user whether it should start sending Accept-Language headers to a
server if it detects, by looking for any Vary response-header fields ...
... Alvestrand, H., "Tags for the identification of languages", RFC 1766(-> 3282draft | 3066(-> 4647 | 4646)), UNINETT, March 1995. ...
... Berners-Lee, T., and D. Connolly, "HyperText Markup Language Specification - 2.0", RFC 1866hist(-> 2854), MIT/LCS, November 1995. ...
... negotiation provided by the Vary field for
those resources that vary over common dimensions like type and
language.
The Alternates header field ...