According to Joshua Slive:
> Hmmm... Before you go coding anything, I think you should
> carefully read
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4
>
> I am not a language lawyer, but the way I interpret that
> is if the browser wants "en", it must ask for "en".
But the document says:
"A language-range matches a language-tag if it exactly equals the
tag, or if it exactly equals a prefix [...]
Note: This use of a 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 with a certain
tag, then this user will also understand all languages with tags
for which this tag is a prefix. The prefix rule simply allows the
use of prefix tags if this is the case."
This sounds to me like it _is_ an option to serve for example an
"en" variant to a client requesting "en-US" and im pretty sure
that this is how mod_negotiation of 1.3 behaves.
IMHO this should be the default behaviour in 2.0 as well and
not something the user should/can configure via ForceDefaultLanguage.
IMHO it's silly to reply with a 'not acceptable' response in such
a case.
BTW, for Germany you might use "de-DE" as a language extension
which is damn equal to "de".
ciao...
--
Lars Eilebrecht - Perl: The only language you can
[EMAIL PROTECTED] uuencode and not notice.
