improve how markdown code language is commented

We added a space between the markdown triple code mark
and language that was enclosed in HTML comments.

So a line of the form:

````
```<!---c--->
````

became:

````
``` <!---c--->
````

This was done to **help** some code see that the HTML comment
string was not a markdown code specifier.   Not all code
understands this after this changed.  For example, `pandoc(1)`
still forms HTML classes of the form "&lt;!---c--&gt;"
when it encounters the above mentioned change.

We also fixed a problem with `2019/dogon/README.md` regarding
a markdown code block.

We also fixed a problem with `2020/yang/README.md` regarding
a markdown code block.

1998/banks/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -34,14 +34,14 @@ macros to, depending on what controls you wish to redefine. For instance, to set
 the throttle up and down to `u` and `d`:
 
 
-```<!---sh-->
+``` <!---sh-->
     make clobber IT=XK_u DT=XK_d all
 ```
 
 because in the header file you can see that `XK_u` corresponds to `u` and `XK_d`
 corresponds to `d`:
 
-```<!---c-->
+``` <!---c-->
     #define XK_d                             0x0064  /* U+0064 LATIN SMALL LETTER D */
     #define XK_u                             0x0075  /* U+0075 LATIN SMALL LETTER U */
 ```
@@ -63,7 +63,7 @@ preselected alternative keys.
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     cat horizon.sc pittsburgh.sc | ./banks
 ```
 
@@ -106,7 +106,7 @@ the right side for movement. These are hard coded, as noted.
 
 To use the default settings for the alternate build:
 
-```<!---sh-->
+``` <!---sh-->
     make alt
 ```
 
@@ -231,7 +231,7 @@ Here is a brief description of the scenery files:
 
 A few examples of how to input scenery:
 
-```<!---sh-->
+``` <!---sh-->
     cat horizon.sc pittsburgh.sc | ./banks
     cat mountains.sc bb.sc | ./banks
     cat mountains.sc river.sc pyramids.sc | ./banks
@@ -240,7 +240,7 @@ A few examples of how to input scenery:
 You can simulate flying through a cloud bank as well:
 
 
-```<!---sh-->
+``` <!---sh-->
     ./banks < /dev/null
 ```
 

1998/bas1/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./bas1.sh
 ```
 

1998/bas2/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./bas2 < file
     echo text | ./bas2
 ```
@@ -15,7 +15,7 @@
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 
     ./try.sh "foo bar" "baz" "IOCCC 1998/bas2" README.md

1998/chaos/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make chaos
 ```
 
@@ -8,21 +8,21 @@ NOTE: Some systems do not implement `halfdelay()` in their `libcurses`.
 You might try compiling with -lncurses if you have that library.
 Or you can build this entry without the `halfdelay()` call by:
 
-```<!---sh-->
+``` <!---sh-->
     make chaos_nohalf
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./chaos
 ```
 
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 

1998/df/README.md

@@ -1,20 +1,20 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./df
 ```
 
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 

1998/dlowe/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -10,7 +10,7 @@ below for more details.
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./dlowe < file > pootfile
 
     ./dlowe < file
@@ -30,7 +30,7 @@ For more detailed information see [1998 dlowe bugs](../../bugs.html#1998_dlowe).
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./dlowe < README.md
     ./dlowe < README.md > README.poot.md
 ```
@@ -39,7 +39,7 @@ Why is there different output?
 
 Also try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -54,7 +54,7 @@ that program.
 
 ### Alternate build:
 
-```<!---sh-->
+``` <!---sh-->
     make alt
 ```
 
@@ -70,7 +70,7 @@ What's the difference between this and `dlowe`?
 
 ### Alternate try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.alt.sh
 ```
 
@@ -93,7 +93,7 @@ more consistent level of quality.  :-)
 
 A CGI script such as:
 
-```<!---sh-->
+``` <!---sh-->
     #!/bin/sh
     # pootify - a sample CGI pootifier
     #
@@ -131,7 +131,7 @@ should use the above one instead. You can use the script
 [pootify.sh](pootify.sh), however, to download and generate html files that you
 can look at locally in a browser or pipe through `less(1)`. For instance:
 
-```<!---sh-->
+``` <!---sh-->
     ./pootify.sh URL=https://microsoft.com | less
 
     ./pootify.sh -r URL=https://microsoft.com > ms.html
@@ -143,7 +143,7 @@ it in a browser.
 
 For an old example of it working as a CGI script see:
 
-```<!---sh-->
+``` <!---sh-->
     https://web.archive.org/web/20040326083431/http://www.pootpoot.com/poot/pootify/?URL=http%3A%2F%2Fwww.ioccc.org
 ```
 

1998/dloweneil/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -22,7 +22,7 @@ For more detailed information see [1998 dloweneil bugs](../../bugs.html#1998_dlo
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./pootris [X size of board] [Y size of board]
 ```
 
@@ -45,14 +45,14 @@ clockwise `l` does as well. Instead of using `d` to drop the letter you can do
 
 ### Alternate build:
 
-```<!---sh-->
+``` <!---sh-->
     make alt
 ```
 
 
 ### Alternate use:
 
-```<!---sh-->
+``` <!---sh-->
     ./pootris.alt [X size of board] [Y size of board]
 ```
 
@@ -73,7 +73,7 @@ experience may mirror one of our experiences:
 
 ### Usage
 
-```<!---sh-->
+``` <!---sh-->
     ./pootris [X size of board] [Y size of board]
 ```
 

1998/dorssel/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./dorssel
     # input some text
 
@@ -17,7 +17,7 @@
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -48,7 +48,7 @@ altering the behavior ?
 Try doing what the last part of the last command in [try.sh](try.sh) suggests.
 As in, do the following:
 
-```<!---sh-->
+``` <!---sh-->
     echo ". -..- . .-. -.-. .. ... .
     -.-. .... .- -. --. .  - .... .  .--. .-. --- --. .-. .- --  ... ---  .. -  -.. --- . ...  -. --- -  ... .... --- ..- -" | ./dorssel
 ```
@@ -91,7 +91,7 @@ invoke undefined behavior.
 
 Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./dorssel < dorssel.c | ./dorssel
 ```
 
@@ -101,20 +101,20 @@ better job than most C beautifiers).
 - Filter your text twice (as in the previous sample) to obtain a version of your
 text that can be reversibly Morsified, i.e.
 
-```<!---sh-->
+``` <!---sh-->
     ./dorssel < dorssel.c | ./dorssel | ./dorssel | ./dorssel
 ```
 
 is the same as
 
-```<!---sh-->
+``` <!---sh-->
     ./dorssel < dorssel.c | ./dorssel
 ```
 
 - The file [dorssel.md](dorssel.md) contains all the information needed to
 understand this program.  For an obfuscated spoiler, try
 
-```<!---sh-->
+``` <!---sh-->
     ./dorssel < dorssel.md
 ```
 

1998/dorssel/dorssel.md

@@ -42,7 +42,7 @@ That means bits 6 and 5 set to 00 is length 1, set to 01 is length 2, etc.
 But this would mean that we would have to extract the length into a
 counter before shifting out each symbol, such as
 
-```<!---c-->
+``` <!---c-->
     length = (encoding & 96) >> 5;
     do {
 	    putchar(encoding & 1 ? '-' : '.');
@@ -62,7 +62,7 @@ We can also use the remaining bits to *include* the counter
 
 with 1 bit still to be chosen freely (let's assume it is 0).  Now we can do
 
-```<!---c-->
+``` <!---c-->
     do {
 	    putchar(encoding & 1 ? '-' : '.');
 	    encoding >>= 1;
@@ -87,7 +87,7 @@ Notice these encodings in the initialization string.  Only the coding for
 `5` needs an escape (`5 = ..... > 01111111 = '\177'`).  The way the length
 is encoded still allows the encoding to be its own counter:
 
-```<!---c-->
+``` <!---c-->
     do {
 	    putchar(encoding & 1 ? '-' : '.');
 	    encoding = (encoding + 32) >> 1;
@@ -101,7 +101,7 @@ precision, so that the actual value of the `char` remains `<= 127`.
 The character `'-'` (ASCII 45) and `'.'` (ASCII 46) are conveniently in
 sequence, so the putchar can simply be
 
-```<!---c-->
+``` <!---c-->
     putchar(45 + encoding % 2);
 ```
 
@@ -110,7 +110,7 @@ The assignment can be incorporated into the `while` control test, and a
 `do-while` loop with a body of a single expression statement can be written
 as a `while` loop with a comma operator in the test:
 
-```<!---c-->
+``` <!---c-->
     while(putchar(45 + encoding % 2), encoding = encoding + 32 >> 1);
 ```
 

1998/fanf/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -10,7 +10,7 @@ this entry because of the system resources it requires.
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./fanf
 ```
 
@@ -19,7 +19,7 @@ this entry because of the system resources it requires.
 
 Enter an expression on standard input.  To try some we have selected:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -47,7 +47,7 @@ can you begin to understand what it is doing?
 
 Look at the first stage of the C pre-processing which was done like:
 
-```<!---sh-->
+``` <!---sh-->
     cc fanf.c -E > fanftmp1.c
 ```
 

1998/schnitzi/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -18,7 +18,7 @@ For more detailed information see [1998 schnitzi bugs](../../bugs.html#1998_schn
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./schnitzi n > sort.c
     make sort
     ./sort
@@ -32,14 +32,14 @@ where `n` and `x`, `y` and `z` are numbers.
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
 What happens if at the command line you don't specify `n` numbers that the
 program expects? For instance try:
 
-```<!---sh-->
+``` <!---sh-->
     ./schnitzi 5 > sort.c
     make sort
 
@@ -99,7 +99,7 @@ a depth of one.
 So what does it do?  Give it an integer `(1 < n < 27)` on the command
 line, such as
 
-```<!---sh-->
+``` <!---sh-->
     ./schnitzi 5
 ```
 
@@ -109,7 +109,7 @@ them, however, using only `if/else` statements, without arrays or
 looping.  To see the resulting program run, redirect the output from
 `schnitzi` into another file, like this
 
-```<!---sh-->
+``` <!---sh-->
     ./schnitzi 4 > sort.c
 ```
 

1998/schweikh1/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -12,7 +12,7 @@ includes some interesting details about the entry.
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./schweikh1
 ```
 
@@ -30,7 +30,7 @@ if you don't have a Mac as it has some interesting details about the entry.
 
 ### Alternate build:
 
-```<!---sh-->
+``` <!---sh-->
     make alt
 ```
 
@@ -126,7 +126,7 @@ macros can be defined, because you could write strictly conforming
 programs that may fail to compile due to syntax errors: supposing that
 `<stdio.h>` defines `PIPE_BUF`, then the conforming
 
-```<!---c-->
+``` <!---c-->
     #include <assert.h>
     #include <stdio.h>    /*  <- or where the bogus macro is defined */
     #include <string.h>
@@ -155,7 +155,7 @@ C compilers.
    must resemble one of the canonical forms, `"foo.h"` or `<bar.h>`.
    This lets us write things like
 
-```<!---c-->
+``` <!---c-->
     #define HEADER "foo.h"
     #include HEADER
 ```
@@ -164,7 +164,7 @@ C compilers.
    torturing the preprocessor a little more, by using token pasting,
    at least one compiler falls over.
 
-```<!---c-->
+``` <!---c-->
     #define H(x) <st##x##.h>
     #include H(dio)              /* expands to <stdio.h> */
 ```
@@ -187,7 +187,7 @@ C compilers.
    ISO 6.8.4. ISO 6.1.4 defines string literals as s-char-sequences,
    which may include octal escape sequences. Let's look at
 
-```<!---c-->
+``` <!---c-->
     #include <stdio.h>
     #line 42 "foo\0bar"
     int main (void) {
@@ -214,7 +214,7 @@ C compilers.
     under his/her nose. Easy money from a bet! Make sure your guru has
     no chance to use Standardese weasel words as an escape: can I have
 
-```<!---c-->
+``` <!---c-->
     case <some_token>:
     case <some_token>:
 ```
@@ -255,7 +255,7 @@ script to compute the character count according to the rules.
 The advantages of an independent clean room approach...
 
 
-```<!---perl-->
+``` <!---perl-->
     #!/usr/bin/perl -w
     $/ = "\0";
     $_ = <>;
@@ -266,7 +266,7 @@ The advantages of an independent clean room approach...
 
 To use, try:
 
-```<!---sh-->
+``` <!---sh-->
     perl ./charcount.pl schweikh1.c
 ```
 

1998/schweikh1/macos.md

@@ -19,7 +19,7 @@ However, as noted, macOS does **not** have `/usr/include` so this would never
 work for macOS without some changes, described next. For macOS you will need the
 command line tools installed which can be done like:
 
-```<!---sh-->
+``` <!---sh-->
     sudo xcode-select --install
 ```
 
@@ -50,7 +50,7 @@ which has been changed to be:
 
 Shortly below that you will see, as noted above, the numbers:
 
-```<!---c-->
+``` <!---c-->
     if ((H = fopen (__FILE__+43, 43+__FILE__)))
     while ((fgets (L, (int)sizeof L, H)) != 0) {
 	    I[strcspn (I, 45+__FILE__)] = O = 0;

1998/schweikh2/README.md

@@ -1,26 +1,26 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./yarng
 ```
 
 or
 
-```<!---sh-->
+``` <!---sh-->
     ./yarng integer_number
 ```
 
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 
     ./yarng
@@ -42,13 +42,13 @@ At the time of judging, some non-gcc compilers that were not fully ANSI standard
 did not compile this entry correctly. Also at that time, some gcc and egcs
 implementations ran into a problem when building the entry. Doing:
 
-```<!---sh-->
+``` <!---sh-->
     make schweikh2
 ```
 
 often produced an error of the form:
 
-```<!---sh-->
+``` <!---sh-->
     gcc -ansi schweikh2.alt.c -o schweikh2.alt
     as: Error: cca00NzV.s, line 58: Missing " at end of string
 	 "
@@ -58,20 +58,20 @@ often produced an error of the form:
 
 because the line:
 
-```<!---c-->
+``` <!---c-->
     #line 10 ONE(O(1,1,2,6,0,6))
 ```
 
 turned into the line:
 
-```<!---c-->
+``` <!---c-->
     # 9 "01\012"
 ```
 
 (note, though, how that line is on line 11) which caused gcc to give to the
 assembler the following two lines:
 
-```<!---asm-->
+``` <!---asm-->
     .stabs "schweikh2.c
     ",132,0,0,Ltext1
 ```
@@ -80,7 +80,7 @@ and the lone `"` after the `#.file` line resulted in an assembly syntax error.
 
 In some cases one had to compile using `gcc -g`:
 
-```<!---sh-->
+``` <!---sh-->
     make schweikh2 CFLAGS=-g
 ```
 
@@ -105,7 +105,7 @@ still can :-) ).
 
 Because of this bug, the code was changed to be instead:
 
-```<!---c-->
+``` <!---c-->
     #line 10 "01\015"
 ```
 
@@ -122,13 +122,13 @@ compiler error:
 
 so the line:
 
-```<!---c-->
+``` <!---c-->
     #line 10 "01\015"
 ```
 
 was changed to:
 
-```<!---c-->
+``` <!---c-->
     #line 10 ONE(O(1,1,2,6,0,6))
 ```
 
@@ -158,7 +158,7 @@ different values? How long would you need for an empirical test?
 
 For example:
 
-```<!---sh-->
+``` <!---sh-->
     $ ./yarng 32
     10111001010101110110010101001111
     $ ./yarng 5

1998/schweikh3/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -23,7 +23,7 @@ If `dir` is the directory (or a directory tree) where you keep
 all your favorite pictures off the Internet or from
 `alt.binaries.pictures.*`, do
 
-```<!---sh-->
+``` <!---sh-->
     find dir -type f -print | ./samefile
 ```
 
@@ -34,7 +34,7 @@ Maybe you will not need to buy another 10 GB disk to store them.  :-)
 
 If you're in this winning entry's directory:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -53,7 +53,7 @@ which if (in the code) is unset will be set to the default, 32767.
 If you wish to change the size to say, 55555:
 
 
-```<!---sh-->
+``` <!---sh-->
     make clobber SIZE=55555 alt
 ```
 
@@ -83,7 +83,7 @@ Thank God the IEEE does not standardize a coding style...
 This is best explained in the man page. The troff source for this
 man page can be found in the file [samefile.1](samefile.1). To render try:
 
-```<!---sh-->
+``` <!---sh-->
     `man ./samefile.1
 ```
 
@@ -100,7 +100,7 @@ Otherwise:
 
 #### SYNOPSIS
 
-```<!---sh-->
+``` <!---sh-->
     ./samefile
 ```
 
@@ -141,7 +141,7 @@ inode numbers is also  minimized.  Suppose  you  have  six
 identical  files  of size 100 in an inode group consisting
 of the three inodes with numbers 10, 20 and 30:
 
-```<!---sh-->
+``` <!---sh-->
     $ ls -i   # output edited for readability:
       10 file1     20 file4     30 file6
       10 file2     20 file5
@@ -177,7 +177,7 @@ For everybody:
 
 What are the duplicates under my home directory?
 
-```<!---sh-->
+``` <!---sh-->
     find $HOME | ./samefile
 ```
 
@@ -185,14 +185,14 @@ For the sysadmin folks:
 
 Report all duplicate files under /usr larger than 16k:
 
-```<!---sh-->
+``` <!---sh-->
     find /usr -size +16384c -a -type f | ./samefile
 ```
 
 For the ftp and WWW admins:
 How much space is wasted below our site's /pub directory?
 
-```<!---sh-->
+``` <!---sh-->
     find /pub -type f | samefile | awk '{sum += $1} END {print sum}'
 ```
 

1998/tomtorfs/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./tomtorfs filename bitwidth polynom reflected init xor
 ```
 
@@ -25,7 +25,7 @@ where:
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -56,7 +56,7 @@ archiver that uses the CRC-32 algorithm.
 
 #### CRC-16:
 
-```<!---sh-->
+``` <!---sh-->
     ./tomtorfs filename 16 1021 0 FFFF 0000
 ```
 
@@ -64,21 +64,21 @@ archiver that uses the CRC-32 algorithm.
 #### CRC-32:
 
 
-```<!---sh-->
+``` <!---sh-->
     ./tomtorfs filename 32 04C11DB7 1 FFFFFFFF FFFFFFFF
 ```
 
 
 #### XMODEM:
 
-```<!---sh-->
+``` <!---sh-->
     ./tomtorfs filename 16 8408 1 0000 0000
 ```
 
 
 #### ARC:
 
-```<!---sh-->
+``` <!---sh-->
     ./tomtorfs filename 16 8005 1 0000 0000
 ```