public inbox for [email protected]  

help / color / mirror / Atom feed

From: Michael Glaesemann <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Kris Jurka <[email protected]>
Cc: David Fetter <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: [DOCS] 8.1 PDF Documentation.
Date: Tue, 15 Nov 2005 20:42:18 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>


On Nov 15, 2005, at 20:23 , Alvaro Herrera wrote:

> Bruce Momjian wrote:
>
>> I am still unclear why there is no more reliable SGML toolchain  
>> for PDF
>> output after all these years.  Seems things have improved because  
>> we now
>> have bookmarks, but still, why is this functionality not more  
>> mainstream.
>
> There is no SGML toolchain because SGML has been abandoned as the
> DocBook markup language.  The toolchain that everybody else uses is
> based on XML DocBook.  It has been proposed that we abandon SGML and
> jump to XML, but the idea has been shot down.  And it's possible to
> convert our SGML to XML automatically and process it with the newer
> toolchain.

It's my understanding that it hasn't been shot down as much as no one  
has shown that it will serve our needs. IIRC, there are two issues:

> Marked sections: SGML DocBook (which is currently used) supports  
> parameter entities to be used to include or exclude certain  
> sections of material depending on the desired output. Profiling in  
> XML DocBook may be able to accomplish the same task.
>
> XML DocBook toolchain: making sure the tools to produce the  
> documentation in its myriad forms (e.g., html, manpages, PDF) works.

(Just for history repeating itself, this was brought up Aug 2004 as  
well :) )

I don't think anyone's standing in the way. It's just that no one's  
shown that the XML toolchain can do the work for us.

Michael Glaesemann
grzm myrealbox com

view thread (18+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [DOCS] 8.1 PDF Documentation.
  In-Reply-To: <[email protected]>

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

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