Date: Thu, 26 Jul 2007 00:13:14 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Michael Glaesemann <grzm@seespotcode.net>
Cc: "Joshua D. Drake" <jd@commandprompt.com>, pgsql-docs@postgresql.org
Subject: Re: Links wrong in docs
Message-ID: <20070726041314.GF3241@alvh.no-ip.org>
Mail-Followup-To: Michael Glaesemann <grzm@seespotcode.net>,
	"Joshua D. Drake" <jd@commandprompt.com>, pgsql-docs@postgresql.org
References: <46A81854.1010606@commandprompt.com>
	<5AAC03DB-B1BA-43CE-AC6F-3EE9311BF7CC@seespotcode.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5AAC03DB-B1BA-43CE-AC6F-3EE9311BF7CC@seespotcode.net>
User-Agent: Mutt/1.5.16 (2007-06-11)

Michael Glaesemann wrote:
>
> On Jul 25, 2007, at 22:43 , Joshua D. Drake wrote:
>
>> I noticed the other day that if you are viewing the release notes for a 
>> particular version that the prev / next links are wrong. E.g., If I am 
>> reading 8.1.8 and want to read 8.1.9 I have to hit previous, instead of 
>> next.
>
> I think it's because the releases are listed newest first, so when you hit 
> next you're not getting the next release, but the next release notes. While 
> perhaps a bit confusing on the individual pages, I still think it's best to 
> have the release notes in reverse chronological order.

Yeah.  It is confusing if you _think_ about it, but if you just use it,
it's fine (after all, we've been using it this way for years.  I mean
even Joshua used to use it and not notice it was backwards).

Probably the only thing you could actually do about it is change the
text in the link so it said "previous release" (resp. "next release")
instead of "next" (resp. "previous"), but I have zero idea what it would
take.  It's probably a lot more work than it's worth, if it's possible
at all.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support