X-Original-To: pgsql-docs@postgresql.org
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP
	id A7E44475ADE; Sun, 23 Feb 2003 05:57:34 -0500 (EST)
Received: from postgresql.org ([64.49.215.8])
	by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with
	SMTP id 68196-01; Sun, 23 Feb 2003 05:57:23 -0500 (EST)
Received: from post.webmailer.de (natsmtp00.webmailer.de [192.67.198.74])
	by postgresql.org (Postfix) with ESMTP
	id B9D64475B33; Sun, 23 Feb 2003 05:56:27 -0500 (EST)
Received: from ianb.local (pD95175F3.dip.t-dialin.net [217.81.117.243])
	by post.webmailer.de (8.9.3/8.8.7) with ESMTP id LAA10167;
	Sun, 23 Feb 2003 11:56:28 +0100 (MET)
Content-Type: text/plain;
  charset="us-ascii"
From: Ian Barwick <barwick@gmx.net>
To: pgsql-hackers@postgresql.org
Subject: Linking to "current" docs
Date: Sun, 23 Feb 2003 11:55:56 +0100
X-Mailer: KMail [version 1.4]
Cc: pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200302231155.56141.barwick@gmx.net>
X-Virus-Scanned: by amavisd-new
X-Archive-Number: 200302/28
X-Sequence-Number: 1662


With the "old" idocs it was possible to create links to the "current"
version of individual documentation pages without having to
provide a Postgres version number, e.g.:

http://www.PostgreSQL.org/idocs/index.php?kernel-resources.html

which would remain constant over longer periods of time. Providing
no major restructuring of the docs takes place, this is a useful
low-maintenance way of linking to the docs without worrying
too much about version changes and seems to be used in a=20
variety of places.

With the new documentation at http://www.postgresql.org/docs/
(which is BTW very nice) this approach doesn't appear to work :-(.

Would it be possible to modify the new docs to provide similar
functionality? E.g. something like

http://www.postgresql.org/docs/view.php?version=3Dcurrent&idoc=3D0&file=3Ds=
ql-createtable.html

If neccessary I can provide time to do this (though I have no idea
of what would be involved ;-).

Ian Barwick
barwick@gmx.net