Language

hi I am translating parts of the documentation to german. If there is someone doin the same please let me know, so that we can coordinate our work. thx torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands

[PATCH] Typemaps with Bodies (for errors/language variants)

It wasn't very clear - this is the first stab at the Typemap/content patch, with an example combined error page. From: "William A. Rowe, Jr." <[EMAIL PROTECTED]> > > From: "Martin Kraemer" <[EMAIL PROTECTED]> > > > > On Sun, Aug 19, 2001 at 11:10:15PM -0500, William A. Rowe, Jr. wrote: > > > By

Re: Multi Language Error Documents

On Sun, 19 Aug 2001, William A. Rowe, Jr. wrote: > 4. Change the default document list to serve index.html index.html.var in > that order. >This will shortcut a ton of time negotating the content by stat() calls, > since >without Multiviews we won't look for index.html.*, but we will cat

Re: Multi Language Error Documents

And a little nit... Apart from the security and performance concerns of having multiviews on by default, there's the little problem I've noticed that recent MSIE vintages seem to be sending "en-us" as its default language, not "en", so the distributed config should

Re: Multi Language Error Documents

According to Rodent of Unusual Size: > Lars Eilebrecht wrote: > > > > We already activate MultiViews by default > > We do? Yes, we define "Options Indexes FollowSymLinks MultiViews" for "/". ciao... -- Lars Eilebrecht - Computers are not intelligent. [EMAIL PROTECTED]

Re: Multi Language Error Documents

Lars Eilebrecht wrote: > > We already activate MultiViews by default We do? -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "All right everyone! Step away from the glowing hamburger!" -

Re: Multi Language Error Documents

According to William A. Rowe, Jr.: > Could this solution presuade everybody between 0 and +1 for negotated > content? +1 on the concept! ciao... -- Lars Eilebrecht - A clean, neat, and orderly work place [EMAIL PROTECTED] - is a sure sign of a sick mind.

Re: Multi Language Error Documents

should enable it by default. > > > > > > Not just yet ... let's get the language issues straightened out. Also, > > > it > > > loads down the server, dunno if we want to do that to administrators :) > > > > We already activate MultiViews by d

Re: Multi Language Error Documents

this to httpd-std.conf. I believe > > >that we should enable it by default. > > > > Not just yet ... let's get the language issues straightened out. Also, it > > loads down the server, dunno if we want to do that to administrators :) > > We already act

Re: Multi Language Error Documents

ve > >that we should enable it by default. > > Not just yet ... let's get the language issues straightened out. Also, it > loads down the server, dunno if we want to do that to administrators :) We already activate MultiViews by default, so I don't think this is

Re: Multi Language Error Documents

From: "Joshua Slive" <[EMAIL PROTECTED]> Sent: Saturday, August 18, 2001 10:26 PM > On Sun, 19 Aug 2001, Lars Eilebrecht wrote: > > > Hi guys, > > > > as requested, I've committed my current version (with a few > > changes) of the multi languag

Re: Multi Language Error Documents

On Sun, 19 Aug 2001, Lars Eilebrecht wrote: > Hi guys, > > as requested, I've committed my current version (with a few > changes) of the multi language error documents to httpd-docs-2.0. > Although I haven't yet seen the commit email. Hmm... Looks good from here. I hav

Multi Language Error Documents

Hi guys, as requested, I've committed my current version (with a few changes) of the multi language error documents to httpd-docs-2.0. Although I haven't yet seen the commit email. Hmm... We could add it to 1.3 aswell, but I think we should just focus on 2.0 here and use my stuff as

[Fwd: Language selection on apache web site]

I am not sure if she is right or not. *Should* it find the .en case if all she has is en-gb and ja in her Accept-Language? -- #kenP-)} Ken Coar<http://Golux.Com/coar/> Apache Software Foundation <http://www.apache.org/> "Apache Server for Dummie

Re: Language Negotiation: "No Acceptable Variant"

ceptable Variants" ErrorDocument when negotiation fails, but the > > ErrorDocument itself is subject to the FallBackLanguage directive in case > > it can't find a good language. > > > > And possibly: > > > > 3. Change the default text of the "No Acc

Re: Language Negotiation: "No Acceptable Variant"

> 2. Add a "FallBackLanguage" directive to use when negotiation fails. > > These directives could be combined such that ordinary content gets the "No > Acceptable Variants" ErrorDocument when negotiation fails, but the > ErrorDocument itself is subject to the Fal

Re: Language Negotiation: "No Acceptable Variant"

ent could be used to list all the available variants. Then here's where the fun part comes: what if you don't have an ErrorDocument in any of the "acceptable" languages? In general, the webmaster is the one best able to know what language should be served in that case. For e

Re: Language Negotiation: "No Acceptable Variant"

On Mon, 29 Jan 2001, Joshua Slive wrote: > On Mon, 29 Jan 2001, Koen Holtman wrote: > > Wait a minute: is the problem that these many people send, say > > > > Accept-language: fr > > > > when they in fact speak en+fr and prefer en, or is the problem that t

Re: Language Negotiation: "No Acceptable Variant"

On Mon, 29 Jan 2001, Koen Holtman wrote: > I recall that, in any case the last time I touched it, mod_negotiation had > a heuristic for the second case above: with Accept-language: en-gb, > mod_negotiation will assume that `en' is also still OK, so in that case > the user would ge

Re: Language Negotiation: "No Acceptable Variant"

On Tue, 30 Jan 2001, James Sutherland wrote: > On Mon, 29 Jan 2001, Joshua Slive wrote: > > > On Mon, 29 Jan 2001, Koen Holtman wrote: > > > Wait a minute: is the problem that these many people send, say > > > > > > Accept-language: fr > > > &

Re: Language Negotiation: "No Acceptable Variant"

On Mon, 29 Jan 2001, Joshua Slive wrote: > On Mon, 29 Jan 2001, Koen Holtman wrote: > > Wait a minute: is the problem that these many people send, say > > > > Accept-language: fr > > > > when they in fact speak en+fr and prefer en, or is the problem that their &g

Re: Language Negotiation: "No Acceptable Variant"

On Mon, 29 Jan 2001, Koen Holtman wrote: > Wait a minute: is the problem that these many people send, say > > Accept-language: fr > > when they in fact speak en+fr and prefer en, or is the problem that their > browsers do not send any accept-language at all? > The probl

Re: Language Negotiation: "No Acceptable Variant"

s in english. This is causing hundreds of "no acceptable variant" > errors per day on the "multi-views" negotiated > pages under httpd.apache.org/docs/. Wait a minute: is the problem that these many people send, say Accept-language: fr when they in fact speak en+fr and pre

Re: Language Negotiation: "No Acceptable Variant"

mark the documents in the fallback language with any language This doesn't work, because a browser configured for "en,fr" priority would get the "fr" page unless there is a specifcally designated "en" page. The work-around I suggested is to include BOTH an &quo

Re: Language Negotiation: "No Acceptable Variant"

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

Re: Language Negotiation: "No Acceptable Variant"

BTW, can't help but think that recent posts in this discussion were more appropriate on new-httpd... david > > > > There seem to be some on new-httpd? Maybe try asking there. > > Lars Eilebrecht <[EMAIL PROTECTED]> for sure.

Re: Language Negotiation: "No Acceptable Variant"

David Reid wrote: > > There seem to be some on new-httpd? Maybe try asking there. Lars Eilebrecht <[EMAIL PROTECTED]> for sure. -- #kenP-)} Ken Coar Apache Software Foundation "Apache Server for Dummies"

Re: Language Negotiation: "No Acceptable Variant"

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

Re: Language Negotiation: "No Acceptable Variant"

There seem to be some on new-httpd? Maybe try asking there. david - Original Message - From: "Joshua Slive" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 29, 2001 4:53 PM Subject: Re: Language Negotiation: "No Acceptable Variant" >

Re: Language Negotiation: "No Acceptable Variant"

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'

Re: Language Negotiation: "No Acceptable Variant"

I agree with James -- this should be solved with a directive, not additional files or symlinks. The case I was thinking of is a Japanese mirror of httpd.apache.org, where they can mirror the 'master' content tree exactly, but specify in their local httpd.conf which language to &#x

Re: Language Negotiation: "No Acceptable Variant"

On Sun, 28 Jan 2001, Joshua Slive wrote: > A quick look at the error logs on apache.org shows almost 500 "No > Acceptable Variant" errors so far today. Many of these errors are caused > by people with misconfigured browsers trying to deal with our new > language-neg

Language Negotiation: "No Acceptable Variant"

A quick look at the error logs on apache.org shows almost 500 "No Acceptable Variant" errors so far today. Many of these errors are caused by people with misconfigured browsers trying to deal with our new language-negotiated manual. (I am defining "misconfigured" as no