Expand all leading tabs in markdown files

Given how problematic leading tabs in markdown files can be,
we have expanded all leading tabs in markdown files by:

```sh
find * -type f -name '*.md' -print |
  while read -r file; do
    rm -f "$file.tmp" ;
    expand < "$file" > "$file.tmp" ;
    mv -f -v "$file.tmp" "$file" ;
  done
```

Given the previous changes to `bin/pandoc-wrapper.sh` and other recent
commits and recent pull requests, the were were **NO** changes to
any HTML files.  This is a **good thing** as the expression goes.

No there are no leading tabs in any markdown files.
A check to catch any re-introduction of leading tabs
into any markdown file is on the way.

BTW: We do not have anything against leading tabs in files,
even though we have had to deal with their impact on forming
HTML from markdown files (as well as the calc source code).
It is just that this is one of those cases where tabs conflict
(sometimes caused by people wanting to change the classic
8-space tab model) with a desired outcome.

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

2001/herrmann1/README.md

@@ -113,9 +113,9 @@ type `./herrmann1` to see the final result. The output will be
 Final tape:
 
 ```
-		      *
+                      *
     ..OOIIIIIIIIIIIIIIIIOOOO..
-		      *
+                      *
 ```
 
 (Note that the last frame of the animation is _not_ the final
@@ -217,9 +217,9 @@ Undefined state start.
 Tape:
 
 ```
-	    *
+            *
     ..OOOOOOOOIIIIOO..
-	    *
+            *
 ```
 
 and the return code will be 1. As you can see, the Turing machine
@@ -320,8 +320,8 @@ to use many variables more than once.
 
 - I couldn't refrain from doing a little bit of nasty stuff like
 
-		#define a 0&0
-		#if !a
+                #define a 0&0
+                #if !a
 
     Of course, it is a bit more subtle, and even useful.
 
@@ -363,15 +363,15 @@ the insertion of `#line` directives. If your compiler doesn't
 support this option (and does insert `#line` directives), you
 should change the call to `sed` to remove them, too: Add
 
-	    -e "/^#line/ d"
+            -e "/^#line/ d"
 
     to the sed parameters. Or, if your `#line` directives look like
 
-	    # 15 "filename"
+            # 15 "filename"
 
     add
 
-	    -e "/^# [0-9]/ d"
+            -e "/^# [0-9]/ d"
 
     instead.
 

2001/kev/README.md

@@ -33,9 +33,9 @@ NOTE: each player's paddle is at the bottom and the opponent at the top.
 ## Try:
 
 ``` <!---sh-->
-    ./kev		    # in one terminal
+    ./kev                   # in one terminal
 
-    ./kev localhost	    # in another terminal on the same host
+    ./kev localhost         # in another terminal on the same host
 ```
 
 If you need to change the speed you can reconfigure it like (say

2001/ollinger/README.md

@@ -78,12 +78,12 @@ A: Yes, there are types of entries that show up over and over again.
 
     generating small primes (below is the list of all prime related entries)
 
-	    1985/august
-	    1988/applin
-	    1994/weisberg
-	    1995/makarios
-	    1996/dalbec
-	    2000/bellard
+            1985/august
+            1988/applin
+            1994/weisberg
+            1995/makarios
+            1996/dalbec
+            2000/bellard
 
     As you can see, just a list of primes (let alone small primes)
     does not cut it anymore.
@@ -92,8 +92,8 @@ A: Yes, there are types of entries that show up over and over again.
 
     entries that use some complex state machine/table to print something
 
-	      1988/isaak
-	      1988/phillipps
+              1988/isaak
+              1988/phillipps
 
     Unbeaten for 12 years and counting...
 ```

2001/schweikh/README.md

@@ -66,9 +66,9 @@ You can use it for your shell scripting needs similar to a silent grep
 
 ``` <!---sh-->
     if prog "${VARIABLE}" '<glob>'; then
-	echo VARIABLE matches
+        echo VARIABLE matches
     else
-	echo no match
+        echo no match
     fi
 ```