Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1axypc-0005kb-TW for pgsql-docs@arkaria.postgresql.org; Wed, 04 May 2016 15:35:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1axypb-0006Pw-N9 for pgsql-docs@arkaria.postgresql.org; Wed, 04 May 2016 15:35:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1axypG-0005yK-CJ for pgsql-docs@postgresql.org; Wed, 04 May 2016 15:34:58 +0000 Received: from mail-lf0-x230.google.com ([2a00:1450:4010:c07::230]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1axypD-0002dY-Rs for pgsql-docs@postgresql.org; Wed, 04 May 2016 15:34:57 +0000 Received: by mail-lf0-x230.google.com with SMTP id u64so64734544lff.3 for ; Wed, 04 May 2016 08:34:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=F9S1O2uxSkyYD5+NUyjDaVVJPRkzHbEIjt4+VGQ5bqQ=; b=nz2ERChBlIfBOc7IMsi5ojwYthvBtlu9PHcvBfuAOO+n/TNbXkRniF+b+PSrZNoUwJ 7PPYGMn7ru2Rt32Dcbv6OcbyDbVzvVfjetx9MdhDqqUYt6dgl9lor5Vw+MiHcrPMGlyS KTv93aJq9SDfZ3PPPuOWyRvbkdlFAYC6CqMqPXrcuraOWnZAi1grGOX8ih55FsVISrza IBnht9eUN07fm8MvgsBoI081HeGQ/7C0QyQaDPP2h/GVJz0bPoUWKwM42bIjxgcmBdVg ZaWMvea9Y0GgdUPbJkp9OTWRz9ow6xZHHG8C6opG7JPrXLUZKm3J8qgP5vT9G+d+ltCU U5Xw== 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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=F9S1O2uxSkyYD5+NUyjDaVVJPRkzHbEIjt4+VGQ5bqQ=; b=CdY5HTHLZxR2Mc03wTNXTywZmDrjiVMWkf7FS2NeO12FhMspolUWwKQJ3wa1O1gVcN 9UfikdWZc6xvKnOapY94dUqzzDvGcaP37Srj7ep5Qw0BJJ6g23jV5q6fYviOx6RXwJNO E5W2Uacwp9+GxmgIG57W99nhLzJ67v9NVK38s7K2TRpo15TeDuWKQpH+ZrCkyB7vfAbh K4upvakMQNBoJPRm7hzOspoHS7tb7FB5rqfSzof1ttRdf2UUJAZjb757mbqAF4guAcSo 9hedM4oVodROaqbrh+LWeOObY42ZbSOaCURSIgPwOO19lIz6adM2AvEcM7vnRXhPAsO6 HtzA== X-Gm-Message-State: AOPr4FVt8ZprCqe8C2eZpkKm478w5AwmpEpBuLbdK2d5jFKs17Jajh/gmRiUAC/TPp3oPw== X-Received: by 10.25.163.15 with SMTP id m15mr4607788lfe.93.1462376095208; Wed, 04 May 2016 08:34:55 -0700 (PDT) Received: from [1.0.0.7] ([109.196.196.224]) by smtp.gmail.com with ESMTPSA id j2sm723704lfb.13.2016.05.04.08.34.53 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 May 2016 08:34:54 -0700 (PDT) Subject: Re: Docbook 5.x To: Alvaro Herrera References: <20160504152158.GA102030@alvherre.pgsql> Cc: =?UTF-8?Q?J=c3=bcrgen_Purtz?= , pgsql-docs@postgresql.org From: Alexander Law Message-ID: <572A169D.3000901@gmail.com> Date: Wed, 4 May 2016 18:34:53 +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: <20160504152158.GA102030@alvherre.pgsql> 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 Alvaro, 04.05.2016 18:21, Alvaro Herrera wrote: > Alexander Law wrote: >> Hello Jürgen, >> >> 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. > Can the Docbook5 build be sped up with similar hacks? > > If the stylesheet tweaks you did are universally useful, why not > contribute them back to upstream Docbook? I can't guarantee that these tweaks with work for all the DocBook documents, though I've made sure that the result is the same for the postgresql doc html's (as I stated in http://www.postgresql.org/message-id/562E061B.1090809@postgrespro.ru). > >> Maybe we should convert to XML with DocBook4 at first step? >> Then, once we get everything stabilized, we can upgrade to DocBook5. > Not sure there's much point in having an intermediate step in the > repository that makes the doc build so much slower. I'd rather go to > Docbook5 straight away. > >> 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 don't think so -- this means leaving a state in the repo in which the > docs don't actually build. > I mean we could build the docs just as we do it now (as DocBook4). So we can continue to use existing toolchain (and Makefile as it can generate html and pdf from XML), just change a format for now. -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs