Re: [DOCS] Uppercase SGML entity declarations - Mailing list pgsql-hackers

From Susanne Ebrecht
Subject Re: [DOCS] Uppercase SGML entity declarations
Date
Msg-id 4D99FF55.9070301@2ndQuadrant.com
Whole thread Raw
In response to Re: [DOCS] Uppercase SGML entity declarations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [DOCS] Uppercase SGML entity declarations  (Robert Haas <robertmhaas@gmail.com>)
Re: [DOCS] Uppercase SGML entity declarations  (Christopher Browne <cbbrowne@gmail.com>)
Re: [DOCS] Uppercase SGML entity declarations  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On 04.04.2011 18:37, Tom Lane wrote:
> AFAIK, the main stumbling block for that is that XML doesn't allow
> abbreviated close tags (ie,<foo>whatever</>).  Which is something that
> we are not likely to give up.  So I'm not sure of the point of changing
> something as trivial as entity declaration casing.  You're going to end
> up having to fork the documentation anyway, or at least feed it through
> an SGML to XML converter.  So why not fix the entity casing then?

Tom,

Honestly, for German I don't mind yet if it is XML or SGML. XML might
be better in future for maintenance tools.

Anyway, I figured out there is another argument for XML:

My information is that DocBook 5.0 won't support SGML anymore.

Which means - sooner or later a reaction is needed.

Susanne
P.S.:
Btw. I change <foo>whatever</> into <foo>whatever</foo> when it
is in the parts which I am translating because my emacs indent don't
like </>.

--
Susanne Ebrecht - 2ndQuadrant
PostgreSQL Development, 24x7 Support, Training and Services
www.2ndQuadrant.com


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [sepgsql] missing checks of process:transition on trusted procedure invocation
Next
From: Robert Haas
Date:
Subject: Re: [DOCS] Uppercase SGML entity declarations