Return-Path: 
 <forrest-dev-return-9865-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org
Received: (qmail 63233 invoked from network); 28 Apr 2004 08:34:45 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 28 Apr 2004 08:34:45 -0000
Received: (qmail 87953 invoked by uid 500); 28 Apr 2004 08:34:18 -0000
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 87906 invoked by uid 500); 28 Apr 2004 08:34:18 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 87893 invoked from network); 28 Apr 2004 08:34:17 -0000
Received: from unknown (HELO fep21-app.kolumbus.fi) (193.229.0.48)
  by daedalus.apache.org with SMTP; 28 Apr 2004 08:34:17 -0000
Received: from [80.186.92.169] by fep21-app.kolumbus.fi with ESMTP
          id <20040428083430.LSDM19565.fep21-app.kolumbus.fi@[80.186.92.169]>
          for <forrest-dev@xml.apache.org>; Wed, 28 Apr 2004 11:34:30 +0300
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <408EAE86.4030805@upaya.co.uk>
References: <405B648E.60606@che-che.com>
 <442628A7-7BD9-11D8-9F85-000393BD5B24@kolumbus.fi>
 <405EAFB1.4050108@che-che.com>
 <8DF68F7E-7BFE-11D8-9F85-000393BD5B24@kolumbus.fi>
 <405F0D31.3010403@che-che.com>
 <2960508C-7CAD-11D8-9F85-000393BD5B24@kolumbus.fi>
 <40615A5E.3080901@upaya.co.uk>
 <23261D5C-7E25-11D8-B4CF-000393BD5B24@kolumbus.fi>
 <4062D395.6090007@upaya.co.uk>
 <7E645CBD-92C6-11D8-9363-000393BD5B24@kolumbus.fi>
 <40855688.5020809@upaya.co.uk> <408E4F90.80900@che-che.com>
 <408EAE86.4030805@upaya.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <DF0F6B9A-98EE-11D8-A8B9-000393BD5B24@kolumbus.fi>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?Sjur_N=F8rsteb=F8_Moshagen?= <sjur.moshagen@kolumbus.fi>
Subject: Re: [I18n] Alternatives locales for a given page.
Date: Wed, 28 Apr 2004 11:34:31 +0300
To: forrest-dev@xml.apache.org
X-Mailer: Apple Mail (2.613)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Nice work!

P=E5 27. apr. 2004 kl. 22.03 skrev Upayavira:

> Well, the nested input module support isn't that spectacular, it just=20=

> means you can do {request-param:{1}}, for example, which you couldn't=20=

> do before.
>
> Here's some further thoughts, had during a nice warm bath:
>
> The below assumes that the content is stored in the following=20
> structure:
>
> /xml/en/*.xml
> /xml/de/*.xml
> /xml/pl/*.xml
>
> Syntax isn't quite right yet, but the idea is there:

<snip/>

> <!-- This one handles urls like www.host.com/foo.html, using the=20
> locale to
>        identify which language, with appropriate fallback -->
> <map:match pattern=3D"**.html">
>  <map:generate src=3D"{i18n:xml/LOCALE/{1}.xml"/>
>   ...
> </map:match>

This is the one that I'm after, in terms of url type and content=20
negotiation.

> This _should_ be compatible with the CLI and Apache, I think.

I know nothing about the CLI, so no comment here.

Apache:
Your proposed directory structure might work ok with apache, but I=20
don't see how you could get content negotiation in Apache 1.x - the=20
standad approach is to have all files in one common directory, with=20
locale suffixes on each file, like:

/xml/*.xml.en
/xml/*.xml.de
/xml/*.xml.pl

In Apache 2.x your suggested directory structure can more easily be=20
handled, I believe (haven't tried it), since the preferred setup for=20
content negotiation is done through a var file (var =3D variants). It =
has=20
the same name as the name of the files to do content negotiation for,=20
with the suffix .var, and with content like:

# This file is used by Apache 2 to support content negotiation
URI: index.html.en
Content-language: en
Content-type: text/html;charset=3DUTF-8

URI: index.html.de
Content-language: de
Content-type: text/html;charset=3DUTF-8

If you want to support a directory structure as yours, the generated=20
static site would be something like:

/xml/index.var
/xml/en/index.html
/xml/de/index.html
...

and the corresponding var file should be something like:

# This file is used by Apache 2 to support content negotiation
URI: en/index.html
Content-language: en
Content-type: text/html;charset=3DUTF-8

URI: de/index.html
Content-language: de
Content-type: text/html;charset=3DUTF-8

(NOTE: I have NOT tested this).

I would recommend going for the standard Apache approach when=20
generating static sites, and generate the .var file as well (the=20
default configuration of Apache 2 won't do content negotiation without=20=

the .var file), that is:

/xml/*.xml.en
/xml/*.xml.de
/xml/*.xml.pl
/xml/*.var

This way, the generated static site will work with both Apache 1.x and=20=

Apache 2.x utilizing content negotiation without further ado.

Sjur