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.
This commit is contained in:
Landon Curt Noll committed 2024-04-14 16:54:24 -07:00
1 parent a672335d2d
commit 518a6336d0
734 files changed
+7919 -4119

No files matched your search

+11 -10
View File
@@ -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,16 +142,16 @@ 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>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
<pre><code> STATUS: known bug - please help us fix</code></pre>
<p>For more detailed information see <a href="../../bugs.html#1995_leo">1995 leo bugs</a>.</p>
<h2 id="to-use">To use:</h2>
<pre class="&lt;!---sh--&gt;"><code> ./leo [ deep ] [ right ] [ Variable ] [ cycle [ freq ] ]</code></pre>
<pre><code> ./leo [ deep ] [ right ] [ Variable ] [ cycle [ freq ] ]</code></pre>
<p>See the author’s information below on these details.</p>
<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>Press return after each image is drawn.</p>
<p>The variable names are element-ary. If you find this confusing,
@@ -163,7 +164,7 @@ the secret switches that the author doesn’t divulge ! (All switches are single
characters on the command line - anything that’s not a number is a candidate.)</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>The usage is:</p>
<pre class="&lt;!---sh--&gt;"><code> ./leo [ deep ] [ right ] [ Variable ] [ cycle [ freq ] ]</code></pre>
<pre><code> ./leo [ deep ] [ right ] [ Variable ] [ cycle [ freq ] ]</code></pre>
<p>where the first three are literal words, <code>cycle</code> is a positive integer (0 is
ignored), and <code>freq</code> is an integer (default = 0) that’s supposed to be in the
range <code>0..100</code> (bigger values are allowed, however). Invalid parameters and
@@ -173,7 +174,7 @@ equivalent to <code>./leo 0 0 0 1 Variable 70 right</code>, etc.</p>
<p>If <code>Variable</code> is used, <code>cycle</code> is almost ignored (see below) but has
to be present if you want to enter <code>freq</code> (and you usually do).</p>
<p>Some options to try (besides the obvious):</p>
<pre class="&lt;!---sh--&gt;"><code> ./leo 1 | cat - /dev/tty | gs -</code></pre>
<pre><code> ./leo 1 | cat - /dev/tty | gs -</code></pre>
<p>This draws the basic pattern I invented in high school:</p>
<p>You take a big sheet of “arithmetic” paper and draw a line
of length 1 (between 2 crossings) at the center of the sheet:</p>
@@ -253,11 +254,11 @@ the opening for step 1 is not a single line but a cross:</p>
<pre><code> \./
/ \</code></pre>
<p>To watch it repeatedly (as a screen saver), use:</p>
<pre class="&lt;!---sh--&gt;"><code> ./leo 2 | cat - /dev/tty | gs -</code></pre>
<pre><code> ./leo 2 | cat - /dev/tty | gs -</code></pre>
<p>The command line:</p>
<pre class="&lt;!---sh--&gt;"><code> ./leo Variable 1 | cat - /dev/tty | gs -</code></pre>
<pre><code> ./leo Variable 1 | cat - /dev/tty | gs -</code></pre>
<p>draws the same as above. Try:</p>
<pre class="&lt;!---sh--&gt;"><code> ./leo Variable 1 1 | cat - /dev/tty | gs -</code></pre>
<pre><code> ./leo Variable 1 1 | cat - /dev/tty | gs -</code></pre>
<p>What happened to the picture? Increase <code>freq</code> and watch the changes.</p>
<p>If <code>cycle</code> is more than 1, the program loops, allowing the user to
enjoy randomly changing patterns (the delay is 3 seconds),
@@ -272,7 +273,7 @@ if you want to pipe the output to a printer.</p>
<p>If <code>Variable</code> is used, the actual value of <code>cycle</code> doesn’t matter,
as far as it is &gt; 1. To figure out what difference
<code>cycle</code> makes when <code>Variable</code> is not used, try</p>
<pre class="&lt;!---sh--&gt;"><code> ./leo Variable 37 80 | cat - /dev/tty | gs -</code></pre>
<pre><code> ./leo Variable 37 80 | cat - /dev/tty | gs -</code></pre>
<p>and other values of <code>cycle</code>; smaller values usually require
smaller values of <code>freq</code> for the patterns to be non-trivial.</p>
<p>The options <code>deep</code> and <code>right</code> make the patterns to be drawn in different
@@ -323,10 +324,10 @@ even want to explain what it does. You’ve been warned!</p>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1995/leo/leo.orig.c">leo.orig.c</a> - original source</li>
<li><a href="spoiler1.html">spoiler1.html</a> - spoiler document</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1995/leo/try.sh">try.sh</a> - how to run</li>
<li><a href="1995_leo.tar.bz2">1995_leo.tar.bz2</a> - download entry tarball</li>
</ul>
<h2 id="secondary-files">Secondary files</h2>
<ul>
<li><a href="1995_leo.tar.bz2">1995_leo.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/1995/leo/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/1995/leo/.entry.json">.entry.json</a> - description of entry in JSON</li>