Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Uppercase SGML entity declarations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Uppercase SGML entity declarations
Date: 2011-04-04 16:37:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docspgsql-hackers
Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it> writes:
> My intention was to start and change some simple documentation files in 
> order to make our conversion process from SGML to XML smoother, while 
> keeping the SGML compatibility of the original documentation intact. 

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?

			regards, tom lane

In response to


pgsql-docs by date

Next:From: Gabriele BartoliniDate: 2011-04-04 17:18:21
Subject: Re: [HACKERS] Uppercase SGML entity declarations
Previous:From: Gabriele BartoliniDate: 2011-04-04 16:23:57
Subject: Re: [HACKERS] Uppercase SGML entity declarations

pgsql-hackers by date

Next:From: Alexander KorotkovDate: 2011-04-04 16:38:24
Subject: Re: Proposal: q-gram GIN and GiST indexes
Previous:From: Jan-Erik LärkaDate: 2011-04-04 16:34:21
Subject: Non Win/*nix UTF-8 codepage not known to PostgreSQL developers?!

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group