From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Documentation epub format |
Date: | 2013-05-03 13:30:53 |
Message-ID: | 20130503133053.GH5933@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2013-05-03 16:03:03 | Re: Documentation epub format |
Previous Message | Fabien COELHO | 2013-05-03 06:05:28 | Re: Documentation epub format |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-05-03 13:40:51 | Re: Recovery target 'immediate' |
Previous Message | Bruce Momjian | 2013-05-03 13:29:20 | Re: Recovery target 'immediate' |