set pandoc 8 character tab stops for HTML conversion

We add `--tab-stop=8` to all `pandoc(1)` executions in order to set
a better tab stop indentation, especially for tab intended code blocks.

Changed `bin/pandoc-wrapper.sh` VERSION "1.5.3 2024-03-26"
to "1.6 2024-03-31".

Fixed `1991/brnstnd/sorta.README.md` so that the sorta code
is code blocks.

Removed unneeded paragraph group in copyright in `inc/footer.default.html`.

Performed `make www` to perform the above and test under macOS.

2012/hou/hint.html

@@ -124,23 +124,20 @@
 
 <h2 id="judges-comments">Judges’ comments:</h2>
 <h3 id="to-build">To build:</h3>
-<pre><code>make hou</code></pre>
+<p>make hou</p>
 <h3 id="to-run">To run:</h3>
-<pre><code>./hou syntax-file file-to-process</code></pre>
+<p>./hou syntax-file file-to-process</p>
 <h3 id="try-unix">Try (Unix):</h3>
 <p>The results are best viewed in a 80x25 console with ANSI colors.</p>
-<pre><code>less hou.c
-
-./hou ansi.txt hou.c | less -r
-
-./hou chk.txt hou.c | wc
-
-./hou markdown.txt remarks.markdown &gt; remarks.htm
-your-browser remarks.htm</code></pre>
+<p>less hou.c</p>
+<p>./hou ansi.txt hou.c | less -r</p>
+<p>./hou chk.txt hou.c | wc</p>
+<p>./hou markdown.txt remarks.markdown &gt; remarks.htm
+your-browser remarks.htm</p>
 <h3 id="try-windows">Try (Windows):</h3>
-<pre><code>copy header.htm hou.htm /y
+<p>copy header.htm hou.htm /y
 hou html.txt hou.c &gt;&gt; hou.htm
-start hou.htm</code></pre>
+start hou.htm</p>
 <h3 id="selected-judges-remarks">Selected Judges Remarks:</h3>
 <p>What a versatile entry! It can be used to check the size of IOCCC entries <em>and</em> to publish them as HTML.</p>
 <p>For extra credit: what is the meaning of the number 2321237?</p>
@@ -168,14 +165,14 @@ original text in the format string using “%s”. Other “%” characters in t
 format string must be escaped with another “%”. The space character can be used
 in the regular expression by escaping it with [] or ““.</p>
 <p>The following regular expression operators are supported:</p>
-<pre><code>() [] * + ? | &quot;&quot;</code></pre>
+<p>() [] * + ? | “”</p>
 <p>For example, one can use the following expression to match a certain declaration statement in hou.c:</p>
-<pre><code>&quot;char&quot;[ *]*[a-zA-Z_][0-9a-zA-Z_]*[ ]*((=[0-9a-zA-Z_ ]+)|(\[[0-9a-zA-Z_ ]*\]))?[ ]*(,[ *]*[a-zA-Z_][0-9a-zA-Z_]*[ ]*((=[0-9a-zA-Z_ ]+)|(\[[0-9a-zA-Z_ ]*\]))?[ ]*)*;</code></pre>
+<p>“char”[ *]<em>[a-zA-Z_][0-9a-zA-Z_]</em>[ ]<em>((=[0-9a-zA-Z_ ]+)|([[0-9a-zA-Z_ ]</em>]))?[ ]<em>(,[ *]</em>[a-zA-Z_][0-9a-zA-Z_]<em>[ ]</em>((=[0-9a-zA-Z_ ]+)|([[0-9a-zA-Z_ ]<em>]))?[ ]</em>)*;</p>
 <p>The regex engine is also algorithmically efficient. To illustrate the point,
 ansi.txt contains a pathological expression [2] that guarantees a hang for the
 competing Perl engine while matching itself. Try to compare these two engines:</p>
-<pre><code>./hou ansi.txt ansi.txt
-perl patho.pl &lt; ansi.txt</code></pre>
+<p>./hou ansi.txt ansi.txt
+perl patho.pl &lt; ansi.txt</p>
 <p>Finally, there are a few limitations…</p>
 <ul>
 <li>The only escape sequence supported is and it doesn’t work in [].</li>
@@ -210,11 +207,11 @@ amount of spaghetti branches and virtual thread creations. Finally, the VM in
 
     You are free to share and adapt this file under the terms of this license:
 
-    Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
+        Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
 
     For more information, see:
 
-    https://creativecommons.org/licenses/by-sa/4.0/
+        https://creativecommons.org/licenses/by-sa/4.0/
 
 -->
 
@@ -251,7 +248,7 @@ amount of spaghetti branches and virtual thread creations. Finally, the VM in
 <div class="footer">
   <h2>Copyright and CC BY-SA 4.0 License</h2>
   <p>This file and web page is:</p>
-  <blockquote><p><b>Copyright &copy; 1984-2024 by Landon Curt Noll. All Rights Reserved.</b></p></blockquote>
+  <blockquote><b>Copyright &copy; 1984-2024 by Landon Curt Noll. All Rights Reserved.</b></blockquote>
   <p>You are free to share and adapt this file under the terms of this license:</p>
   <blockquote><b>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</b></blockquote>
   <p>For more information, see:</p>