M
Michael
Hi
how to automatically use different languages alike winehq.org etc.?
Many thanks
Michael
how to automatically use different languages alike winehq.org etc.?
Many thanks
Michael
how to automatically use different languages alike winehq.org etc.?
Beware of over-generalized assumptions...
It's often OK to user [sic] English as fallback
... because sometimes, even people who *do* take such things seriously
still fall prey to the occasional typo.
how to automatically use different languages alike winehq.org etc.?
... 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
body content is intended only for a Danish-literate audience, the
appropriate field is
Content-Language: da
If no Content-Language is specified, the default is that the content
is intended for all language audiences. This might mean that the
sender does not consider it to be specific to any natural language,
or that the sender does not know for which 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
versions, would call for
Content-Language: mi, en
However, just because multiple languages are present within an 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 would
properly only include "en".
"The Content-Language entity-header field describes
the natural language(s) of the intended audience for the enclosed
entity.
So 'Content-Language' is not appropriate for specifying the language of
the content as specifying:
Content-Language: en
would mean: "intended only for native English speakers",
I'm not really fond of the current 'Content-Language' intention as I
find it quite useless compared to the use of specifying the language of
the entity, but that's what has been really specified.
"The Content-Language entity-header field describes
the natural language(s) of the intended audience for the enclosed
entity.
That's a sloppy wording in the HTTP protocol, and it gets worse:
[...]Content-Language: en
would mean: "intended only for native English speakers",
No, it does not mean that. The HTTP protocol just describes the
header poorly. What it wants to say, more or less, applied to this
particular case, is that the header informs that the resource is
intended for people who understand English, in some vague sense.
So, is it correct to say specifying:
Content-Language: <LN>
where <LN> is a two-letter language code, is always appropriate for a
content mainly written in the given language?
And of course you also warn the user that cookies are used, and that
they should not empty their cookie-jar if they want to keep the
language setting in the future.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.