From: Bruce Momjian <bruce@momjian.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: Documentation epub format
Date: Fri, 3 May 2013 12:28:08 -0400
Message-ID: <20130503162808.GA15498@momjian.us> (raw)
In-Reply-To: <5183E059.2070207@dunslane.net>
References: <alpine.DEB.2.02.1305011144590.25330@localhost6.localdomain6>
<1367550999.25798.4.camel@vanquo.pezone.net>
<5183E059.2070207@dunslane.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Fri, May 3, 2013 at 12:05:45PM -0400, Andrew Dunstan wrote:
>
> On 05/02/2013 11:16 PM, Peter Eisentraut wrote:
> >On Wed, 2013-05-01 at 18:27 +0200, Fabien COELHO wrote:
> >>The table of contents too much detailed, so it is long and slow to
> >>scan, and there is no clear shortcut. Flipping pages in the
> >>documentation takes ages (well, close to one second or more if I flip
> >>a few pages). Do not try "search".
> >EPUB is essentially a zip file with per-section simplified HTML files.
> >So any device that can render simple web pages should be able to handle
> >that with ease. What I think iBooks is doing is it internally
> >pre-renders all the pages in order to be able to attach page numbers to
> >all the table of contents entries. I suspect other readers that don't
> >do that will be able to handle this better.
> >
> >That said, I think trimming down the table of contents nesting depth
> >might be worth checking into for this output format.
> >
> >
>
> I don't think we should be governed by the silly behaviour of one
> epub reader. My ereader doesn't collapse the contents into one giant
> list. If ibooks is doing stuff badly, complain to Apple.
I tend to agree. Losing the ability to link across books is a big loss,
and I am unclear how we would allow that for books split into files.
--
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, andrew@dunslane.net, peter_e@gmx.net, coelho@cri.ensmp.fr, pgsql-hackers@postgresql.org
Subject: Re: Documentation epub format
In-Reply-To: <20130503162808.GA15498@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox