Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ay0LQ-0002gq-KF for pgsql-docs@arkaria.postgresql.org; Wed, 04 May 2016 17:12:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ay0LQ-0005DK-1S for pgsql-docs@arkaria.postgresql.org; Wed, 04 May 2016 17:12:16 +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 1ay0LP-0005B1-5P for pgsql-docs@postgresql.org; Wed, 04 May 2016 17:12:15 +0000 Received: from out.smtp-auth.no-ip.com ([8.23.224.60]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ay0LM-0004Co-Da for pgsql-docs@postgresql.org; Wed, 04 May 2016 17:12:14 +0000 X-No-IP: alvh.no-ip.org@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from alvin.alvh.no-ip.org (unknown [216.155.90.98]) (Authenticated sender: alvh.no-ip.org@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 6C4B3400624; Wed, 4 May 2016 10:12:07 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id BAAC1438; Wed, 4 May 2016 14:12:05 -0300 (CLST) Date: Wed, 4 May 2016 14:12:05 -0300 From: Alvaro Herrera To: =?iso-8859-1?Q?J=FCrgen?= Purtz Cc: pgsql-docs@postgresql.org Subject: Re: Docbook 5.x Message-ID: <20160504171205.GA107908@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <572A28D4.6060702@purtz.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -1.1 (-) 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 Jürgen Purtz wrote: > The real challenge is the second > step as it implies some manual modifications (entities, non-valid markup in > sense of db5-schema) and a switch to a different output chain. Maybe we can > live for a while with some files, which are not valid against db5-schema - > as far as the output chain produces correct results. Speaking of entities, I noticed you changed some entities such as — to __mdash__ and such. That's not acceptable. What is Docbook5's accepted way to enter such characters? -- Álvaro Herrera 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