Date: Fri, 3 May 2013 07:57:07 +0200 (CEST)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: "Joshua D. Drake" <jd@commandprompt.com>
cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: Documentation epub format
In-Reply-To: <518143D3.8060007@commandprompt.com>
Message-ID: <alpine.DEB.2.02.1305030747140.9292@localhost6.localdomain6>
References: <alpine.DEB.2.02.1305011144590.25330@localhost6.localdomain6>
	<518143D3.8060007@commandprompt.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


>> This seems to suggest that instead of generating one large ebook, the
>> build should generate a set of ebooks, say one for each part. At the
>> minimum, a less detailed toc could be more usable and help navigate the
>> huge contents.
>
> Once upon a time we had multiple books as documentation, then at some point 
> we merged them. It was quite a few years ago.
>
> I would agree at this point that we need to consider breaking them up again. 
> The documentation is unwieldy.

PostgreSQL documentation in PDF seemed quite usable on the same ipad, so 
maybe there is no unique answer. I like the principle and simplicity of 
"one" document to move around, so sticking to that if possible seems 
better.

-- 
Fabien.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers