Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ay7nR-0002IH-0c for pgsql-docs@arkaria.postgresql.org; Thu, 05 May 2016 01:09:41 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ay7nP-0007Yr-K7 for pgsql-docs@arkaria.postgresql.org; Thu, 05 May 2016 01:09:39 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ay7nO-0007Yh-3P for pgsql-docs@postgresql.org; Thu, 05 May 2016 01:09:38 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ay7nH-0005pT-1e for pgsql-docs@postgresql.org; Thu, 05 May 2016 01:09:36 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id E01DD20B0B for ; Wed, 4 May 2016 21:09:29 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 04 May 2016 21:09:29 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=S2wJkRbj6tHZ5kl eKJeIEbZ7J+k=; b=LQw7ZpTLEry1x5WWmxvxjgLX28wec5kVkzJwTM8n9b3Xax4 f6pnQv9kPr423a2WMtJexM49TKxomy27ntOSWpLUm0bOegYe7lb59DlstppcRnO/ k16r8zJDoexAfuVaerfo0B9OHLXeTuBI8VFyeYuiPkeaUo/eNYzzcGrPAK5c= X-Sasl-enc: fxqm5Yt0P/4q8Tqj/VunoAbgVpS+aPNq+R4Vb6tHoVeB 1462410569 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 400986800BA; Wed, 4 May 2016 21:09:29 -0400 (EDT) Subject: Re: Docbook 5.x To: Alexander Law , =?UTF-8?Q?J=c3=bcrgen_Purtz?= , pgsql-docs@postgresql.org References: <57179283.6080704@purtz.de> <20160503193441.GA61759@alvherre.pgsql> <572A0AD2.2070909@purtz.de> <572A1089.7030004@gmail.com> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <4f55ecfb-3aaf-4f1d-7364-05f9153c7526@2ndquadrant.com> Date: Wed, 4 May 2016 21:09:28 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <572A1089.7030004@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 5/4/16 11:08 AM, Alexander Law wrote: > As was stated in the aforementioned thread, solution 2 can be much (8x) > faster with some xslt optimizations, but I think now we should outline > some roadmap before we start to prepare patches and so. > Maybe we should convert to XML with DocBook4 at first step? > Then, once we get everything stabilized, we can upgrade to DocBook5. > Shouldn't we decompose the conversion procedure, so we could perform > fully automatic conversion without any manual changes, and then fix > non-valid situations, you described before? I think the process should be something like this: - Apply your XSLT performance patch. The patch should be submitted to the next commit fest. - Wait a while to make sure everyone is happy with the performance. Keep tweaking if necessary. - Port all DSSSL customizations to XSLT. Manually evaluate output for quality. - Switch to XSLT build for official HTML documentation. [milestone 1] - Convert sources to XML. (There could be substeps here.) [milestone 2] - Then consider upgrading to DocBook 5. [milestone 3] -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs