From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Gabriele Bartolini <gabriele(dot)bartolini(at)2ndquadrant(dot)it> |
Cc: | 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 14:57:55 |
Message-ID: | BANLkTikwxtb9MU-Bn7XqCJSCEdEuJPL+Lg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Mon, Apr 4, 2011 at 5:11 AM, Gabriele Bartolini
<gabriele(dot)bartolini(at)2ndquadrant(dot)it> wrote:
> I have made very small modifications to a few files in the documentation
> directory, which involve SGML entity declarations. Currently they are all
> written lowercase, the patch makes them uppercase. This won't affect SGML
> parsing, as SGML is case insensitive - even though it is a good practice to
> write SGML declarations in uppercase.
>
> An example is:
>
> <!entity abort system "abort.sgml">
>
> written
>
> <!ENTITY abort SYSTEM "abort.sgml">
>
>
> This patch makes also every single directive of them XML compliant.
Forgive me for asking what may seem like a stupid question, but what's
not XML compliant about them now, and why do we care? The text is
only ever going to parse as SGML (not XML) so I guess I don't see why
it matters. I don't really object to the proposed patch but I guess
I'm not sure what it accomplishes.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-04 15:15:30 | Re: [HACKERS] Uppercase SGML entity declarations |
Previous Message | Robert Haas | 2011-04-04 14:54:01 | Re: [HACKERS] found a very confusing and maybe outdated sentence |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-04 14:58:16 | Re: cast from integer to money |
Previous Message | Robert Haas | 2011-04-04 14:56:07 | Re: Proposal: q-gram GIN and GiST indexes |