Re: Can extension build own SGML document? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Can extension build own SGML document?
Date
Msg-id CA+Tgmob7_XyGP7g0HwX5jd3JcnqGG9prvy_QT9QP=nC_uAvZFw@mail.gmail.com
Whole thread Raw
In response to Re: Can extension build own SGML document?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Wed, Sep 16, 2015 at 12:16 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On 9/15/15 11:45 AM, Robert Haas wrote:
>> On Tue, Sep 15, 2015 at 9:43 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> AFAICT from a quick look at its documentation, asciidoc can produce
>>> either html or docbook output; so as soon as you want something other
>>> than html output (in particular, PDF), you're back to relying on the
>>> exact same creaky docbook toolchain we use now.  Only with one extra
>>> dependency in front of it.
>>>
>>> Personally I never look at anything but the HTML rendering, but I doubt
>>> that dropping support for all other output formats would fly :-(
>>
>> Just out of curiosity, really?
>
> Man pages are in wide use, I think.

Hmm, yeah.

>> I mean, I can't see that building a PDF of the documentation really
>> has much value, and I don't know even what else we can build.  Who in
>> 2015 would use a PDF instead of HTML?
>
> PDF is actually kind of neat for searches across the whole document.

OK.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_resetxlog sentences
Next
From: Robert Haas
Date:
Subject: Re: Reliance on undefined behaviour in << operator