From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Can extension build own SGML document? |
Date: | 2015-09-15 13:43:42 |
Message-ID: | 22642.1442324622@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> I'm not sure SGML is the way to go anymore anyways. Asciidoc offers a
> lot of what our SGML does in a much easier to support toolchain. It's
> also natively supported by github, which makes it nice for others to
> view the output (see [1] as an exmaple). If asciidoc isn't powerful
> enough for what you need you can switch to asciidoctor which is even
> more powerful[2].
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 :-(
I do agree that the SGML toolchain is getting pretty long in the tooth
and we need to be looking for something else.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-09-15 13:46:27 | Re: Could the configure script detect the endianness for a Power CPU with endianness mode change |
Previous Message | Jan Wieck | 2015-09-15 13:25:28 | Re: [COMMITTERS] pgsql: Fix an O(N^2) problem in foreign key references. |