Date: Fri, 3 May 2013 08:05:28 +0200 (CEST)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Peter Eisentraut <peter_e@gmx.net>
cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: Documentation epub format
In-Reply-To: <1367550999.25798.4.camel@vanquo.pezone.net>
Message-ID: <alpine.DEB.2.02.1305030757310.9292@localhost6.localdomain6>
References: <alpine.DEB.2.02.1305011144590.25330@localhost6.localdomain6>
	<1367550999.25798.4.camel@vanquo.pezone.net>
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


>> 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.

Indeed, iBooks computes page numbers, which mean processing the whole 
contents.

> That said, I think trimming down the table of contents nesting depth
> might be worth checking into for this output format.

That at least would be a relief. The TOC on iBooks is shown as a very long 
scrolling window, without collapsable parts.

-- 
Fabien.


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