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.

2012/hou/README.md

@@ -1,21 +1,21 @@
 ## To build:
 
 ```sh
-make
+    make
 ```
 
 
 ## To use:
 
 ```sh
-./hou syntax-file file-to-process
+    ./hou syntax-file file-to-process
 ```
 
 
 ## Try:
 
 ```sh
-./try.sh
+    ./try.sh
 ```
 
 View the `remarks.htm` file in your web browser.
@@ -26,9 +26,9 @@ The result is best viewed in a 80x25 console with ANSI colors.
 ## Try (Windows):
 
 ```
-copy header.htm hou.htm /y
-hou html.txt hou.c >> hou.htm
-start hou.htm
+    copy header.htm hou.htm /y
+    hou html.txt hou.c >> hou.htm
+    start hou.htm
 ```
 
 
@@ -74,15 +74,15 @@ in the regular expression by escaping it with `[]` or `""`.
 The following regular expression operators are supported:
 
 ```
-() [] * + ? | ""
+    () [] * + ? | ""
 ```
 
 For example, one can use the following expression to match a certain declaration
 statement in [hou.c](hou.c):
 
 ```re
-    "char"[ *]*[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_ ]*\]))?[ ]*)*;
-```
+	"char"[ *]*[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_ ]*\]))?[ ]*)*;
+    ```
 
 The regex engine is also algorithmically efficient. To illustrate the point,
 [ansi.txt](ansi.txt) contains a pathological expression [^2] that guarantees a
@@ -90,8 +90,8 @@ hang for the competing Perl engine while matching itself. Try to compare these
 two engines:
 
 ```sh
-./hou ansi.txt ansi.txt
-perl patho.pl < ansi.txt
+    ./hou ansi.txt ansi.txt
+    perl patho.pl < ansi.txt
 ```