Re: Diff of this page with other version

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Euler Taveira" <euler(at)eulerto(dot)com>
Cc: "Daniel Gustafsson" <daniel(at)yesql(dot)se>, "Marcos Pegoraro" <marcos(at)f10(dot)com(dot)br>, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-www(at)postgresql(dot)org
Subject: Re: Diff of this page with other version
Date: 2024-03-04 15:12:32
Message-ID: 3597695.1709565152@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

"Euler Taveira" <euler(at)eulerto(dot)com> writes:
> There is also tools like pgPedia [1] that provides a command / function
> history. Unless there is a way to automate this request as Alvaro said, it
> would impose extra work by adding tags to mark that a feature adds a keyword
> and/or value. What happen if a deprecated keyword / value was removed? The
> synopsis content can be rearranged too. I have a gut feeling that some work
> should be done manually.

There's no doubt that we could get *better* results with the addition
of manual effort. But even htmldiff as it stands today produces
*usable* results (I tried it on a couple of versions of the COPY
reference page). Given that we've not offered something like this
at all before, I think it's silly to put in a lot of up-front effort
in advance of seeing what the demand really is.

In any case, I concur with the other committers that there is simply
no way we're going to accept manual change markup as an additional
expectation for documentation commits. It's hard enough already.

regards, tom lane

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Marcos Pegoraro 2024-03-04 17:06:22 Re: Diff of this page with other version
Previous Message Euler Taveira 2024-03-04 14:45:38 Re: Diff of this page with other version