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.
Indeed that makes sense as the issue is specific to this reader. I was
afraid that the problem was
On 04/05/13 18:11, Fabien COELHO wrote:
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.
Indeed that makes sense as the issue is specific to this
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
On Fri, May 3, 2013 at 07:57:07AM +0200, Fabien COELHO wrote:
This seems to suggest that instead of generating one large ebook, the
build should generate a set of ebooks, say one for each part. At the
minimum, a less detailed toc could be more usable and help navigate the
huge contents.
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
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
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
Bruce Momjian wrote:
On Fri, May 3, 2013 at 12:05:45PM -0400, Andrew Dunstan wrote:
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
On 05/01/2013 11:36 PM, Gavin Flower wrote:
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
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
On 03/05/13 15:16, 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
On Thu, May 02, 2013 at 03:42:33AM -0400, Andrew Dunstan wrote:
On 05/01/2013 11:36 PM, Gavin Flower wrote:
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
This seems to suggest that instead of generating one large ebook, the
build should generate a set of ebooks, say one for each part. At the
minimum, a less detailed toc could be more usable and help navigate the
huge contents.
Once upon a time we had multiple books as documentation, then at
Hello devs,
I've given a try to the PostgreSQL documentation in epub format.
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
On 05/01/2013 09:27 AM, Fabien COELHO wrote:
Hello devs,
I've given a try to the PostgreSQL documentation in epub format.
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
Joshua D. Drake j...@commandprompt.com writes:
Once upon a time we had multiple books as documentation, then at some
point we merged them. It was quite a few years ago.
I would agree at this point that we need to consider breaking them up
again. The documentation is unwieldy.
The reason we
I would second Tom on this, and if ePub is really a longer term goal of the
documentation, the various eBook formats have differing levels of support for
hyperlinking that would merit retaining everything in a single book that can be
linked from direct references.
Dru
On May 1, 2013, at 1:52
On Wed, May 01, 2013 at 01:52:43PM -0400, Tom Lane wrote:
Joshua D. Drake j...@commandprompt.com writes:
Once upon a time we had multiple books as documentation, then at some
point we merged them. It was quite a few years ago.
I would agree at this point that we need to consider breaking
On 05/01/2013 10:52 AM, Tom Lane wrote:
Joshua D. Drake j...@commandprompt.com writes:
Once upon a time we had multiple books as documentation, then at some
point we merged them. It was quite a few years ago.
I would agree at this point that we need to consider breaking them up
again. The
On 05/01/2013 10:56 AM, Andrew Satori wrote:
I would second Tom on this, and if ePub is really a longer term goal of the
documentation, the various eBook formats have differing levels of support for
hyperlinking that would merit retaining everything in a single book that can be
linked from
On Wed, May 1, 2013 20:13, Joshua D. Drake wrote:
I don't think ePub is a problem here, we will have the same problem with
PDF. The issue is the sheer size of the manual. If we can solve the
cross referencing issue, breaking them up makes sense I would think.
I like the one-huge-chunk pdf:
On May 1, 2013, at 2:11 PM, Joshua D. Drake j...@commandprompt.com wrote:
On 05/01/2013 10:52 AM, Tom Lane wrote:
Joshua D. Drake j...@commandprompt.com writes:
Once upon a time we had multiple books as documentation, then at some
point we merged them. It was quite a few years ago.
I
On Wed, May 01, 2013 at 09:33:23AM -0700, Joshua D. Drake wrote:
On 05/01/2013 09:27 AM, Fabien COELHO wrote:
Hello devs,
I've given a try to the PostgreSQL documentation in epub format.
I must admit that there is a bit of a disappointement as far as the user
experience is
On 05/01/2013 10:52 AM, Tom Lane wrote:
Joshua D. Drake j...@commandprompt.com writes:
Once upon a time we had multiple books as documentation, then at some
point we merged them. It was quite a few years ago.
I would agree at this point that we need to consider breaking them up
again. The
Also the divisions between sections were totally arbitrary and unintuitive.
I think it would make a lot more sense to modify the SGML export to
create a book per chapter.
Also ... why is this discussion not on pgsql-docs, where it belongs?
Crossing it over.
--
Josh Berkus
PostgreSQL
On Wed, May 1, 2013 at 5:27 PM, Fabien COELHO coe...@cri.ensmp.fr 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
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
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
28 matches
Mail list logo
