public inbox for [email protected]  

help / color / mirror / Atom feed

From: Susanne Ebrecht <[email protected]>
To: Tom Lane <[email protected]>
Cc: Gabriele Bartolini <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: [email protected]
Cc: PostgreSQL-development <[email protected]>
Subject: Re: [HACKERS] Uppercase SGML entity declarations
Date: Mon, 04 Apr 2011 19:26:45 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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

view thread (29+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] Uppercase SGML entity declarations
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox