pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Satori <dru@druware.com>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: Documentation epub format
Date: Wed, 1 May 2013 14:24:08 -0400
Message-ID: <EE7F2F2A-8F93-47B2-9815-DF32D00B0E45@druware.com> (raw)
In-Reply-To: <51815AEC.80901@commandprompt.com>
References: <alpine.DEB.2.02.1305011144590.25330@localhost6.localdomain6>
	<518143D3.8060007@commandprompt.com>
	<25988.1367430763@sss.pgh.pa.us>
	<51815AEC.80901@commandprompt.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>


On May 1, 2013, at 2:11 PM, "Joshua D. Drake" <jd@commandprompt.com> wrote:

> 
> On 05/01/2013 10:52 AM, Tom Lane wrote:
>> "Joshua D. Drake" <jd@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 merged them was to allow hyperlink cross-references between
>> different parts of the docs.  I would be sad to lose that.\
> 
> Defintely. Is there no way to cross reference multiple documents?
> 
> Peter?
> 


The weakness (IMO) is that you are trading off one large file for several smaller ones.  The documentation is unwieldily because of the depth and breadth, not the size of the file.  Thinking in terms of common use cases, you would have the the published document on an offline device.  For external linking you would have to assume a directory structure, or multiple files all local in the same directory, and that's assuming the various formats for doing the linking.  While there is fairly broad support for link points within a document, or to an http(s) url in formats like epub and pdf.  file:// uri's are far less robust in support, and it is quite hit or miss in the various readers.  Other than local HTML, I cannot think of a format that has good local file/relative path support for linking multiple documents, and broad device/platform support.
Dru






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



view thread (29+ messages)  latest in thread

Message-ID: <EE7F2F2A-8F93-47B2-9815-DF32D00B0E45@druware.com>
Permalink:  ../EE7F2F2A-8F93-47B2-9815-DF32D00B0E45@druware.com/
Also on:    postgresql.org/message-id/EE7F2F2A-8F93-47B2-9815-DF32D00B0E45@druware.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: dru@druware.com, jd@commandprompt.com, tgl@sss.pgh.pa.us, coelho@cri.ensmp.fr, pgsql-hackers@postgresql.org
  Subject: Re: Documentation epub format
  In-Reply-To: <EE7F2F2A-8F93-47B2-9815-DF32D00B0E45@druware.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox