Return-Path: 
 <docs-return-4062-apmail-httpd-docs-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-docs-archive@httpd.apache.org
Received: (qmail 98498 invoked by uid 500); 25 Sep 2002 18:25:48 -0000
Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:docs-help@httpd.apache.org>
list-unsubscribe: <mailto:docs-unsubscribe@httpd.apache.org>
list-post: <mailto:docs@httpd.apache.org>
Reply-To: docs@httpd.apache.org
Delivered-To: mailing list docs@httpd.apache.org
Received: (qmail 98486 invoked from network); 25 Sep 2002 18:25:47 -0000
Message-ID: <3D91FFA7.7080000@slive.ca>
Date: Wed, 25 Sep 2002 14:25:43 -0400
From: Joshua Slive <joshua@slive.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en, fr
MIME-Version: 1.0
To: docs@httpd.apache.org
Subject: Re: links to english originals
References: <Xns929213DF01948ndparker@news.perlig.de>
 <3D8F4E55.5000903@slive.ca> <7613183637.20020924172757@perlig.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Andr=E9 Malo wrote:

> hmm, I think, sitemap.xml is the right place for storing that info.
>=20
> <page alternate=3D"de ja ru">...</page>

Not the best xml ;-)  More like <page=20
href=3D""><variant>en</variant><variant>de</variant></page> or something =

like that.  We're supposed to able to avoid parsing strings for spaces=20
to get at our data.

>=20
> or so. (but doesn't solve the problem...)

It potentially could, but is probably an over-complex solution for the=20
problem at hand.  As I said, if the translations start to get large, we=20
may want to switch to typemaps pointing at different directories.  Then=20
something like this would be very useful.


> But... I don't like JS ;-)

I agree on principal

> I actually would prefer a SSI=20

I'd really prefer not to have the parse all the docs for SSI just for=20
this little thing.

> or better a post processing
> solution (for example a perl script similiar to expand.pl).

That is a possibility.  I would want to use a proper xml parser=20
(possibly from within perl) and not just a search/replace thing.

Anyway, lets think about the problem a little more before we try=20
anything.  That way we can hopefully come up with a solution that will=20
help us in other areas as well.

You might want to add the idea to STATUS so we don't forget it.

Joshua.


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org