On Mon, 29 Jan 2001, James Sutherland wrote: > On Mon, 29 Jan 2001, Joshua Slive wrote: > > > On Mon, 29 Jan 2001, Chris Pepper wrote: > > > A DefaultLanguage directive (defaulting to en), specifying > > > the preferred language(s) for browsers that don't specify their own > > > preference, seems like the right way to do it. > > > > Thanks for the feedback Chris and James. I don't disagree with the > > conclusion. I should point out, to avoid confusion, that Apache does > > have a DefaultLanguage directive, but it DOES NOT do what we want. > > Yes - I remembered seeing it somewhere, but not doing this :-( > > > It just specifies the language associated with all non-specified > > files. What we want is a directive that will indicate what file to > > send when no acceptable variants are found. > > Yes... FallbackLanguage?? > > > I get the feeling, however, that we are all talking about something that > > we really don't know much about. I wish we had some real language > > negotation experts here. > > Apparently there are some on new-httpd; CC-ed there in case they can help.
Only seeing the message text above, I don't believe that I fully understand the context of the question, but... - Have you looked into the LanguagePriority directive? I'm not sure if that does what you want, I am a bit confused about the text about `Correctly implemented HTTP/1.1 requests will mean this directive has no effect.' in the docs for LanguagePriority. I have not read the source yet to find out what this really means. If LanguagePriority does not work for you, alternative tricks that might work are: - do not mark the documents in the fallback language with any language - use type map files and use the qs= feature in there to set the source quality of the document in the fallback language higher than the others. Both of these force the negotiation algorithm into the desired (I think) behavior, but both are not perfect solutions.. Koen.
