It was. But if the compromise is single file html, that is a vast
improvement over the current system imho.
What I want is the thing that is maximally amenable to being searched
conveniently using all the tools at our disposal especially regular
expressons. The point has been made that Google is the best system to
search for Postgres documentation/knowledge/etc. Frankly, I don't
necessarily agree with that, particularly for the novice. The
documentation is where it is at, and it is the documentation that is
referenced the most in these posts.
But there are no dichotomies here. It is not either or. It is a
balance between what is easiest to produce and maintain and what is
most productive to use.
And the background for my request is my respect for the extraordinary
power and elegance of postgres.
John
On Jun 12, 2010, at 3:10 PM, Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
>> On lör, 2010-06-12 at 11:18 +0200, John Gage wrote:
>>> A one file html version would be a godsend.
>
>> I've committed a build target for that now. Use 'make
>> postgres.html' in
>> doc/src/sgml/.
>
> Huh, is that actually worth anything? How many browsers will open it
> without crashing, or will navigate the page with decent performance
> if they do manage to open it?
>
> (Not that I object to providing this Make target. But I thought the
> discussion was about plain-text output.)
>
> regards, tom lane
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general