X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0A713DB585; Tue, 15 Nov 2005 07:42:21 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 19819-04; Tue, 15 Nov 2005 11:42:22 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [151.155.5.143]) by svr1.postgresql.org (Postfix) with ESMTP id 4E950DACDE; Tue, 15 Nov 2005 07:42:18 -0400 (AST) Received: from [172.16.1.187] grzm [61.197.227.146] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 1.6 $ on Linux via secured & encrypted transport (TLS); Tue, 15 Nov 2005 04:42:18 -0700 In-Reply-To: <20051115112341.GC25699@surnet.cl> References: <18400.1131720229@sss.pgh.pa.us> <200511150513.jAF5D1e13382@candle.pha.pa.us> <20051115112341.GC25699@surnet.cl> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <46AFC43E-9D5C-4AEF-918B-D0C24D8E9224@myrealbox.com> Cc: Bruce Momjian , Tom Lane , Kris Jurka , David Fetter , pgsql-www@postgresql.org, pgsql-docs@postgresql.org Content-Transfer-Encoding: 7bit From: Michael Glaesemann Subject: Re: [DOCS] 8.1 PDF Documentation. Date: Tue, 15 Nov 2005 20:42:18 +0900 To: Alvaro Herrera X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.19 required=5 tests=[AWL=0.190] X-Spam-Score: 0.19 X-Spam-Level: X-Archive-Number: 200511/93 X-Sequence-Number: 8808 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