Message-ID: <5181DF59.10302@archidevsys.co.nz>
Date: Thu, 02 May 2013 15:36:57 +1200
From: Gavin Flower <GavinFlower@archidevsys.co.nz>
Organization: ArchiDevSys
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130328 Thunderbird/17.0.5
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>
	<1367465025.32604.13.camel@vanquo.pezone.net>
In-Reply-To: <1367465025.32604.13.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 02/05/13 15:23, Peter Eisentraut wrote:
> On Wed, 2013-05-01 at 18:27 +0200, Fabien COELHO wrote:
>> I must admit that there is a bit of a disappointement as far as the
>> user experience is concerned: the generated file is barely usable on
>> an iPad2 with the default iBooks reader, which was clearly not
>> designed for handling a "4592" pages book (from its point of view).
> Well, clearly there are mainstream books that have 1000 pages, so it
> ought to be designed for that.  It's not clear to me then why it
> necessarily must fail at 4000 pages.  I think you might want to run some
> experiments to see what the reader can handle before we start doing
> anything.
>
>
There might be something silly in some eReaders, like reserving 12 bits 
for page numbers internally - as 'no one will ever want a book with more 
than 4095 pages!'?


Cheers,
Gavin


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