Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e4nHn-0006dN-7C for pgsql-docs@arkaria.postgresql.org; Wed, 18 Oct 2017 12:17:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e4nHl-0003ql-FQ for pgsql-docs@arkaria.postgresql.org; Wed, 18 Oct 2017 12:17:21 +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 1e4nHk-0003qK-Ru for pgsql-docs@postgresql.org; Wed, 18 Oct 2017 12:17:21 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e4nHf-0002YP-8c for pgsql-docs@postgresql.org; Wed, 18 Oct 2017 12:17:20 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E557E21141; Wed, 18 Oct 2017 08:17:12 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 18 Oct 2017 08:17:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=lJa87a Qbwf2aTixwrBujsiKlawv6HL7hyUIgw+Hc2ig=; b=TVYyfbK+vIZYUBUYHQWH2x jIgHyA4psWcFuMfQSu2g51WvX+GPQHH6GWya8WQRBtIEakoPr9PYolCJKnn3IVkZ alLlgqge4Tofr9VWMPiMj1Bo/80SnhvktKYabKsHNJUWDaC/12VG3gnJ4/R2Zt/Q Q3jrH7qvtIwErcTC4mKsSrqD4S3L0kX1Y/VIRsCQeDwT1bi+XGxqEXLs6WmsBVGi d+WM6pjoBwlqhtOuk5anA5/gKmmqu5jRzmbLdZAvodPw0tmBeyW96r1NOkRpvxg4 Fw8JrWiGYz1V9s6VHoBUthmAFXzQgap+o8hRtTuHM1E2BCgN1bppq/JE1YrmBS3Q == X-ME-Sender: 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 9E9F07F961; Wed, 18 Oct 2017 08:17:12 -0400 (EDT) Subject: Re: no more SGML empty tags To: Tatsuo Ishii References: <6d137bd0-eef6-1d91-d9b8-1a5e9195a899@2ndquadrant.com> <20171018.090908.1654875320266791258.t-ishii@sraoss.co.jp> Cc: pgsql-docs@postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 18 Oct 2017 08:17:08 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171018.090908.1654875320266791258.t-ishii@sraoss.co.jp> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 10/17/17 20:09, Tatsuo Ishii wrote: >> In XML, empty tags such as are no longer allowed. In preparation >> for converting the documentation to DocBook XML, I have committed a >> patch that expands all such empty tags. There is also now a warning >> from onsgmls when empty tags are used. (There is no -werror option, >> unfortunately.) > > Just out of curiosity, did you do the work (expanding the empty tags) > manually or using some tools? We are using SGML DocBook in the > Pgpool-II project and a little bit annoyed by the empty tags (for > example emacs auto indentation does not work with empty tags). I used the tools provided in the "Docbook 5.x" thread, in particular the sgml2xml.pl script. I think you should be able to use that for your documentation as well. -- 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