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.

1998/dlowe/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,11 +142,11 @@ 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 all</code></pre>
+<pre><code>    make all</code></pre>
 <p>There is an alternate version available. See <a href="#alternate-code">Alternate code</a>
 below for more details.</p>
 <h2 id="to-use">To use:</h2>
-<pre class="&lt;!---sh--&gt;"><code>    ./dlowe &lt; file &gt; pootfile
+<pre><code>    ./dlowe &lt; file &gt; pootfile
 
     ./dlowe &lt; file</code></pre>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
@@ -153,22 +154,22 @@ below for more details.</p>
 <pre><code>    STATUS: missing or dead link - please provide them</code></pre>
 <p>For more detailed information see <a href="../../bugs.html#1998_dlowe">1998 dlowe bugs</a>.</p>
 <h2 id="try">Try:</h2>
-<pre class="&lt;!---sh--&gt;"><code>    ./dlowe &lt; README.md
+<pre><code>    ./dlowe &lt; README.md
     ./dlowe &lt; README.md &gt; README.poot.md</code></pre>
 <p>Why is there different output?</p>
 <p>Also try:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./try.sh</code></pre>
+<pre><code>    ./try.sh</code></pre>
 <p>Did you spot the Easter egg there?</p>
 <h2 id="alternate-code">Alternate code:</h2>
 <p>The original entry was just a text based pootifier. This alternate version is
 that program.</p>
 <h3 id="alternate-build">Alternate build:</h3>
-<pre class="&lt;!---sh--&gt;"><code>    make alt</code></pre>
+<pre><code>    make alt</code></pre>
 <h3 id="alternate-use">Alternate use:</h3>
 <pre><code>    ./dlowe.alt &lt; file &gt; pootfile</code></pre>
 <p>What’s the difference between this and <code>dlowe</code>?</p>
 <h3 id="alternate-try">Alternate try:</h3>
-<pre class="&lt;!---sh--&gt;"><code>    ./try.alt.sh</code></pre>
+<pre><code>    ./try.alt.sh</code></pre>
 <p>Did you spot the Easter egg there?</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>Why could this this entry be considered a utility? Well because it
@@ -179,7 +180,7 @@ a CGI program: <a href="https://web.archive.org/web/20001025182142/http://pootpo
 more consistent level of quality. :-)</p>
 <h3 id="historical-remarks">Historical remarks:</h3>
 <p>A CGI script such as:</p>
-<pre class="&lt;!---sh--&gt;"><code>    #!/bin/sh
+<pre><code>    #!/bin/sh
     # pootify - a sample CGI pootifier
     #
     POOT=&quot;/usr/local/bin/dlowe&quot;
@@ -212,14 +213,14 @@ added bonus that one can use <code>file://</code> URLs. If one wants a CGI scrip
 should use the above one instead. You can use the script
 <a href="pootify.sh">pootify.sh</a>, however, to download and generate html files that you
 can look at locally in a browser or pipe through <code>less(1)</code>. For instance:</p>
-<pre class="&lt;!---sh--&gt;"><code>    ./pootify.sh URL=https://microsoft.com | less
+<pre><code>    ./pootify.sh URL=https://microsoft.com | less
 
     ./pootify.sh -r URL=https://microsoft.com &gt; ms.html</code></pre>
 <p>where the first one would show the text as rendered but without links, images
 etc. and the second one would write the html to <code>ms.html</code> so that you could open
 it in a browser.</p>
 <p>For an old example of it working as a CGI script see:</p>
-<pre class="&lt;!---sh--&gt;"><code>    https://web.archive.org/web/20040326083431/http://www.pootpoot.com/poot/pootify/?URL=http%3A%2F%2Fwww.ioccc.org</code></pre>
+<pre><code>    https://web.archive.org/web/20040326083431/http://www.pootpoot.com/poot/pootify/?URL=http%3A%2F%2Fwww.ioccc.org</code></pre>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>This program is a text filter, it reads <code>stdin</code> and outputs the
 “corrected” text to <code>stdout</code>.</p>
@@ -262,10 +263,10 @@ run <code>perl4</code> programs after they’ve been run through it; “encrypt
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/pootify.sh">pootify.sh</a> - pootify tool</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/try.alt.sh">try.alt.sh</a> - how to run alternative code</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/try.sh">try.sh</a> - how to run</li>
-<li><a href="1998_dlowe.tar.bz2">1998_dlowe.tar.bz2</a> - download entry tarball</li>
 </ul>
 <h2 id="secondary-files">Secondary files</h2>
 <ul>
+<li><a href="1998_dlowe.tar.bz2">1998_dlowe.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/1998/dlowe/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/1998/dlowe/.entry.json">.entry.json</a> - description of entry in JSON</li>