From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Jürgen Purtz <juergen(at)purtz(dot)de> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Docbook 5.x |
Date: | 2016-05-04 18:20:43 |
Message-ID: | 20160504182043.GA117338@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Jürgen Purtz wrote:
> 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.
OK. Currently we have no non-ASCII chars in our source code, so this
would be without precedent, but I think all modern tools should cope.
The only pain point may be Tom Lane's mail client, which is unique in
still using us-ascii encoding.
> 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.
Hmm? I think we use these entities to generate text files that are
distributed in the tarball. How would we generate these files in the
Docbook5 XML world?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Law | 2016-05-04 19:04:59 | Re: Some minor error fixes |
Previous Message | Peter Eisentraut | 2016-05-04 18:11:59 | Re: Some minor error fixes |