From: Alvaro Herrera <alvherre@commandprompt.com>
To: Josh Kupershmidt <schmiddy@gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Large SGML Cleanup
Date: Wed, 03 Nov 2010 10:14:47 -0300
Message-ID: <1288788816-sup-8169@alvh.no-ip.org> (raw)
In-Reply-To: <AANLkTi=1Sm9N3Khiued9UiMfdd_TKLimMiO9mCfHtL39@mail.gmail.com>
References: <AANLkTi=1Sm9N3Khiued9UiMfdd_TKLimMiO9mCfHtL39@mail.gmail.com>
Excerpts from Josh Kupershmidt's message of mar nov 02 23:56:26 -0300 2010:
> [Resending without large attachment, looks like the previous attempt
> isn't going to make it]
>
> Hi all,
>
> I've gone through the SGML documentation, trying to push the output
> HTML towards HTML 4.01 compliance. By far the most common problem I
> found was incorrect nesting of <para> nodes, which results in invalid
> HTML.
I wonder if you're going to get stuck at some point due to invalid HTML
being output by the toolchain that cannot be fixed. For example, there
are <A> elements inside other <A> elements in history.html. How would
you fix that? There's also a systematic problem in bookindex.html
which is a generated file.
I wonder if it would be better to see about switching the toolchain. We
discussed jumping to XML; this was rejected in the past for no bigger
reason that not wanting to have to rename the files from .sgml to .xml.
Now that we're in Git, that's no longer a problem. If we can switch to
a better toolchain for producing the HTML, maybe these problems would go
away. (Of course, to be able to switch to XML we'd need to change a few
habits that no longer work such as using </> as closing tag).
Of course, switching to XML is going to meet a lot more resistance than
just committing these simple fixes to the SGML source.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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: pgsql-docs@postgresql.org
Cc: alvherre@commandprompt.com, schmiddy@gmail.com
Subject: Re: Large SGML Cleanup
In-Reply-To: <1288788816-sup-8169@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox