Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ayBJb-0005Vp-VB for pgsql-docs@arkaria.postgresql.org; Thu, 05 May 2016 04:55:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ayBJb-0003NJ-6x for pgsql-docs@arkaria.postgresql.org; Thu, 05 May 2016 04:55:07 +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 1ayBJa-0003Mn-MR for pgsql-docs@postgresql.org; Thu, 05 May 2016 04:55:06 +0000 Received: from mail-lf0-x242.google.com ([2a00:1450:4010:c07::242]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ayBJY-0002Br-5r for pgsql-docs@postgresql.org; Thu, 05 May 2016 04:55:05 +0000 Received: by mail-lf0-x242.google.com with SMTP id p64so9385175lfg.0 for ; Wed, 04 May 2016 21:55:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=iQjtyYcqA9bodPwyQxdMsebNdhXuU+HcFCnqC9Eb5H0=; b=I3+6K/KDjs0St9cd51SmaJ+UbTHFwnHn75btp/irdo8VngOFHu9hJMdL4eKHxmBDWh aQWu5/MOSeWCyCL5w98c/NZEEn/qRu5fNu6PNhILSWJj1dQG/fX0VmtCIwBAjHZDASCH 2TvqYumGFIPWj4gKYC3btaLmdulB/c77Dl2ZnesoF+tWokrdV25ECsRbdAYoZKjrH8kx rJC4oaFlKdG1XirjYNKKSxku3/W4VOKwuZd7ibL9KXJZtBZtLsWQTg5FGa3vzVTf+xJG pZKq7E+rAmLavmHI3g9AEKlL/Ijifo/z7rfd9Tb2lcezTrsHNNMVgPCGpfTwexOGiyyh CcaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=iQjtyYcqA9bodPwyQxdMsebNdhXuU+HcFCnqC9Eb5H0=; b=lbnMUCklioNDWKBK2Mh5PItuoZZYwTVfvtPVAYOrXkOLR0lqDsRO6PzFSn84Ys6HXg wQhf4MUKs1AzfxmfCAVWkeTw2bLDduSiGcSTHFRrkjOry7eb7AXbyh1L0iAfyiMMpE84 DwwRN5Cb5PndQaetYQPV5Zx62z2nY2iEazj2dE7VsXmW1z7tHgJU9U2q1tTF00stC9q4 rI3aRYPj/W/UE6HFkErBfrM9IC4pyFDenLLlnyliSazzfu/K4hQRUuBc2rjtwFJq1aVX 1aX0aOe4xNd1cHALCORQ+NphcreJ1WSXMH7MtJnuZdRt6vVlARlh1suox2aQPf+ZENN+ vb9A== X-Gm-Message-State: AOPr4FVo0Xxb4pnBirRpYhWA0nlvqB6yd/SNmHouBg2W2fiA9J3wgW2O3nKMWIqzaNJReQ== X-Received: by 10.112.198.169 with SMTP id jd9mr5087329lbc.94.1462424102256; Wed, 04 May 2016 21:55:02 -0700 (PDT) Received: from [1.0.0.7] ([109.196.196.224]) by smtp.gmail.com with ESMTPSA id ku5sm1199531lbc.11.2016.05.04.21.55.01 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 May 2016 21:55:01 -0700 (PDT) Subject: Re: Docbook 5.x To: Peter Eisentraut , =?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> <4f55ecfb-3aaf-4f1d-7364-05f9153c7526@2ndquadrant.com> From: Alexander Law Message-ID: <572AD224.5070307@gmail.com> Date: Thu, 5 May 2016 07:55:00 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <4f55ecfb-3aaf-4f1d-7364-05f9153c7526@2ndquadrant.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) 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 Hello Peter, I fully support your plan and going to move this way. Best regards, Alexander 05.05.2016 04:09, Peter Eisentraut пишет: > 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] > -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs