add rules, guidelines, fix HTML code, move compressed tarball in inventory

By changing the _inventory_order_ of the compressed tarball from
**100000** to **1415926535**, the compressed tarball will land at
the top of the secondary file list and remain still easy to find.

Updated the `manifest.numbers` spreadsheet and rebuilt
the `.entry.json` files.

Added `next/` directory to hold the next IOCCC rules and guidelines.
Added `next/README.md` that `bin/gen-top-html.sh` uses to form
the `next/index.html` file.

Added _Rules and Guidelines_ link to the sidenav bar to link to the
`next/index.html` file.

Added _IOCCC Rules_ as `next/rules.md` that `bin/gen-top-html.sh`
uses to form the `next/rules.html` file.

Added _IOCCC Guidelines_ as `next/guidelines.md` that `bin/gen-top-html.sh`
uses to form the `next/guidelines.html` file.

Changed `bin/gen-top-html.sh` VERSION from "1.2.4 2024-04-13"
to "1.3 2024-04-14".

Prevent `pandoc(1)` from interpreting the commented out language
of a markdown code block as a code class.  So a markdown such as:

````
``` <!---sh-->
...
```
````

that produced HTML of the form:

```html
<pre class="&lt;!---sh--&gt;"><code>...</code></pre>
```

will now produce HTML of the form:

```html
<pre><code>...</code></pre>
```

NOTE: Before when the language of a markdown code block
was not commented, the HTML produced by `pandoc(1)` was
oddly indented with extra whitespace on the first line
of the code block.  While commenting out the language
of the code block removed some of the odd intending,
it left a weird class in the HTML pre block that
surrounded the HTML code block.  This hack prevents
`pandoc(1)` from assigning a class to the HTML pre block.

Changed `in/md2html.sh` VERSION from "1.2.1 2024-04-13"
to "1.3 2024-04-14".

Added `make gen_sitemap` to end of both `make www` and `make
quick_www` in top level Makefile.

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

**IMPORTANT NOTE**: The current `next/rules.md` and `next/guidelines.md`
are simply the 2020 IOCCC Rules and Guidelines converted into
markdown form.  There are **NOT** the Rules and Guidelines that
will be used the IOCCC MOCK, nor the next IOCCC.

TODO: Improve the `bin/gen-status.sh` tool to modify the top of the
      `next/rules.md` and `next/guidelines.md` files to keep them
      in sync with the _contest_status_ as found in `status.json`.

TODO: Improve the look and feel of the `next/rules.md` and
      `next/guidelines.md` markdown files.

2019/yang/index.html

@@ -88,6 +88,7 @@
     <div class="sidenav">
       <a href="../../news.html">IOCCC News</a>
       <a href="../../status.html">Contest status</a>
+      <a href="../../next/index.html">Rules and Guidelines</a>
       <a href="../../faq.html#submit">How to enter the IOCCC</a>
       <a href="../../faq.html">FAQ</a>
     </div>
@@ -141,13 +142,13 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
 
 <h2 id="to-build">To build:</h2>
-<pre class="&lt;!---sh--&gt;"><code>    make</code></pre>
+<pre><code>    make</code></pre>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
 <p>The current status of this entry is:</p>
 <pre><code>    STATUS: INABIAF - please **DO NOT** fix</code></pre>
 <p>For more detailed information see <a href="../../bugs.html#2019_yang">2019 yang bugs</a>.</p>
 <h2 id="to-use">To use:</h2>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog sample_input.txt a b c d
+<pre><code>    ./prog sample_input.txt a b c d
 
     cat a
 
@@ -159,34 +160,34 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 
     cat a b c d | ./prog</code></pre>
 <h2 id="try">Try:</h2>
-<pre class="&lt;!---sh--&gt;"><code>    ./try.sh</code></pre>
+<pre><code>    ./try.sh</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>Do you understand how this program works? You may have to go over and over the
 output again.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <h3 id="summary">Summary:</h3>
 <p>Scramble/unscramble to single file:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog original.txt &gt; scrambled.txt
+<pre><code>    ./prog original.txt &gt; scrambled.txt
 
     ./prog &lt; scrambled.txt &gt; unscrambled.txt</code></pre>
 <p>Scramble/unscramble to multiple files:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog input.txt output1.txt output2.txt ...
+<pre><code>    ./prog input.txt output1.txt output2.txt ...
 
     cat output1.txt output2.txt ... | ./prog &gt; unscrambled.txt</code></pre>
 <p>Re-scramble:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog original.txt | ./prog - &gt; scrambled1.txt
+<pre><code>    ./prog original.txt | ./prog - &gt; scrambled1.txt
     ./prog original.txt | ./prog - | ./prog - &gt; scrambled2.txt
     ./prog original.txt | ./prog - | ./prog - | ... &gt; scrambled3.txt</code></pre>
 <p>Scramble slowly:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog input.txt | ruby prog.c</code></pre>
+<pre><code>    ./prog input.txt | ruby prog.c</code></pre>
 <p>Input must be in UTF-8 encoding.</p>
 <h3 id="details">Details:</h3>
 <p>This is a text scrambling utility. To scramble text, specify input file name as
 the first argument:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog input.txt &gt; output.txt</code></pre>
+<pre><code>    ./prog input.txt &gt; output.txt</code></pre>
 <p>If original input file was small enough to fit in your terminal, you
 can simply use <code>cat</code> to unscramble the output text.</p>
-<pre class="&lt;!---sh--&gt;"><code>    cat output.txt</code></pre>
+<pre><code>    cat output.txt</code></pre>
 <p>It might seem like nothing was scrambled, but you can try passing the output
 through <code>strings(1)</code> and see that most of the original strings are gone. What
 happened is that the original text has been shuffled with ANSI cursor
@@ -194,14 +195,14 @@ positioning codes inserted in such a way that characters are printed in random
 order. This effect is more visible if there is a delay after each character is
 printed. For convenience, a utility is included in the source to output
 characters slowly:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog input.txt | ruby prog.c</code></pre>
+<pre><code>    ./prog input.txt | ruby prog.c</code></pre>
 <p>Scrambling order is deterministic, but you can reshuffle the output by
 piping it through the same utility again, by specifying <code>-</code> as the
 first argument:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog input.txt | ./prog - | ./prog - | ...</code></pre>
+<pre><code>    ./prog input.txt | ./prog - | ./prog - | ...</code></pre>
 <p>You can also split the input to multiple files, each getting a subset
 of the original input characters:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog input.txt output1.txt output2.txt ...
+<pre><code>    ./prog input.txt output1.txt output2.txt ...
     cat output1.txt output2.txt ... &gt; unscrambled.txt</code></pre>
 <p>You can only unscramble files with <code>cat</code> if the input fits in a single
 terminal screen. If you don’t know what will be the terminal size of
@@ -213,11 +214,11 @@ sufficient for unscrambling because any scrolling causes the character
 positions to be misaligned. But fear not, this utility also includes
 unscrambling functionality. If no argument is specified, input will
 be read through <code>stdin</code> and unscrambled to <code>stdout</code>:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog &lt; scrambled.txt &gt; unscrambled.txt</code></pre>
+<pre><code>    ./prog &lt; scrambled.txt &gt; unscrambled.txt</code></pre>
 <p>Where this is useful is that if you scramble the input to multiple
 files and unscramble each output file individually, those output
 files can be printed on transparencies and distributed separately.</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog input.txt output1.txt output2.txt output3.txt
+<pre><code>    ./prog input.txt output1.txt output2.txt output3.txt
     ./prog &lt; output1.txt &gt; layer1.txt
     ./prog &lt; output2.txt &gt; layer2.txt
     ./prog &lt; output3.txt &gt; layer3.txt</code></pre>
@@ -225,7 +226,7 @@ files can be printed on transparencies and distributed separately.</p>
 <a href="https://en.wikipedia.org/wiki/Visual_cryptography">visual cryptography</a>.</p>
 <p>This utility can also be used just for removing trailing whitespaces
 and expanding tabs to 8 spaces.</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./prog input.txt | ./prog</code></pre>
+<pre><code>    ./prog input.txt | ./prog</code></pre>
 <h3 id="features">Features:</h3>
 <h4 id="utf-8-support">UTF-8 support:</h4>
 <p>A simple text scrambling utility might not have required a screenful
@@ -295,10 +296,10 @@ the same name, the character who is highly skilled in writing letters.</p>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/yang/try.sh">try.sh</a> - how to run</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/yang/violet.c">violet.c</a> - source formatter as ASCII Violet Evergarden</li>
 <li><a href="spoiler.html">spoiler.html</a> - SPOILER WARNING</li>
-<li><a href="2019_yang.tar.bz2">2019_yang.tar.bz2</a> - download entry tarball</li>
 </ul>
 <h2 id="secondary-files">Secondary files</h2>
 <ul>
+<li><a href="2019_yang.tar.bz2">2019_yang.tar.bz2</a> - download entry tarball</li>
 <li><a href="index.html">index.html</a> - this web page</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/yang/README.md">README.md</a> - markdown source for this web page</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/yang/.entry.json">.entry.json</a> - description of entry in JSON</li>