Date: Fri, 3 May 2013 09:30:53 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: "Joshua D. Drake" <jd@commandprompt.com>,
	PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: Documentation epub format
Message-ID: <20130503133053.GH5933@momjian.us>
References: <alpine.DEB.2.02.1305011144590.25330@localhost6.localdomain6>
	<518143D3.8060007@commandprompt.com>
	<alpine.DEB.2.02.1305030747140.9292@localhost6.localdomain6>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1305030747140.9292@localhost6.localdomain6>
User-Agent: Mutt/1.5.20 (2009-06-14)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On Fri, May  3, 2013 at 07:57:07AM +0200, Fabien COELHO wrote:
> 
> >>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.

No question that PDF readers with collapsable index sections is a huge
win for our documentation.  It isn't really the docs itself that control
that.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


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