force use of pandoc version >= 3.1.12.2

The `bin/pandoc-wrapper.sh` tool will verify that the ssytem
has a recent enough version of `pandoc(1)`.

We explain why we insist on `pandoc(1)`. version >= 3.1.12.2
in comments where the $PANDOC_MIN_VERSION is set.

Added `--wrap=preserve` as a default argument to `pandoc(1)`.
While this change will impact every HTML file generated,
we believe this will improve the ability of someone to look
at the generated HTML and correlate with the original markdown.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.4.2 2024-03-17"
to "1.4.3 2024-03-18".

Performed `make www` to achieve all of the above and to generate
HTML using the new  `--wrap=preserve` `pandoc(1)` mode.

1993/vanb/index.html

@@ -129,9 +129,9 @@
 
 <h2 id="author"><a name="author"></a>Author:</h2>
 <ul>
-<li>Name: <a href="../../authors.html#David_Van_Brackle">David Van
-Brackle</a><br> Location: <a href="../../location.html#ZZ">ZZ</a> -
-<em>Unknown location</em> <br><br></li>
+<li>Name: <a href="../../authors.html#David_Van_Brackle">David Van Brackle</a><br>
+Location: <a href="../../location.html#ZZ">ZZ</a> - <em>Unknown location</em>
+<br><br></li>
 </ul>
 
 <!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -144,12 +144,11 @@ Brackle</a><br> Location: <a href="../../location.html#ZZ">ZZ</a> -
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
 <p>The current status of this entry is:</p>
 <pre><code>STATUS: INABIAF - please **DO NOT** fix</code></pre>
-<p>For more detailed information see <a
-href="../../bugs.html#1993_vanb">1993 vanb bugs</a>.</p>
+<p>For more detailed information see <a href="../../bugs.html#1993_vanb">1993 vanb bugs</a>.</p>
 <h2 id="to-use">To use:</h2>
 <div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./vanb</span> <span class="st">&#39;exp&#39;</span></span></code></pre></div>
-<p>where <code>exp</code> is an octal expression. See below for how it
-can also have hexadecimal and decimal numbers.</p>
+<p>where <code>exp</code> is an octal expression. See below for how it can also have
+hexadecimal and decimal numbers.</p>
 <h2 id="try">Try:</h2>
 <div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.sh</span></span></code></pre></div>
 <p>What happens if you use something other than valid digits?</p>
@@ -163,46 +162,37 @@ octal numbers:      octal digits
 grouping:       ()</code></pre>
 <p>No spaces are allowed in the expression. To avoid shell expansion,
 one should surround the expression in single quotes.</p>
-<p>It is a good thing that this program consists of only one expression,
-otherwise it might become hard to understand. :-)</p>
+<p>It is a good thing that this program consists of only one
+expression, otherwise it might become hard to understand. :-)</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>The program does no error checking - erroneous expressions will
-produce spurious results. Note that unary <code>-</code> is an operator.
-Thus, decimal <code>-46</code> would be entered as <code>-d46</code> and
-not <code>d-46</code>.</p>
-<h3 id="what-makes-this-program-special">What Makes This Program
-Special:</h3>
+produce spurious results. Note that unary <code>-</code> is an operator. Thus,
+decimal <code>-46</code> would be entered as <code>-d46</code> and not <code>d-46</code>.</p>
+<h3 id="what-makes-this-program-special">What Makes This Program Special:</h3>
 <ol start="0" type="1">
-<li><p>Of course, the fact that the program takes input and produces
-output in octal, rather than a more useful system like decimal, makes it
-“special”.</p></li>
-<li><p>The entire program consists of a single expression, returned from
-<code>main()</code>.</p></li>
-<li><p>There are no global or local variables other than the parameters
-to <code>main()</code>.</p></li>
-<li><p>All of the constants in the program are expressed in octal -
-including the <code>printf(3)</code> string.</p></li>
-<li><p>The variables are given names which cause visual confusion with
-the octal constants.</p></li>
-<li><p>The program is formatted like a Roman numeral 8. The significance
-of 8 is obvious. I chose Roman numerals because it is a numbering system
-even more arcane than octal. It’s not very ‘deceptive’, but it’s
-difficult to deceptively format a program which has no explicit control
-structures (other than <code>?:</code>s).</p></li>
-<li><p>Many simple tasks are done many times. I tried to do these
-differently each time, to make the program harder to
-understand.</p></li>
+<li><p>Of course, the fact that the program takes input and produces output in
+octal, rather than a more useful system like decimal, makes it “special”.</p></li>
+<li><p>The entire program consists of a single expression, returned from <code>main()</code>.</p></li>
+<li><p>There are no global or local variables other than the parameters to <code>main()</code>.</p></li>
+<li><p>All of the constants in the program are expressed in octal - including the
+<code>printf(3)</code> string.</p></li>
+<li><p>The variables are given names which cause visual confusion with the octal
+constants.</p></li>
+<li><p>The program is formatted like a Roman numeral 8. The significance of 8 is
+obvious. I chose Roman numerals because it is a numbering system even more
+arcane than octal. It’s not very ‘deceptive’, but it’s difficult to deceptively
+format a program which has no explicit control structures (other than <code>?:</code>s).</p></li>
+<li><p>Many simple tasks are done many times. I tried to do these differently each
+time, to make the program harder to understand.</p></li>
 </ol>
 <h3 id="how-it-works">How It Works:</h3>
-<p>It’s a recursive descent parser, calling <code>main()</code> for all
-of its recursion. <code>O2</code> is a state variable, telling
-<code>main()</code> what grammar non-terminal to parse.
-<code>**O7</code> is the next character. <code>O3</code> is an
-intermediate result. Whenever you see a construct like:</p>
+<p>It’s a recursive descent parser, calling <code>main()</code>
+for all of its recursion. <code>O2</code> is a state variable, telling <code>main()</code>
+what grammar non-terminal to parse. <code>**O7</code> is the next character.
+<code>O3</code> is an intermediate result. Whenever you see a construct like:</p>
 <pre><code>!(expression with O2)?</code></pre>
-<p>it’s decrementing and testing <code>O2</code> to see what state it’s
-in. Comparisons involving <code>**O7</code> and octal constants are
-looking for certain characters.</p>
+<p>it’s decrementing and testing <code>O2</code> to see what state it’s in. Comparisons
+involving <code>**O7</code> and octal constants are looking for certain characters.</p>
 <p>Here’s the grammar (<code>'e'</code> denotes the empty string) :</p>
 <pre><code>&lt;E&gt;  ::=  &lt;T&gt;&lt;E&#39;&gt;
 &lt;E&#39;&gt; ::=  +&lt;T&gt;&lt;E&#39;&gt; | -&lt;T&gt;&lt;E&#39;&gt; | e
@@ -223,9 +213,9 @@ looking for certain characters.</p>
 &lt;D&gt;  is   04
 &lt;X&gt;  is   05
 &lt;O&gt;  is   03</code></pre>
-<p>Here’s a version of the program before it got formatted into the
-VIII, augmented with comments showing where each state begins.
-<code>N1</code> and <code>N2</code> are notes:</p>
+<p>Here’s a version of the program before it got formatted into the VIII,
+augmented with comments showing where each state begins. <code>N1</code> and <code>N2</code> are
+notes:</p>
 <div class="sourceCode" id="cb9"><pre class="sourceCode c"><code class="sourceCode c"><span id="cb9-1"><a href="#cb9-1" aria-hidden="true" tabindex="-1"></a><span class="pp">#define O5 main</span></span>
 <span id="cb9-2"><a href="#cb9-2" aria-hidden="true" tabindex="-1"></a>O5<span class="op">(</span>O2<span class="op">,</span>O7<span class="op">,</span>O3<span class="op">)</span><span class="dt">char</span><span class="op">**</span>O7<span class="op">;</span></span>
 <span id="cb9-3"><a href="#cb9-3" aria-hidden="true" tabindex="-1"></a><span class="op">{</span></span>
@@ -261,13 +251,11 @@ VIII, augmented with comments showing where each state begins.
 <span id="cb9-33"><a href="#cb9-33" aria-hidden="true" tabindex="-1"></a>          O5<span class="op">(</span><span class="bn">011</span><span class="op">,</span>O7<span class="op">,</span>O5<span class="op">(</span><span class="bn">010</span><span class="op">,</span>O7<span class="op">,</span><span class="bn">00</span><span class="op">)):</span></span>
 <span id="cb9-34"><a href="#cb9-34" aria-hidden="true" tabindex="-1"></a><span class="co">/* C  */</span> <span class="op">(++*</span>O7<span class="op">,</span>O3<span class="op">);</span></span>
 <span id="cb9-35"><a href="#cb9-35" aria-hidden="true" tabindex="-1"></a><span class="op">}</span></span></code></pre></div>
-<p>Note <code>N1</code>: It should never enter this state, unless the
-user invokes the program with no parameters, in which case it just
-returns 0.</p>
-<p>Note <code>N2</code>: Since the program is properly invoked with 1
-parameter, this is the first state it will go into. This state just
-invokes printf, and sends the parser to state <code>012</code> (which is
-<code>&lt;E&gt;</code>).</p>
+<p>Note <code>N1</code>: It should never enter this state, unless the user invokes the
+program with no parameters, in which case it just returns 0.</p>
+<p>Note <code>N2</code>: Since the program is properly invoked with 1 parameter, this is
+the first state it will go into. This state just invokes
+printf, and sends the parser to state <code>012</code> (which is <code>&lt;E&gt;</code>).</p>
 <p>The <code>E</code> and <code>T</code> states work like this:</p>
 <div class="sourceCode" id="cb10"><pre class="sourceCode c"><code class="sourceCode c"><span id="cb10-1"><a href="#cb10-1" aria-hidden="true" tabindex="-1"></a><span class="dt">int</span> e<span class="op">(){</span> <span class="cf">return</span> eprime<span class="op">(</span> t<span class="op">()</span> <span class="op">);</span> <span class="op">}</span></span></code></pre></div>
 <p>The <code>E'</code> and <code>T'</code> states work like this:</p>
@@ -280,9 +268,8 @@ invokes printf, and sends the parser to state <code>012</code> (which is
 <span id="cb11-7"><a href="#cb11-7" aria-hidden="true" tabindex="-1"></a>    <span class="op">}</span></span>
 <span id="cb11-8"><a href="#cb11-8" aria-hidden="true" tabindex="-1"></a>    <span class="cf">else</span> <span class="cf">return</span> intermediate<span class="op">;</span></span>
 <span id="cb11-9"><a href="#cb11-9" aria-hidden="true" tabindex="-1"></a><span class="op">}</span></span></code></pre></div>
-<p>The <code>D</code>, <code>X</code> and <code>O</code> states work
-like this (they assume that they’re initially called with
-<code>0</code>):</p>
+<p>The <code>D</code>, <code>X</code> and <code>O</code> states work like this (they assume that they’re initially
+called with <code>0</code>):</p>
 <div class="sourceCode" id="cb12"><pre class="sourceCode c"><code class="sourceCode c"><span id="cb12-1"><a href="#cb12-1" aria-hidden="true" tabindex="-1"></a><span class="dt">int</span> octal<span class="op">(</span> <span class="dt">int</span> intermediate <span class="op">)</span></span>
 <span id="cb12-2"><a href="#cb12-2" aria-hidden="true" tabindex="-1"></a><span class="op">{</span></span>
 <span id="cb12-3"><a href="#cb12-3" aria-hidden="true" tabindex="-1"></a>    <span class="cf">if</span><span class="op">(</span> ch<span class="op">&gt;=</span><span class="ch">&#39;0&#39;</span> <span class="op">&amp;&amp;</span> ch<span class="op">&lt;=</span><span class="ch">&#39;7&#39;</span> <span class="op">)</span></span>
@@ -294,56 +281,35 @@ like this (they assume that they’re initially called with
 <span id="cb12-9"><a href="#cb12-9" aria-hidden="true" tabindex="-1"></a>    <span class="cf">else</span> <span class="cf">return</span> intermediate<span class="op">;</span></span>
 <span id="cb12-10"><a href="#cb12-10" aria-hidden="true" tabindex="-1"></a><span class="op">}</span></span></code></pre></div>
 <p><code>F</code> and <code>C</code> work similarly.</p>
-<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0
-License:</h2>
-<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights
-Reserved. You are free to share and adapt this file under the terms of
-this license:</p>
+<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0 License:</h2>
+<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved.
+You are free to share and adapt this file under the terms of this license:</p>
 <pre><code>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</code></pre>
-<p>For more information, see:
-https://creativecommons.org/licenses/by-sa/4.0/</p>
+<p>For more information, see: https://creativecommons.org/licenses/by-sa/4.0/</p>
 
 <!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
 <!-- START: this line starts content for HTML phase 22 by: bin/output-index-inventory.sh via bin/md2html.sh -->
 
 <!-- START: this line starts content generated by: bin/output-index-inventory.sh -->
 
-<h1 id="inventory-for-1993vanb"><a name="inventory"></a>Inventory for
-1993/vanb</h1>
+<h1 id="inventory-for-1993vanb"><a name="inventory"></a>Inventory for 1993/vanb</h1>
 <p><a href="#top">Jump to top</a></p>
 <h2 id="primary-files">Primary files</h2>
 <ul>
-<li><a
-href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/vanb.c">vanb.c</a>
-- entry source</li>
-<li><a
-href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/Makefile">Makefile</a>
-- entry Makefile</li>
-<li><a
-href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/vanb.alt.c">vanb.alt.c</a>
-- alternative source</li>
-<li><a
-href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/vanb.orig.c">vanb.orig.c</a>
-- original source</li>
-<li><a
-href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/try.sh">try.sh</a>
-- how to run</li>
-<li><a href="1993_vanb.tar.bz2">1993_vanb.tar.bz2</a> - download entry
-source</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/vanb.c">vanb.c</a> - entry source</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/Makefile">Makefile</a> - entry Makefile</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/vanb.alt.c">vanb.alt.c</a> - alternative source</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/vanb.orig.c">vanb.orig.c</a> - original source</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/try.sh">try.sh</a> - how to run</li>
+<li><a href="1993_vanb.tar.bz2">1993_vanb.tar.bz2</a> - download entry source</li>
 </ul>
 <h2 id="secondary-files">Secondary files</h2>
 <ul>
 <li><a href="index.html">index.html</a> - entry home page</li>
-<li><a
-href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/.entry.json">.entry.json</a>
-- description of entry in JSON</li>
-<li><a
-href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/.gitignore">.gitignore</a>
-- list of files that should not be committed under git</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/.entry.json">.entry.json</a> - description of entry in JSON</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/.gitignore">.gitignore</a> - list of files that should not be committed under git</li>
 <li><a href=".path">.path</a> - directory path from top directory</li>
-<li><a
-href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/README.md">README.md</a>
-- markdown source for index.html</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/vanb/README.md">README.md</a> - markdown source for index.html</li>
 </ul>
 
 <!-- END: next line ends content generated by: bin/output-index-inventory.sh -->