From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Large SGML Cleanup |
Date: | 2010-11-14 18:45:10 |
Message-ID: | AANLkTikG5A7Ma9yrDAn4xEVOkVzx1pBDUQyTAu-AAn0S@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
[Sorry, I'm revisiting this topic a bit late.. have had a lot of stuff
keeping me busy]
On Wed, Nov 3, 2010 at 10:24 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> In general, I think the more efficient way to address this overall
> problem is to run the resulting HTML through tidy and be done with it.
Running tidy -modify on the .html files in ./sgml/html/ gets the
number of invalid HTML files down to 4 from 224 [1]. I took a quick
look at a few of the resulting pages in Firefox, and couldn't see any
visual difference between the original and tidy'ed versions.
I think it would be a good idea to add a step in ./sgml/Makefile to
run tidy on all the .html files produced. Anyone interested in doing
this?
Josh
[1] For reference, the 4 remaining invalid files are: index.html,
functions-string.html, biblio.html, and ecpg-variables.html
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-14 19:46:29 | Re: Large SGML Cleanup |
Previous Message | Marti Raudsepp | 2010-11-14 10:23:59 | Re: [PATCH] Fix documentation about PL/Python exception handling |