Content-Type: multipart/alternative;
 boundary="------------8Vtf0dN1GN0Iox5LnBqUMcRy"
Message-ID: <3d846208-ff49-5a23-1684-a2e00a14496b@purtz.de>
Date: Tue, 27 Sep 2022 09:12:45 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Subject: Re: DocBook 5.2
Content-Language: en-US
To: pgsql-docs@lists.postgresql.org
References: <ae14eca5-f57c-2db2-42ce-258bab3c6806@purtz.de>
 <20220905111508.wzgmpbcarxizdnin@alvherre.pgsql>
 <YzIY/OCgljTdqOgX@momjian.us> <3524032.1664228552@sss.pgh.pa.us>
 <YzJfBb+79/gW0d5y@momjian.us>
From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= <juergen@purtz.de>
In-Reply-To: <YzJfBb+79/gW0d5y@momjian.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3d846208-ff49-5a23-1684-a2e00a14496b%40purtz.de>
Precedence: bulk

This is a multi-part message in MIME format.
--------------8Vtf0dN1GN0Iox5LnBqUMcRy
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

>> Yeah, I think we'd have to convert all the supported versions to
>> make this palatable.  If the conversion is sufficiently automated,
>> that might not be a big lift.  (If it's*not*  automated, I think
>> the change would never get off the ground even for HEAD, because
>> the docs are too much of a moving target.)
> +1

The process is totally automated. There are general steps which work for 
every DocBook 4.x book. And there are Postgres-specific steps 
(doRealModifictions.sh) which looks for individual patterns per file. 
This is the critical part. Currently it's tested only with HEAD. My 
expectation is, that it should work also for translations to other 
languages because the patterns contain only elements and attributes, no 
text. But if they run against older versions it's likely that we need 
some changes or additional patterns. I'm willing to work on this if a) 
there is a consensus in the community that the work should go on and b) 
someone helps me to resolve the reported unacceptable runtime problem 
during PDF generation.

--

J. Purtz

--------------8Vtf0dN1GN0Iox5LnBqUMcRy
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <blockquote type="cite" cite="mid:YzJfBb+79%2FgW0d5y@momjian.us">
      <blockquote type="cite" style="color: #007cff;">
        <pre class="moz-quote-pre" wrap="">Yeah, I think we'd have to convert all the supported versions to
make this palatable.  If the conversion is sufficiently automated,
that might not be a big lift.  (If it's <b class="moz-txt-star"><span class="moz-txt-tag">*</span>not<span class="moz-txt-tag">*</span></b> automated, I think
the change would never get off the ground even for HEAD, because
the docs are too much of a moving target.)
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">+1
</pre>
    </blockquote>
    <p>The process is totally automated. There are general steps which
      work for every DocBook 4.x book. And there are Postgres-specific
      steps (doRealModifictions.sh) which looks for individual patterns
      per file. This is the critical part. Currently it's tested only
      with HEAD. My expectation is, that it should work also for
      translations to other languages because the patterns contain only
      elements and attributes, no text. But if they run against older
      versions it's likely that we need some changes or additional
      patterns. I'm willing to work on this if a) there is a consensus
      in the community that the work should go on and b) someone helps
      me to resolve the reported unacceptable runtime problem during PDF
      generation.<br>
    </p>
    <p>--</p>
    <p>J. Purtz<br>
    </p>
  </body>
</html>

--------------8Vtf0dN1GN0Iox5LnBqUMcRy--