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.

2014/deak/README.md

@@ -99,8 +99,8 @@ would not be true, the application would be the following:
     ,1,-1.3                ,1.3,  0,         0,0,0
     ,0               ,0,50, 80,     0,0,0     ,255
     ,               8,0};    int      main       (
-		   int j) {if (j==  1 ){ if(
-	   _[12]      >_[10]  )_[17]=1 ;}  if
+                   int j) {if (j==  1 ){ if(
+           _[12]      >_[10]  )_[17]=1 ;}  if
        (_[13] >_[11     ] ||_[17]==1)  return 1
      ;_[6]   =  _ [13] / _[11]*(_[1]-_[   0])
     +_[  0];  _ [7]=_[12]/_[10]*(_[3]-_[2] )+_
@@ -108,8 +108,8 @@ would not be true, the application would be the following:
     ;_[  5]=  _ [9]*_[9];_[9]=2*_[8]*_[9]+ _[7
      ];_[8   ]  = _ [ 4 ]-_[5]+_[6];_[14   ]++
        ;if((_ [14]<     _ [15])&&(_[4]+ _[ 5]
-	   <_[16      ])) goto l2;  putchar(
-		   " #@*+   "[( int)  _[14]%
+           <_[16      ])) goto l2;  putchar(
+                   " #@*+   "[( int)  _[14]%
     5             ]);_ [13   ] ++ ;   main       (
     0)               ;_[12]++;      _[13]       =0
     ;if(_                [17]    !=1)      putchar

2014/endoh1/spoilers.md

@@ -101,14 +101,14 @@ The compiler tool chain is the following.
     raw.txt               |
       |                   |
       +---------+---------+
-		|
-		| [link.rb]
-		V
-	      main.c
-		|
-		| [gen-prog.c]
-		V
-	      prog.c
+                |
+                | [link.rb]
+                V
+              main.c
+                |
+                | [gen-prog.c]
+                V
+              prog.c
 ```
 
 * [parse.rb](%%REPO_URL%%/2014/endoh1/parse.rb) converts Ruby to AST.

2014/maffiodo1/README.md

@@ -234,10 +234,10 @@ here:
 
 Each row has six columns:
 
-1. `Screen X`	: `x` position of the object in the level.
-2. `Screen Y`	: `y` position of the object in the level.
-3. `Sprite`	: `id` of the sprite to be used for the object.
-4. `CLASSFLAGS`	: a bitmask that describe how the object behaves.
+1. `Screen X`   : `x` position of the object in the level.
+2. `Screen Y`   : `y` position of the object in the level.
+3. `Sprite`     : `id` of the sprite to be used for the object.
+4. `CLASSFLAGS` : a bitmask that describe how the object behaves.
 5. `CLASSPARAM0`: a parameter that depends on `CLASSFLAGS`.
 6. `CLASSPARAM1`: a parameter that depends on `CLASSFLAGS`.
 
@@ -245,52 +245,52 @@ Each row has six columns:
 
 * `ENEMY` (`1`)
 
-	    An enemy. CLASSPARAM0 can be 0 if the enemies don't move, 1 if the
-	    initial move direction is right, -1 if that direction is left. All
-	    enemies that walk will change their direction after 20 steps. The
-	    sprite of an enemy must have 2 other adjacent sprites: SPRITE-1,
-	    used when the enemy dies, and SPRITE+1, used when it moves.
+            An enemy. CLASSPARAM0 can be 0 if the enemies don't move, 1 if the
+            initial move direction is right, -1 if that direction is left. All
+            enemies that walk will change their direction after 20 steps. The
+            sprite of an enemy must have 2 other adjacent sprites: SPRITE-1,
+            used when the enemy dies, and SPRITE+1, used when it moves.
 
 * `BLOCK` (`2`)
 
-	    A wall. Player can walk over the object but can not pass through it.
+            A wall. Player can walk over the object but can not pass through it.
 
 * `OBJECT BLOCK` (`4`)
 
-	    When the player hits the object from below, a new object is created.
-	    CLASSFLAGS of the new object is defined in CLASSPARAM0. The sprite
-	    used for the new object is defined in CLASSPARAM1. The sprite of the
-	    new object must have an adjacent sprite: SPRITE+1, used when the
-	    block is hit.
+            When the player hits the object from below, a new object is created.
+            CLASSFLAGS of the new object is defined in CLASSPARAM0. The sprite
+            used for the new object is defined in CLASSPARAM1. The sprite of the
+            new object must have an adjacent sprite: SPRITE+1, used when the
+            block is hit.
 
 * `POWERUP` (`8`)
 
-	    This is a power-up like the classic Mario mushroom. When the
-	    character hits the power-up object, the character becomes the Super
-	    character. If CLASSFLAGS has the bit ZOOM, the character height will
-	    be doubled.  The Super character can hit the enemies without dying,
-	    but when this happens, the Super character goes back to being
-	    normal.
+            This is a power-up like the classic Mario mushroom. When the
+            character hits the power-up object, the character becomes the Super
+            character. If CLASSFLAGS has the bit ZOOM, the character height will
+            be doubled.  The Super character can hit the enemies without dying,
+            but when this happens, the Super character goes back to being
+            normal.
 
 * `END` (`16`)
 
-	    When the player hits this object the level ends; the player wins.
+            When the player hits this object the level ends; the player wins.
 
 * `ZOOM` (`32`)
 
-	    This flag can be used with POWERUP to indicate a power-up that
-	    will double the size of the player (like the Mario mushroom).
+            This flag can be used with POWERUP to indicate a power-up that
+            will double the size of the player (like the Mario mushroom).
 
 * `DESTROY` (`64`)
 
-	    When the player hits the object (e.g. the classic Mario coin) the
-	    object disappears but the engine does not count the points, so,
-	    from the player point of view, this object is useless.
+            When the player hits the object (e.g. the classic Mario coin) the
+            object disappears but the engine does not count the points, so,
+            from the player point of view, this object is useless.
 
 * `DESTROYUP` (`128`)
 
-	    This object is like a BLOCK but when the player hits the object
-	    from below, the object disappears.
+            This object is like a BLOCK but when the player hits the object
+            from below, the object disappears.
 
 If `CLASSFLAGS` is `0` the object only has an aesthetic function.