MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="=_9ba1e3905cc64537bc376f994e21b528"
Date: Sat, 02 Mar 2024 20:28:31 +0000
From: Jimmy Angelakos <vyruss@hellug.gr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Erik Wienhold <ewie@ewie.name>, Marcos Pegoraro <marcos@f10.com.br>,
        pgsql-www@postgresql.org
Subject: Re: Diff of this page with other version
Organization: Hellenic Linux User Group
In-Reply-To: <3129677.1709400823@sss.pgh.pa.us>
References: 
 <CAB-JLwYmR+sW9spQQMjnLT0hbAR_3qTCqqJgt-sC3=NgCSJyRg@mail.gmail.com>
 <w57oncn7cptrcah6kgbn5gdkqfmo3nihsrb2bvcbgpfwpkeixl@dqqdc5f7i5p5>
 <3129677.1709400823@sss.pgh.pa.us>
Message-ID: <eda40c8d77cf81e098a62ecbca745782@hellug.gr>
User-Agent: Roundcube Webmail/1.3.17
Archived-At: 
 <https://www.postgresql.org/message-id/eda40c8d77cf81e098a62ecbca745782%40hellug.gr>
Precedence: bulk

--=_9ba1e3905cc64537bc376f994e21b528
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

On 02/03/2024 17:33, Tom Lane wrote:

> Erik Wienhold <ewie@ewie.name> writes: 
> 
>> I think you underestimate the effort because the changes are not always
>> as clear (adding one line) as for copy.sgml as you've shown above.  For
>> example, if I check create_table.sgml between v15 and v16, I see that
>> the addition of STORAGE modified an existing line.  So that regex has to
>> match and wrap just the relevant substring.  When new storage modes are
>> added we end up with nested version info in order to compare vXX with
>> pre v16:
> 
> Yeah.  I think the chances of getting people to do this in the .sgml
> files are precisely zero.  What might have a chance of happening is
> to provide a way on the website of running htmldiff or similar tool
> over two versions of a doc page on-the-fly and show the results.
> 
> regards, tom lane

I agree with Tom, I think automation of this process is the way to go
here. 

Best regards,
Jimmy
--=_9ba1e3905cc64537bc376f994e21b528
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p>On 02/03/2024 17:33, Tom Lane wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ig=
nored -->
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
Erik Wienhold &lt;<a href=3D"mailto:ewie@ewie.name">ewie@ewie.name</a>&gt; =
writes:
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">I think you underestimate the effort because the chang=
es are not always<br /> as clear (adding one line) as for copy.sgml as you'=
ve shown above. &nbsp;For<br /> example, if I check create_table.sgml betwe=
en v15 and v16, I see that<br /> the addition of STORAGE modified an existi=
ng line. &nbsp;So that regex has to<br /> match and wrap just the relevant =
substring. &nbsp;When new storage modes are<br /> added we end up with nest=
ed version info in order to compare vXX with<br /> pre v16:</blockquote>
<br /> Yeah. &nbsp;I think the chances of getting people to do this in the =
=2Esgml<br /> files are precisely zero. &nbsp;What might have a chance of h=
appening is<br /> to provide a way on the website of running htmldiff or si=
milar tool<br /> over two versions of a doc page on-the-fly and show the re=
sults.<br /> <br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;regards, tom lane</div>
</blockquote>
<p>I agree with Tom, I think automation of this process is the way to go he=
re.</p>
<p>Best regards,<br />Jimmy</p>

</body></html>

--=_9ba1e3905cc64537bc376f994e21b528--