improved indentation and whitespace for markdown code blocks

All code blocks in markdown have been intended by at least 4 spaces.

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 from "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`.

Fixed excess whitespace after list Author on entry `index.html` page.

Changed `bin/output-index-author.sh` VERSION from "1.5.2 2024-03-26"
to "1.6 2024-03-31".

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

TODO: Fix the problem of the initial line of code being extra intended.
TODO: Fix excess whitespace around code that is inline.

2011/blakely/README.md

@@ -1,7 +1,7 @@
 ## To build:
 
 ```sh
-make
+    make
 ```
 
 
@@ -10,20 +10,20 @@ make
 Zoom out and make your terminal window 53 or more lines deep.
 
 ```sh
-./blakely < blakely.c | head -300
+    ./blakely < blakely.c | head -300
 ```
 
 
 ## Try:
 
 ```sh
-./try.sh
+    ./try.sh
 ```
 
 For those who have a lot of time, try:
 
 ```sh
-./blakely < t0_3.dat
+    ./blakely < t0_3.dat
 ```
 
 though one might or might not need to kill it, depending on your boredom
@@ -41,7 +41,7 @@ If you have enough time to spare, put the plan of your garden in a text file,
 and run:
 
 ```sh
-./blakely - < garden.txt
+    ./blakely - < garden.txt
 ```
 
 
@@ -55,7 +55,7 @@ over tabs.
 In order to see the main feature of the code, type:
 
 ```sh
-./blakely < blakely.c
+    ./blakely < blakely.c
 ```
 
 and wait for about four seconds before using Ctrl-C (or whatever) to end the program. The
@@ -73,7 +73,7 @@ the first 15 decimal places of pi after 4 time steps. This was setup using the
 other feature of the program which can be demonstrated as follows:
 
 ```sh
-./blakely - < 3.dat
+    ./blakely - < 3.dat
 ```
 
 The program will first display the grid given in [3.dat](3.dat), and then three
@@ -82,7 +82,7 @@ grids will take a substantial amount of time. The final grid has been put into
 [evolve_to_3.dat](evolve_to_3.dat), and if you type
 
 ```sh
-./blakely < evolve_to_3.dat
+    ./blakely < evolve_to_3.dat
 ```
 
 then the 3 will reappear after three time steps.
@@ -213,9 +213,9 @@ without expanding to collide with the digits' evolution.
 Groups of cells such as singletons, pairs, and larger groups like
 
 ```
-* * * * * * * * * *
- *****************
-* * * * * * * * * *
+    * * * * * * * * * *
+     *****************
+    * * * * * * * * * *
 ```
 
 were useful in this regard.

2011/blakely/index.html

@@ -132,8 +132,7 @@
 <h2 id="author"><a name="author"></a>Author:</h2>
 <ul>
 <li>Name: <a href="../../authors.html#Philip_Blakely">Philip Blakely</a><br>
-Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great Britain and Northern Ireland</em> (<em>United Kingdom</em>)
-<br><br></li>
+Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great Britain and Northern Ireland</em> (<em>United Kingdom</em>)</li>
 </ul>
 
 <!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -142,14 +141,14 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
 <!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
 
 <h2 id="to-build">To build:</h2>
-<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span></span></code></pre></div>
+<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a>    <span class="fu">make</span></span></code></pre></div>
 <h2 id="to-use">To use:</h2>
 <p>Zoom out and make your terminal window 53 or more lines deep.</p>
-<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./blakely</span> <span class="op">&lt;</span> blakely.c <span class="kw">|</span> <span class="fu">head</span> <span class="at">-300</span></span></code></pre></div>
+<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a>    <span class="ex">./blakely</span> <span class="op">&lt;</span> blakely.c <span class="kw">|</span> <span class="fu">head</span> <span class="at">-300</span></span></code></pre></div>
 <h2 id="try">Try:</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">./try.sh</span></span></code></pre></div>
+<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">./try.sh</span></span></code></pre></div>
 <p>For those who have a lot of time, try:</p>
-<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">./blakely</span> <span class="op">&lt;</span> t0_3.dat</span></code></pre></div>
+<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">./blakely</span> <span class="op">&lt;</span> t0_3.dat</span></code></pre></div>
 <p>though one might or might not need to kill it, depending on your boredom
 threshold.</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
@@ -159,14 +158,14 @@ if given its own source as input, and allows to check if your garden
 is a <a href="http://en.wikipedia.org/wiki/Garden_of_Eden_%28cellular_automaton%29">Garden of Eden</a>, all in one source.</p>
 <p>If you have enough time to spare, put the plan of your garden in a text file,
 and run:</p>
-<div class="sourceCode" id="cb5"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./blakely</span> <span class="at">-</span> <span class="op">&lt;</span> garden.txt</span></code></pre></div>
+<div class="sourceCode" id="cb5"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a>    <span class="ex">./blakely</span> <span class="at">-</span> <span class="op">&lt;</span> garden.txt</span></code></pre></div>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>This program uses a well-known algorithm in order to display pi to fifteen
 decimal places. The source-layout itself demonstrates the importance of using
 the correct amount of whitespace in code and the clear superiority of spaces
 over tabs.</p>
 <p>In order to see the main feature of the code, type:</p>
-<div class="sourceCode" id="cb6"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./blakely</span> <span class="op">&lt;</span> blakely.c</span></code></pre></div>
+<div class="sourceCode" id="cb6"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a>    <span class="ex">./blakely</span> <span class="op">&lt;</span> blakely.c</span></code></pre></div>
 <p>and wait for about four seconds before using Ctrl-C (or whatever) to end the program. The
 results are best viewed in a terminal window at least 60 characters
 high and wide. Alternatively, redirect the output to a separate file
@@ -177,12 +176,12 @@ Life</a>”, using standard input as a starting grid. The
 layout of the source-code is such that it evolves to a digital representation of
 the first 15 decimal places of pi after 4 time steps. This was setup using the
 other feature of the program which can be demonstrated as follows:</p>
-<div class="sourceCode" id="cb7"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./blakely</span> <span class="at">-</span> <span class="op">&lt;</span> 3.dat</span></code></pre></div>
+<div class="sourceCode" id="cb7"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a>    <span class="ex">./blakely</span> <span class="at">-</span> <span class="op">&lt;</span> 3.dat</span></code></pre></div>
 <p>The program will first display the grid given in <a href="3.dat">3.dat</a>, and then three
 more grids (taking a few minutes to display the last). Waiting for any more
 grids will take a substantial amount of time. The final grid has been put into
 <a href="evolve_to_3.dat">evolve_to_3.dat</a>, and if you type</p>
-<div class="sourceCode" id="cb8"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./blakely</span> <span class="op">&lt;</span> evolve_to_3.dat</span></code></pre></div>
+<div class="sourceCode" id="cb8"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a>    <span class="ex">./blakely</span> <span class="op">&lt;</span> evolve_to_3.dat</span></code></pre></div>
 <p>then the 3 will reappear after three time steps.</p>
 <p>As should now be clear, this use of the program will attempt to evolve a given setup
 backwards in time according to the Life rules. The resulting grid is clearly not
@@ -282,9 +281,9 @@ will not collide when evolving.</p>
 into. Therefore it was necessary to add some regions that would quickly die off
 without expanding to collide with the digits’ evolution.
 Groups of cells such as singletons, pairs, and larger groups like</p>
-<pre><code>* * * * * * * * * *
- *****************
-* * * * * * * * * *</code></pre>
+<pre><code>    * * * * * * * * * *
+     *****************
+    * * * * * * * * * *</code></pre>
 <p>were useful in this regard.</p>
 <p>Other problems were keywords which need to be all in one
 string, keywords requiring space after them, and