Subject: Re: Docbook 5.x
To: pgsql-docs@postgresql.org
References: <20160504171205.GA107908@alvherre.pgsql>
From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= <juergen@purtz.de>
Message-ID: <572A3A1F.4050407@purtz.de>
Date: Wed, 4 May 2016 20:06:23 +0200
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: <20160504171205.GA107908@alvherre.pgsql>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

Hello Alvaro,

yes, character entities respectively their values must be kept (what you 
have seen is an intermediate state). We will use utf-8, so every 
possible Unicode code point can be used directly. But we use not only 
character entities, there are also parameter entities and external 
entities. The external entities will be replaced by xi:XInclude. At last 
there are 4 parameter entities, to whom I actually have no solution: 
%standalone-ignore; %standalone-include; %include-index; 
%include-xslt-index; . But they should not be a show-stopper.

Jürgen Purtz


On 04.05.2016 19:12, Alvaro Herrera wrote:
> 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
> &mdash; to __mdash__ and such.  That's not acceptable.  What is
> Docbook5's accepted way to enter such characters?
>


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs