Message-ID: <5183DFB7.6060502@gmx.net>
Date: Fri, 03 May 2013 12:03:03 -0400
From: Peter Eisentraut <peter_e@gmx.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
	rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Fabien COELHO <coelho@cri.ensmp.fr>
CC: 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>
	<alpine.DEB.2.02.1305030757310.9292@localhost6.localdomain6>
In-Reply-To: <alpine.DEB.2.02.1305030757310.9292@localhost6.localdomain6>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 5/3/13 2:05 AM, Fabien COELHO wrote:
>> 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.

After trying out a few different EPUB readers on iOS (iPhone), I think
this is simply a quality-of-implementation issue with iBooks.  For
example, NeoSoar's reader is much more responsive with the same file on
the same hardware.  Its page counting is much more nonsensical, but that
just seems to support my earlier theory.


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