Message-ID: <5183E059.2070207@dunslane.net>
Date: Fri, 03 May 2013 12:05:45 -0400
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: Fabien COELHO <coelho@cri.ensmp.fr>,
	PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: Documentation epub format
References: <alpine.DEB.2.02.1305011144590.25330@localhost6.localdomain6>
	<1367550999.25798.4.camel@vanquo.pezone.net>
In-Reply-To: <1367550999.25798.4.camel@vanquo.pezone.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


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.

cheers

andrew


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