X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id E126230EEBA for ; Mon, 16 Jun 2003 15:16:42 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 41630-04 for ; Mon, 16 Jun 2003 12:16:32 -0300 (ADT) Received: from mailav.tor1.inquent.com (mail.inquent.com [216.208.117.106]) by svr1.postgresql.org (Postfix) with ESMTP id 69ACB30EE82 for ; Mon, 16 Jun 2003 12:16:32 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mailav.tor1.inquent.com (Postfix) with ESMTP id 134D21024D; Mon, 16 Jun 2003 11:10:21 -0400 (EDT) Received: from [10.0.2.11] (unknown [10.0.2.11]) by mailav.tor1.inquent.com (Postfix) with ESMTP id 8F4A910248; Mon, 16 Jun 2003 11:10:18 -0400 (EDT) Subject: Re: DocBook V4.2 From: Rod Taylor To: Peter Eisentraut Cc: PostgreSQL Docs In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-KrXUweTEAPuUEdWHDd81" Message-Id: <1055776603.92447.20.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 16 Jun 2003 15:16:44 +0000 X-Virus-Scanned: by AMaViS perl-11 X-Archive-Number: 200306/34 X-Sequence-Number: 1820 --=-KrXUweTEAPuUEdWHDd81 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > We are now beginning to run into trouble with the established toolchain > (particularly for print output), and there isn't much new development > happening, so I'd like to start trying out XML-based toolchains. To do > that, we need to move to a DocBook version that is available as both SGML > (processed by OpenJade) and XML, which is the case for 4.x. We can > convert SGML to XML automatically, so there are no syntax implications. I've had good luck processing XML through both toolchains, and would find it VERY useful if there was the ability to quickly pull in PostgreSQL content into other in-house documents via an XMLInclude rather than a hacked checkout, file munge, etc. I vote for having valid XML in the system itself with each file having a valid DTD specification. This has the added benefit of allowing an XSL transform to function on a single document fairly easily which enables people such as Josh who don't normally write documentation to quickly validate their changes with nothing but a webbrowser, a very short set of instructions, and the URL to the docbook XSLs. --=20 Rod Taylor PGP Key: http://www.rbt.ca/rbtpub.asc --=-KrXUweTEAPuUEdWHDd81 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA+7d9b6DETLow6vwwRAu2vAJ9x1iZukThGs/TehG16l5IouzjA8wCfRGoN xHsy9NLVm6hkJ7Djw33zNsk= =2SBh -----END PGP SIGNATURE----- --=-KrXUweTEAPuUEdWHDd81--