Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bk8D3-0004mq-Oa for pgsql-docs@arkaria.postgresql.org; Wed, 14 Sep 2016 11:18:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bk8D3-0001BG-7e for pgsql-docs@arkaria.postgresql.org; Wed, 14 Sep 2016 11:18:33 +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 1bk8D2-0001AX-6U for pgsql-docs@postgresql.org; Wed, 14 Sep 2016 11:18:32 +0000 Received: from mail-lf0-x234.google.com ([2a00:1450:4010:c07::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bk8Cy-0005Mk-J7 for pgsql-docs@postgresql.org; Wed, 14 Sep 2016 11:18:30 +0000 Received: by mail-lf0-x234.google.com with SMTP id l131so7484777lfl.2 for ; Wed, 14 Sep 2016 04:18:28 -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=F0haBloL3mNRd6RF9deU+UodwuR2xVKN0JWV77/aq24=; b=y7qSRNSLojz+52tnH9PSgA0B5HJ4ueTRG7fBoSjgnF6wrTTtFCVklj56mI7y7CQ/wY ZtOrKnDWPhgyQLJbx0/cHOXXoMUx1AGOJvjpoGDpJN9wPfNANwgC8F1BEZJT0RK4YAf5 gwygE9PYT19fZl4DlkOJvDirtoKk5I1a4rXOngDLWlvYKZAjotHO3uG0yilcilyDgJHK gogog9HoVAZweGnIAKEIXO1IQIwksw9bFtEO1ow06V8+1g1kuzVoMc293dci37YMIzOo 4UTtbm1XYDNR14aVNhn7/K3eGmdc5YfB6CKWeyovuP28gvYD+pV6zsSG4fqzZeVaqIo8 lP1w== 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=F0haBloL3mNRd6RF9deU+UodwuR2xVKN0JWV77/aq24=; b=WTCsEA8alYu+b/AgHGBsjsiBywQ+nQKAIWInuuScZ72Sz1uhO/Utq2WD/+s0qsHRB7 oS6Ixx0NvaLevxdWx6utCcsBI9j+L2OIL/HO7hEksyN8RkCvuzUm3V7s6dibHS3n1omN ySZjuYSx5u5YYSKb4CI1s2kS+Twf6tCIZj2PgQaFzro6+r9uqct9QpmCaRtLcA35kc2y 5Fof39cNLQdohzJBZhHx+miguTkQDbmxI3XiJw2U/Gtbw92cthMtJeDWpx955TZPXOMH UJ/GEIwiNpiUKqscBgDfmoTTNGXHI28Ui7p3qAeZYRYv90ZK9W4mvgHuOQ7YIoIgY0v7 4E1A== X-Gm-Message-State: AE9vXwMEFQaIg1ty80C2y5wy/Wn1G2JN7GzSo/LtwV8zAWL0AizSh6eAXCFc6B2nKOjL1w== X-Received: by 10.25.20.80 with SMTP id k77mr820783lfi.112.1473851906521; Wed, 14 Sep 2016 04:18:26 -0700 (PDT) Received: from [1.0.0.7] ([109.196.196.203]) by smtp.gmail.com with ESMTPSA id f9sm2439572lji.19.2016.09.14.04.18.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Sep 2016 04:18:25 -0700 (PDT) Subject: Re: Docbook 5.x To: Peter Eisentraut , obartunov@gmail.com, Alvaro Herrera , Alexander Lakhin References: <57179283.6080704@purtz.de> <20160503193441.GA61759@alvherre.pgsql> <572AD007.60900@gmail.com> <5752E599.2090505@gmail.com> <576d0623-a89c-b3de-e321-dc48a579ff1a@2ndquadrant.com> <4adecfc6-2f2e-2ff2-bfa3-58b7d397227b@gmail.com> Cc: =?UTF-8?Q?J=c3=bcrgen_Purtz?= , pgsql-docs@postgresql.org From: Alexander Law Message-ID: Date: Wed, 14 Sep 2016 14:18:24 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <4adecfc6-2f2e-2ff2-bfa3-58b7d397227b@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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. >>> Should we now compare DSSSL outputs with XSLT? >>> I had some success with it before. See my letter: >>> https://www.postgresql.org/message-id/57712848.7060306%40gmail.com >>> Those xslt's (see xhtml-like-dsssl.patch) can help us to see all the >>> differences and to decide which customizations to keep. >> It looks like the idea there is to whack the XSLT stylesheets until the >> output looks exactly like the DSSSL output? I'm not sure that's >> terribly useful. It would probably be a lot of work, which we'll just >> end up removing eventually. I'd rather just fix any formatting issues >> we find and move forward. > That work is done already and it's results are countable and > observable differences. (See comments in the xslt.) > For example, with DSSSL we don't get a chapter TOC when the chapter > contains only one sect1 (with XSLT we get the TOC with the one item). > We also had subtoc for sect1/refentry and sect1/simplesect, but with > XSLT it's absent. > So if all such differences are not important, let's move forward. > Please look at the http://oc.postgrespro.ru/index.php/s/ttJyMDLr8Xr1HTu/download where I have gathered together all the significant differences, that we have between DSSSL and XSLT outputs. I have marked red the differences that I would consider as negative. Let's decide which ones are acceptable and which we need to eliminate. Best regards, Alexander -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs