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.

2014/vik/README.md

@@ -1,7 +1,7 @@
 ## To build:
 
 ```sh
-make
+    make
 ```
 
 There is an alternate version that will theoretically work with Windows
@@ -14,7 +14,7 @@ code](#alternate-code) section below.
 The current status of this entry is:
 
 ```
-STATUS: known bug - please help us fix
+    STATUS: known bug - please help us fix
 ```
 
 For more detailed information see [2014 vik bugs](../../bugs.html#2014_vik).
@@ -23,16 +23,16 @@ For more detailed information see [2014 vik bugs](../../bugs.html#2014_vik).
 ## To use:
 
 ```sh
-echo foo | ./prog > audio_file.raw
+    echo foo | ./prog > audio_file.raw
 
-echo foo | ./prog | mplayer -demuxer rawaudio -
+    echo foo | ./prog | mplayer -demuxer rawaudio -
 ```
 
 
 ## Try:
 
 ```sh
-./try.sh
+    ./try.sh
 ```
 
 
@@ -45,7 +45,7 @@ instructions on how to get it to work with Windows.
 ### Alternate build:
 
 ```sh
-make alt
+    make alt
 ```
 
 
@@ -60,14 +60,13 @@ This program sets a new tone for obfuscation. But do you understand
 what it says about obfuscation? Perhaps:
 
 ```sh
-./prog < prog.c > prog.raw
+    ./prog < prog.c > prog.raw
 ```
 
 might speak to your coding style? If not, then perhaps:
 
 ```sh
-./prog < README.md | mplayer -demuxer rawaudio -
-
+    ./prog < README.md | mplayer -demuxer rawaudio -
 ```
 
 might help? :-)
@@ -89,7 +88,7 @@ Don't forget the last '`-`' as it makes `mplayer(1)` read from `stdin`.
 ## Convert audio file with Morse signals to text
 
 ```sh
-./prog e < audio_file.raw
+    ./prog e < audio_file.raw
 ```
 
 or alternatively pass a .wav file as input.
@@ -108,7 +107,7 @@ program with this platform, the following line can be added to `main()` before
 any code in order for the program to run correctly:
 
 ```c
-_setmode(_fileno(stdout), 0x8000);
+    _setmode(_fileno(stdout), 0x8000);
 ```
 
 NOTE: see the [alternate code](prog.alt.c) for this.