Re: Documentation epub format - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Documentation epub format
Date
Msg-id 20130503162808.GA15498@momjian.us
Whole thread Raw
In response to Re: Documentation epub format  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Documentation epub format  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-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. +



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Remaining beta blockers
Next
From: Tom Lane
Date:
Subject: Re: matview niceties: pick any two of these three