Fix html files in 2001

This also includes a few updates to the bugs file.
2024-08-05 09:48:14 -07:00
1 parent 3da5bb9022
commit 515281417c
@@ -6,7 +6,7 @@

 The programs that this program is supposed to act on,
 [anonymous.ten.c](%%REPO_URL%%/2001/anonymous/anonymous.ten.c) and [anonymous.bed.c](%%REPO_URL%%/2001/anonymous/anonymous.bed.c),
-compiled with `make`, MUST be compiled as 32-bit ELF binaries. In the case that
+compiled with `make`, **MUST** be compiled as **32-bit ELF binaries**. In the case that
 this fails these programs will be compiled as 64-bit binaries as alternate code,
 `anonymous.ten.alt` and `anonymous.bed.alt`, ELF or otherwise. However trying to
 use the entry on these files will fail. See [Alternate code](#alternate-code)
@@ -38,7 +38,7 @@ For more detailed information see [2001/anonymous in bugs.html](../../bugs.html#
    ./anonymous anonymous.bed # if able to compile as a 32-bit (-m32) ELF binary
 ```

-NOTE: if the 32-bit version cannot be compiled the script will at least compile
+**NOTE**: if the 32-bit version cannot be compiled the script will at least compile
 [anonymous.ten](%%REPO_URL%%/2001/anonymous/anonymous.ten.c) as a 64-bit program (or whatever your system is
 set to) and run it directly.

@@ -196,7 +196,7 @@ global state, and the other doesn't.

 There is also quite a nice trick where I wave a magic wand, and a chunk of code
 which should only be run when the program is run for the first time (setting the
-[PC / IP](https://en.wikipedia.org/wiki/Program_counter) to point at `main()`
+[PC/IP](https://en.wikipedia.org/wiki/Program_counter) to point at `main()`
 etc.) gets turned into a <del>frog</del>string.  The C compiler sees a string by
 itself in the code, thinks "yup, that's a valid C expression", and quietly moves
 on to the next line of code.
@@ -231,7 +231,7 @@ new set of switches, and the call to `execv(3)` asks for the newly compiled
 program to be executed.  I would point out that almost every other entry to this
 competition also require a C compiler (well, the published winning entries at any rate,
 and I recognize that a few don't).  There is little real difference between this
-program and one like last year's entry [dhyang](%%REPO_URL%%/2000/dhyang/dhyang.c); both are
+program and one like last year's entry [dhyang](../../2000/dhyang/index.html); both are
 just C programs that generate C code as their output.

 Enjoy and thanks!
@@ -411,7 +411,7 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
 <pre><code>    make</code></pre>
 <p>The programs that this program is supposed to act on,
 <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.ten.c">anonymous.ten.c</a> and <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.bed.c">anonymous.bed.c</a>,
-compiled with <code>make</code>, MUST be compiled as 32-bit ELF binaries. In the case that
+compiled with <code>make</code>, <strong>MUST</strong> be compiled as <strong>32-bit ELF binaries</strong>. In the case that
 this fails these programs will be compiled as 64-bit binaries as alternate code,
 <code>anonymous.ten.alt</code> and <code>anonymous.bed.alt</code>, ELF or otherwise. However trying to
 use the entry on these files will fail. See <a href="#alternate-code">Alternate code</a>
@@ -429,7 +429,7 @@ whatever your system will compile them as).</p>
 <pre><code>    ./try.sh

    ./anonymous anonymous.bed # if able to compile as a 32-bit (-m32) ELF binary</code></pre>
-<p>NOTE: if the 32-bit version cannot be compiled the script will at least compile
+<p><strong>NOTE</strong>: if the 32-bit version cannot be compiled the script will at least compile
 <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.ten.c">anonymous.ten</a> as a 64-bit program (or whatever your system is
 set to) and run it directly.</p>
 <p>What happens if the x86 program has already been modified by this program? The
@@ -537,7 +537,7 @@ local variables which shadow global variables: so one modifies the
 global state, and the other doesn’t.</p>
 <p>There is also quite a nice trick where I wave a magic wand, and a chunk of code
 which should only be run when the program is run for the first time (setting the
-<a href="https://en.wikipedia.org/wiki/Program_counter">PC / IP</a> to point at <code>main()</code>
+<a href="https://en.wikipedia.org/wiki/Program_counter">PC/IP</a> to point at <code>main()</code>
 etc.) gets turned into a <del>frog</del>string. The C compiler sees a string by
 itself in the code, thinks “yup, that’s a valid C expression”, and quietly moves
 on to the next line of code.</p>
@@ -564,7 +564,7 @@ new set of switches, and the call to <code>execv(3)</code> asks for the newly co
 program to be executed. I would point out that almost every other entry to this
 competition also require a C compiler (well, the published winning entries at any rate,
 and I recognize that a few don’t). There is little real difference between this
-program and one like last year’s entry <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dhyang/dhyang.c">dhyang</a>; both are
+program and one like last year’s entry <a href="../../2000/dhyang/index.html">dhyang</a>; both are
 just C programs that generate C code as their output.</p>
 <p>Enjoy and thanks!</p>
 <!--
@@ -10,7 +10,6 @@
 The current status of this entry is:

 > **STATUS: INABIAF - please DO NOT fix**<br>
-> **STATUS: doesn't work with some platforms - please help us fix it**

 For more detailed information see [2001/bellard in bugs.html](../../bugs.html#2001_bellard).

@@ -412,8 +412,7 @@ Location: <a href="../../location.html#FR">FR</a> - <em>French Republic</em> (<e
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
 <p>The current status of this entry is:</p>
 <blockquote>
-<p><strong>STATUS: INABIAF - please DO NOT fix</strong><br>
-<strong>STATUS: doesn’t work with some platforms - please help us fix it</strong></p>
+<p><strong>STATUS: INABIAF - please DO NOT fix</strong><br></p>
 </blockquote>
 <p>For more detailed information see <a href="../../bugs.html#2001_bellard">2001/bellard in bugs.html</a>.</p>
 <h2 id="to-use">To use:</h2>
@@ -11,6 +11,12 @@
    ./coupard
 ```

+**NOTE**: the author notes that you might want to convert the sound formats. For
+this you can use `SoX`. If you do not have this installed then see the
+FAQ on "[using entries that require sound](../../faq.html#sox)"
+for help.
+
+

 ## Try:

@@ -411,6 +411,10 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <pre><code>    make</code></pre>
 <h2 id="to-use">To use:</h2>
 <pre><code>    ./coupard</code></pre>
+<p><strong>NOTE</strong>: the author notes that you might want to convert the sound formats. For
+this you can use <code>SoX</code>. If you do not have this installed then see the
+FAQ on “<a href="../../faq.html#sox">using entries that require sound</a>”
+for help.</p>
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
@@ -4,8 +4,8 @@
    make
 ```

-There is an alternate version with vi(m) key movements. See [alternate
-code](#alternate code) below.
+There is an alternate version with vi(m) key movements. See [Alternate
+code](#alternate-code) below.


 ## To use:
@@ -409,7 +409,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <!-- BEFORE: 1st line of markdown file: 2001/ctk/README.md -->
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
-<p>There is an alternate version with vi(m) key movements. See <a href="#alternate%20code">alternate
+<p>There is an alternate version with vi(m) key movements. See <a href="#alternate-code">Alternate
 code</a> below.</p>
 <h2 id="to-use">To use:</h2>
 <pre><code>    ./ctk</code></pre>
@@ -4,7 +4,7 @@
    make
 ```

-There is an alternate version based on the author's remarks. See [alternate
+There is an alternate version based on the author's remarks. See [Alternate
 code](#alternate-code) below for more details.


@@ -221,13 +221,11 @@ this is not so.
 A: When compiled with `gcc -Wall`, the compiler generated the following
 warnings:

-```
-    suggest parentheses around + or - in operand of &
-    array subscript has type 'char'
-    return type defaults to 'int'
-    control reaches end of non-void function
-    value computed is not used
-```
+> suggest parentheses around `+` or `-` in operand of `&`<br>
+> array subscript has type '`char`'<br>
+> return type defaults to '`int`'<br>
+> control reaches end of non-void function<br>
+> value computed is not used

 The `value computed is not used` warning happens because I use the `&&`
 operator and take advantage of short circuit evaluation instead of using
@@ -248,7 +246,7 @@ appropriate sportsmanship for a program of this genre and can think of
 no worse job than trying to find an elusive bug in an intentionally
 obfuscated program.

-[Judge's note:  This was followed by a description of the bug, and
+[**Judges' note**: This was followed by a description of the bug, and
 the comment:]

 Note, if this program wins, the author thinks it would be good to leave
@@ -409,7 +409,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <!-- BEFORE: 1st line of markdown file: 2001/dgbeards/README.md -->
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
-<p>There is an alternate version based on the author’s remarks. See <a href="#alternate-code">alternate
+<p>There is an alternate version based on the author’s remarks. See <a href="#alternate-code">Alternate
 code</a> below for more details.</p>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
 <p>The current status of this entry is:</p>
@@ -560,11 +560,13 @@ this is not so.</p>
 <h4 id="q-what-about-the-compiler-warnings">Q: What about the compiler warnings?</h4>
 <p>A: When compiled with <code>gcc -Wall</code>, the compiler generated the following
 warnings:</p>
-<pre><code>    suggest parentheses around + or - in operand of &amp;
-    array subscript has type &#39;char&#39;
-    return type defaults to &#39;int&#39;
-    control reaches end of non-void function
-    value computed is not used</code></pre>
+<blockquote>
+<p>suggest parentheses around <code>+</code> or <code>-</code> in operand of <code>&amp;</code><br>
+array subscript has type ‘<code>char</code>’<br>
+return type defaults to ‘<code>int</code>’<br>
+control reaches end of non-void function<br>
+value computed is not used</p>
+</blockquote>
 <p>The <code>value computed is not used</code> warning happens because I use the <code>&amp;&amp;</code>
 operator and take advantage of short circuit evaluation instead of using
 an <code>if()</code> statement.</p>
@@ -578,7 +580,7 @@ eliminate them and that can’t be done given the size limit.</p>
 appropriate sportsmanship for a program of this genre and can think of
 no worse job than trying to find an elusive bug in an intentionally
 obfuscated program.</p>
-<p>[Judge’s note: This was followed by a description of the bug, and
+<p>[<strong>Judges’ note</strong>: This was followed by a description of the bug, and
 the comment:]</p>
 <p>Note, if this program wins, the author thinks it would be good to leave
 this information out of the remarks and encourage others to try and
@@ -164,8 +164,8 @@ expected, and one more I is appended to the row.) Let's call it

 Some explanations:
 - The tape alphabet is always O and I.
- The states can be anything starting with "st". "start" and
-"stop" are the start and stop states, respectively.
+- The states can be anything starting with "`st`". "`start`" and
+"`stop`" are the start and stop states, respectively.
 - To define a state, use two lines: one for each letter on the
 tape. You may omit one of the lines if the Turing machine will
 never enter the state reading that letter. (In the example, the
@@ -220,13 +220,13 @@ Tape:
            *
 ```

-and the return code will be 1. As you can see, the Turing machine
+and the return code will be `1`. As you can see, the Turing machine
 moved over the `O`s, but when it arrived at the `I` (still in state
 start), the error occurred.

 Note that other kinds of errors can cause compilation to fail.
 If this happens, the build script will write the error message of
-gcc into a file called `error` and then exit.
+`gcc` into a file called `error` and then exit.


 ### What the build script does
@@ -238,7 +238,7 @@ beginning of the program; this is where the animation takes place
 (except in the first and last few steps).

 However, there's a technical problem to overcome: Some compilers
-(including gcc) insert a lot of white space during the
+(including `gcc`) insert a lot of white space during the
 preprocessing. This is bad for two reasons. First, the animated
 picture won't look right. And second, after some time, the file
 will grow too big for your hard disk. (The amount of white space
@@ -246,12 +246,12 @@ grows exponentially.) So after each preprocessing, the first thing
 the build script does is remove all the unnecessary white space
 using `sed`.

-(gcc would even insert `#line` directives if I didn't suppress
+(`gcc` would even insert `#line` directives if I didn't suppress
 them with the `-P` option.)

 ### Some more details

- The arguments passed to the build script are passed on to gcc
+- The arguments passed to the build script are passed on to `gcc`
 with a `-D` before. I had a slight technical problem doing this
 (especially with the spaces that can appear within the tape
 argument). That made the build script a bit longer.
@@ -266,8 +266,8 @@ lines of code.)
 `herrmann1-2.c` are generated.

 - Also, a file `error` is generated. This file is removed after
-the compilation, except if gcc produced an error; then it contains
-the error message. (I can't let gcc output all its messages
+the compilation, except if `gcc` produced an error; then it contains
+the error message. (I can't let `gcc` output all its messages
 directly, because the warnings would clobber the animation. I
 could have made the compile script output the error file in case
 of an error, but I didn't want to make it yet longer.)
@@ -318,9 +318,10 @@ to use many variables more than once.

 - I couldn't refrain from doing a little bit of nasty stuff like

-                #define a 0&0
-                #if !a
-
+``` <!---c-->
+    #define a 0&0
+    #if !a
+```
    Of course, it is a bit more subtle, and even useful.

 - The layout of the source code..., well, let's call it the
@@ -330,9 +331,9 @@ indenting and modern art. There are even some comments...

 ### Compatibility

- It works with many versions of gcc. I tested it with versions
+- It works with many versions of `gcc`. I tested it with versions
 2.7.2.1, 2.8.1, 2.95.2, and ecgs-2.91.66. However, an old version
-of gcc produced "internal compiler errors" (obviously not my
+of `gcc` produced "internal compiler errors" (obviously not my
 fault).

 - The only warnings I get tell me that I'm undefining `__FILE__` and
@@ -356,21 +357,25 @@ script, so that one does not have to choose "preprocess" from
 the menu over and over again. I leave this as an exercise to the
 experienced Mac programmer.)

- In the build script, I passed the `-P` option to gcc to suppress
+- In the build script, I passed the `-P` option to `gcc` to suppress
 the insertion of `#line` directives. If your compiler doesn't
 support this option (and does insert `#line` directives), you
 should change the call to `sed` to remove them, too: Add

-            -e "/^#line/ d"
+``` <!---sed-->
+    -e "/^#line/ d"
+```

-    to the sed parameters. Or, if your `#line` directives look like
-
-            # 15 "filename"
+    to the `sed` parameters. Or, if your `#line` directives look like

+``` <!---c-->
+    # 15 "filename"
+```
    add

-            -e "/^# [0-9]/ d"
-
+``` <!---sed-->
+    -e "/^# [0-9]/ d"
+```
    instead.

 - First, I had `-ansi -pedantic` turned on, but on some systems,
@@ -511,8 +511,8 @@ expected, and one more I is appended to the row.) Let’s call it
    #define st2_O   I, left, stop</code></pre>
 <p>Some explanations:
 - The tape alphabet is always O and I.
- The states can be anything starting with “st”. “start” and
-“stop” are the start and stop states, respectively.
+- The states can be anything starting with “<code>st</code>”. “<code>start</code>” and
+“<code>stop</code>” are the start and stop states, respectively.
 - To define a state, use two lines: one for each letter on the
 tape. You may omit one of the lines if the Turing machine will
 never enter the state reading that letter. (In the example, the
@@ -541,12 +541,12 @@ line</p>
 <pre><code>            *
    ..OOOOOOOOIIIIOO..
            *</code></pre>
-<p>and the return code will be 1. As you can see, the Turing machine
+<p>and the return code will be <code>1</code>. As you can see, the Turing machine
 moved over the <code>O</code>s, but when it arrived at the <code>I</code> (still in state
 start), the error occurred.</p>
 <p>Note that other kinds of errors can cause compilation to fail.
 If this happens, the build script will write the error message of
-gcc into a file called <code>error</code> and then exit.</p>
+<code>gcc</code> into a file called <code>error</code> and then exit.</p>
 <h3 id="what-the-build-script-does">What the build script does</h3>
 <p>In principle, the build script simply runs the preprocessor over
 and over again, until nothing changes anymore; then, the program
@@ -554,18 +554,18 @@ is compiled. After each preprocessing step, the script outputs the
 beginning of the program; this is where the animation takes place
 (except in the first and last few steps).</p>
 <p>However, there’s a technical problem to overcome: Some compilers
-(including gcc) insert a lot of white space during the
+(including <code>gcc</code>) insert a lot of white space during the
 preprocessing. This is bad for two reasons. First, the animated
 picture won’t look right. And second, after some time, the file
 will grow too big for your hard disk. (The amount of white space
 grows exponentially.) So after each preprocessing, the first thing
 the build script does is remove all the unnecessary white space
 using <code>sed</code>.</p>
-<p>(gcc would even insert <code>#line</code> directives if I didn’t suppress
+<p>(<code>gcc</code> would even insert <code>#line</code> directives if I didn’t suppress
 them with the <code>-P</code> option.)</p>
 <h3 id="some-more-details">Some more details</h3>
 <ul>
-<li><p>The arguments passed to the build script are passed on to gcc
+<li><p>The arguments passed to the build script are passed on to <code>gcc</code>
 with a <code>-D</code> before. I had a slight technical problem doing this
 (especially with the spaces that can appear within the tape
 argument). That made the build script a bit longer.</p></li>
@@ -577,8 +577,8 @@ lines of code.)</p></li>
 <li><p>During the preprocessing, intermediate files <code>herrmann1-1.c</code> and
 <code>herrmann1-2.c</code> are generated.</p></li>
 <li><p>Also, a file <code>error</code> is generated. This file is removed after
-the compilation, except if gcc produced an error; then it contains
-the error message. (I can’t let gcc output all its messages
+the compilation, except if <code>gcc</code> produced an error; then it contains
+the error message. (I can’t let <code>gcc</code> output all its messages
 directly, because the warnings would clobber the animation. I
 could have made the compile script output the error file in case
 of an error, but I didn’t want to make it yet longer.)</p></li>
@@ -620,19 +620,21 @@ produced, etc. If you want a real challenge, try to understand
 what the line <code>w j k(P ## x)</code> does.</p></li>
 <li><p>Due to the fact that our alphabet has only 53 ;-) letters, I had
 to use many variables more than once.</p></li>
-<li><p>I couldn’t refrain from doing a little bit of nasty stuff like</p>
-<pre><code>      #define a 0&amp;0
-      #if !a</code></pre>
-<p>Of course, it is a bit more subtle, and even useful.</p></li>
-<li><p>The layout of the source code…, well, let’s call it the
+<li><p>I couldn’t refrain from doing a little bit of nasty stuff like</p></li>
+</ul>
+<pre><code>    #define a 0&amp;0
+    #if !a</code></pre>
+<p>Of course, it is a bit more subtle, and even useful.</p>
+<ul>
+<li>The layout of the source code…, well, let’s call it the
 “modern art of programming” - a mixture of program-like
-indenting and modern art. There are even some comments…</p></li>
+indenting and modern art. There are even some comments…</li>
 </ul>
 <h3 id="compatibility">Compatibility</h3>
 <ul>
-<li><p>It works with many versions of gcc. I tested it with versions
+<li><p>It works with many versions of <code>gcc</code>. I tested it with versions
 2.7.2.1, 2.8.1, 2.95.2, and ecgs-2.91.66. However, an old version
-of gcc produced “internal compiler errors” (obviously not my
+of <code>gcc</code> produced “internal compiler errors” (obviously not my
 fault).</p></li>
 <li><p>The only warnings I get tell me that I’m undefining <code>__FILE__</code> and
 that preprocessing directives are not recognized within macro
@@ -652,16 +654,18 @@ to write a kind of script which does the equivalent to the build
 script, so that one does not have to choose “preprocess” from
 the menu over and over again. I leave this as an exercise to the
 experienced Mac programmer.)</p></li>
-<li><p>In the build script, I passed the <code>-P</code> option to gcc to suppress
+<li><p>In the build script, I passed the <code>-P</code> option to <code>gcc</code> to suppress
 the insertion of <code>#line</code> directives. If your compiler doesn’t
 support this option (and does insert <code>#line</code> directives), you
-should change the call to <code>sed</code> to remove them, too: Add</p>
-<pre><code>  -e &quot;/^#line/ d&quot;</code></pre>
-<p>to the sed parameters. Or, if your <code>#line</code> directives look like</p>
-<pre><code>  # 15 &quot;filename&quot;</code></pre>
+should change the call to <code>sed</code> to remove them, too: Add</p></li>
+</ul>
+<pre><code>    -e &quot;/^#line/ d&quot;</code></pre>
+<p>to the <code>sed</code> parameters. Or, if your <code>#line</code> directives look like</p>
+<pre><code>    # 15 &quot;filename&quot;</code></pre>
 <p>add</p>
-<pre><code>  -e &quot;/^# [0-9]/ d&quot;</code></pre>
-<p>instead.</p></li>
+<pre><code>    -e &quot;/^# [0-9]/ d&quot;</code></pre>
+<p>instead.</p>
+<ul>
 <li><p>First, I had <code>-ansi -pedantic</code> turned on, but on some systems,
 the <code>stdio.h</code> is not compatible to that, so I turned it back off.</p></li>
 <li><p>The build script probably needs a bash to run in. So perhaps you
@@ -117,14 +117,6 @@ the game entertaining, see if you can find
 in the source code.)


-### NOTICE to those who wish for a greater challenge:
-
-**If you want a greater challenge, don't read any further**:
-just try to understand the program via the source.
-
-If you get stuck, come back and read below for additional hints and information.
-
-
 ### GAME STRATEGY

 The trick, of course, is to drop items in empty rooms to mark them.  That way
@@ -487,10 +487,6 @@ the game entertaining, see if you can find</p>
 <pre><code>    the fish scales              Q)++j&lt;
    the shooting star         -~- ~ -~i +</code></pre>
 <p>in the source code.)</p>
-<h3 id="notice-to-those-who-wish-for-a-greater-challenge">NOTICE to those who wish for a greater challenge:</h3>
-<p><strong>If you want a greater challenge, don’t read any further</strong>:
-just try to understand the program via the source.</p>
-<p>If you get stuck, come back and read below for additional hints and information.</p>
 <h3 id="game-strategy">GAME STRATEGY</h3>
 <p>The trick, of course, is to drop items in empty rooms to mark them. That way
 you usually know if you’re in a room you’ve seen before. It greatly aids
@@ -5,7 +5,7 @@
 ```

 There is another version which lets you use the arrow keys rather than the more
-awkward `,` and `.` keys. See [alternate code](#alternate-code) below.
+awkward `,` and `.` keys. See [Alternate code](#alternate-code) below.


 ### Bugs and (Mis)features:
@@ -25,7 +25,7 @@ For more detailed information see [2001/kev in bugs.html](../../bugs.html#2001_k
    ./kev hostname # in another terminal
 ```

-NOTE: each player's paddle is at the bottom and the opponent at the top.
+**NOTE**: each player's paddle is at the bottom and the opponent at the top.


 ## Try:
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#AU">AU</a> - <em>Commonwealth of Australi
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
 <p>There is another version which lets you use the arrow keys rather than the more
-awkward <code>,</code> and <code>.</code> keys. See <a href="#alternate-code">alternate code</a> below.</p>
+awkward <code>,</code> and <code>.</code> keys. See <a href="#alternate-code">Alternate code</a> below.</p>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
 <p>The current status of this entry is:</p>
 <blockquote>
@@ -421,7 +421,7 @@ awkward <code>,</code> and <code>.</code> keys. See <a href="#alternate-code">al
 <pre><code>    ./kev # in one terminal

    ./kev hostname # in another terminal</code></pre>
-<p>NOTE: each player’s paddle is at the bottom and the opponent at the top.</p>
+<p><strong>NOTE</strong>: each player’s paddle is at the bottom and the opponent at the top.</p>
 <h2 id="try">Try:</h2>
 <pre><code>    ./kev                   # in one terminal

@@ -64,36 +64,34 @@ Q: Are there types of entries that are submitted so frequently that the
 A: Yes, there are types of entries that show up over and over again.
   The guidelines say:

-```
-    We tend to dislike programs that:
-    are similar to previous winning entries
-
-    We like variety. However too often we see (please look at the winning
-    examples given to be aware of the level of the competition):
-
-    (snip)
-
-    generating small primes (below is the list of all prime related entries)
-
-            1985/august
-            1988/applin
-            1994/weisberg
-            1995/makarios
-            1996/dalbec
-            2000/bellard
-
-    As you can see, just a list of primes (let alone small primes)
-    does not cut it anymore.
-
-    (snip)
-
-    entries that use some complex state machine/table to print something
-
-              1988/isaak
-              1988/phillipps
-
-    Unbeaten for 12 years and counting...
-```
+> We tend to dislike programs that:<br>
+> &nbsp;&nbsp;&nbsp;&nbsp;are similar to previous winning entries<br>
+>
+> We like variety. However too often we see (please look at the winning examples
+given to be aware of the level of the competition):
+>
+>    (snip)<br>
+>
+> generating small primes (below is the list of all prime related entries)<br>
+>
+> 1985/august<br>
+> 1988/applin<br>
+> 1994/weisberg<br>
+> 1995/makarios<br>
+> 1996/dalbec<br>
+> 2000/bellard<br>
+>
+>    As you can see, just a list of primes (let alone small primes) does not cut
+it anymore.
+>
+>    (snip)<br>
+>
+> entries that use some complex state machine/table to print something
+>
+> 1988/isaak<br>
+> 1988/phillipps
+>
+> Unbeaten for 12 years and counting...

 I think this is enough motivation for trying to submit a program which uses
 some complex state machine/table to generate small primes and print them.
@@ -114,7 +112,9 @@ guarantee a constant time.

 The main loop simply iterates this transition function on each cell.

-"The rest is silence" (Hamlet, V.2)
+> "The rest is silence"<br>
+>
+> (Hamlet, V.2)

 Enjoy!

@@ -441,34 +441,27 @@ character printed on the screen.</p>
 judges get tired of them?</p>
 <p>A: Yes, there are types of entries that show up over and over again.
 The guidelines say:</p>
-<pre><code>    We tend to dislike programs that:
-    are similar to previous winning entries
-
-    We like variety. However too often we see (please look at the winning
-    examples given to be aware of the level of the competition):
-
-    (snip)
-
-    generating small primes (below is the list of all prime related entries)
-
-            1985/august
-            1988/applin
-            1994/weisberg
-            1995/makarios
-            1996/dalbec
-            2000/bellard
-
-    As you can see, just a list of primes (let alone small primes)
-    does not cut it anymore.
-
-    (snip)
-
-    entries that use some complex state machine/table to print something
-
-              1988/isaak
-              1988/phillipps
-
-    Unbeaten for 12 years and counting...</code></pre>
+<blockquote>
+<p>We tend to dislike programs that:<br>
+    are similar to previous winning entries<br></p>
+<p>We like variety. However too often we see (please look at the winning examples
+given to be aware of the level of the competition):</p>
+<p>(snip)<br></p>
+<p>generating small primes (below is the list of all prime related entries)<br></p>
+<p>1985/august<br>
+1988/applin<br>
+1994/weisberg<br>
+1995/makarios<br>
+1996/dalbec<br>
+2000/bellard<br></p>
+<p>As you can see, just a list of primes (let alone small primes) does not cut
+it anymore.</p>
+<p>(snip)<br></p>
+<p>entries that use some complex state machine/table to print something</p>
+<p>1988/isaak<br>
+1988/phillipps</p>
+<p>Unbeaten for 12 years and counting…</p>
+</blockquote>
 <p>I think this is enough motivation for trying to submit a program which uses
 some complex state machine/table to generate small primes and print them.</p>
 <h3 id="the-way-it-works">The way it works</h3>
@@ -482,7 +475,10 @@ by <a href="http://richardallenfischer.com">Fischer</a> in 1965.</p>
 is obfuscated to reduce its size, restrict it to characters 32 to 127 and
 guarantee a constant time.</p>
 <p>The main loop simply iterates this transition function on each cell.</p>
-<p>“The rest is silence” (Hamlet, V.2)</p>
+<blockquote>
+<p>“The rest is silence”<br></p>
+<p>(Hamlet, V.2)</p>
+</blockquote>
 <p>Enjoy!</p>
 <!--

@@ -4,7 +4,7 @@
    make
 ```

-NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
+**NOTE**: this entry requires the `X11/Xlib.h` header file and the X11 library to
 compile.  For more information see the
 FAQ on "[X11](../../faq.html#X11)".

@@ -13,7 +13,8 @@ FAQ on "[X11](../../faq.html#X11)".

 The current status of this entry is:

-> **STATUS: missing files - please provide them**
+> **STATUS: INABIAF - please DO NOT fix**<br>
+> **STATUS: missing files - please provide them**<br>

 For more detailed information see [2001/rosten in bugs.html](../../bugs.html#2001_rosten).

@@ -24,10 +25,10 @@ For more detailed information see [2001/rosten in bugs.html](../../bugs.html#200
    ./rosten [number]
 ```

-WARNING: this will mess with your mouse and can make it hard to quit the
+**WARNING**: this will mess with your mouse and can make it hard to quit the
 program.  Use at your own risk.

-NOTE: number is floating point.
+**NOTE**: number is floating point.


 ## Try:
@@ -108,7 +109,9 @@ like this:
    greasymouse.c:58: This program is rubbish. I'm not going to link it.
 ```

-The code is best viewed with [tab stops](https://en.wikipedia.org/wiki/Tab_stop) every 8 spaces.
+The code is best viewed with [tab stops](https://en.wikipedia.org/wiki/Tab_stop)
+every 8 spaces. If you use `vi(m)` see the
+FAQ on "[tab stops](../../faq.html#tabstops)".


 ### BUGS
@@ -409,20 +409,21 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
 <!-- BEFORE: 1st line of markdown file: 2001/rosten/README.md -->
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
-<p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
+<p><strong>NOTE</strong>: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
 compile. For more information see the
 FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
 <p>The current status of this entry is:</p>
 <blockquote>
-<p><strong>STATUS: missing files - please provide them</strong></p>
+<p><strong>STATUS: INABIAF - please DO NOT fix</strong><br>
+<strong>STATUS: missing files - please provide them</strong><br></p>
 </blockquote>
 <p>For more detailed information see <a href="../../bugs.html#2001_rosten">2001/rosten in bugs.html</a>.</p>
 <h2 id="to-use">To use:</h2>
 <pre><code>    ./rosten [number]</code></pre>
-<p>WARNING: this will mess with your mouse and can make it hard to quit the
+<p><strong>WARNING</strong>: this will mess with your mouse and can make it hard to quit the
 program. Use at your own risk.</p>
-<p>NOTE: number is floating point.</p>
+<p><strong>NOTE</strong>: number is floating point.</p>
 <h2 id="try">Try:</h2>
 <pre><code>    ./rosten 1.03
    ./rosten 1.00</code></pre>
@@ -464,7 +465,9 @@ like this:</p>
    greasymouse.c:55: So is that
    ...
    greasymouse.c:58: This program is rubbish. I&#39;m not going to link it.</code></pre>
-<p>The code is best viewed with <a href="https://en.wikipedia.org/wiki/Tab_stop">tab stops</a> every 8 spaces.</p>
+<p>The code is best viewed with <a href="https://en.wikipedia.org/wiki/Tab_stop">tab stops</a>
+every 8 spaces. If you use <code>vi(m)</code> see the
+FAQ on “<a href="../../faq.html#tabstops">tab stops</a>”.</p>
 <h3 id="bugs">BUGS</h3>
 <p>The mouse gets stuck completely if you give it an option of less
 than 1 and leave it for too long. This is quite annoying if it
@@ -28,13 +28,6 @@ comments for details and a workaround.

 There's also no way to escape meta characters.

-This is supposed to happen.  As is written in the
-[The Jargon File](http://catb.org/jargon/html/F/feature.html):
-
-```
-    That's not a bug, that's a feature.
-```
-

 ## Try:

@@ -422,9 +422,6 @@ two args.</p>
 <p>Note also that the glob pattern must match the whole string. See the author’s
 comments for details and a workaround.</p>
 <p>There’s also no way to escape meta characters.</p>
-<p>This is supposed to happen. As is written in the
-<a href="http://catb.org/jargon/html/F/feature.html">The Jargon File</a>:</p>
-<pre><code>    That&#39;s not a bug, that&#39;s a feature.</code></pre>
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
@@ -101,7 +101,7 @@ versions of the program, all valid C!
 ## Author's remarks:

 [Punch cards](https://en.wikipedia.org/wiki/Punched_card), or Hollerith cards,
-were becoming obsolete just as C was becoming more popular\*; this is rather
+were becoming obsolete just as C was becoming more popular[^1]; this is rather
 unfortunate, because C has an advantage over many other languages when it comes
 to punch cards - C programs can be written to be "drop proof".

@@ -117,7 +117,7 @@ Consider the following C program:
 This program will compile and run no matter what order the
 lines are in.  If you punch it on cards (one line of code per
 card, naturally) and drop them, you don't need to put them in
-any particular order\*\*; it will always produce `ABC` as output.
+any particular order[^2]; it will always produce `ABC` as output.

 You can also use global variables:

@@ -224,11 +224,9 @@ comment), there are technically `28!` different programs, or
 `304,888,344,611,713,860,501,504,000,000` different versions,
 all legal C.

-```
-    * except in Florida voting machines
+[^1]: except in Florida voting machines

-    ** all cards must be face down, nine-edge first, of course.
-```
+[^2]: all cards must be face down, nine-edge first, of course.


 <!--
@@ -461,7 +461,7 @@ blank lines) there are <code>28!</code> or <code>304,888,344,611,713,860,501,504
 versions of the program, all valid C!</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p><a href="https://en.wikipedia.org/wiki/Punched_card">Punch cards</a>, or Hollerith cards,
-were becoming obsolete just as C was becoming more popular*; this is rather
+were becoming obsolete just as C was becoming more popular<a href="#fn1" class="footnote-ref" id="fnref1" role="doc-noteref"><sup>1</sup></a>; this is rather
 unfortunate, because C has an advantage over many other languages when it comes
 to punch cards - C programs can be written to be “drop proof”.</p>
 <p>Consider the following C program:</p>
@@ -472,7 +472,7 @@ to punch cards - C programs can be written to be “drop proof”.</p>
 <p>This program will compile and run no matter what order the
 lines are in. If you punch it on cards (one line of code per
 card, naturally) and drop them, you don’t need to put them in
-any particular order**; it will always produce <code>ABC</code> as output.</p>
+any particular order<a href="#fn2" class="footnote-ref" id="fnref2" role="doc-noteref"><sup>2</sup></a>; it will always produce <code>ABC</code> as output.</p>
 <p>You can also use global variables:</p>
 <pre><code>    char *greet = &quot;Hello, world!&quot;;
    char *greet; main(){puts(greet);}</code></pre>
@@ -553,9 +553,6 @@ actually shorter than the trigraph version of <code>a??(b??)</code>.</p>
 comment), there are technically <code>28!</code> different programs, or
 <code>304,888,344,611,713,860,501,504,000,000</code> different versions,
 all legal C.</p>
-<pre><code>    * except in Florida voting machines
-
-    ** all cards must be face down, nine-edge first, of course.</code></pre>
 <!--

    Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
@@ -570,6 +567,14 @@ all legal C.</p>

 -->
 <!-- AFTER: last line of markdown file: 2001/westley/README.md -->
+<hr style="width:10%;text-align:left;margin-left:0">
+<section id="footnotes" class="footnotes footnotes-end-of-document" role="doc-endnotes">
+<h5>Footnotes</h5>
+<ol>
+<li id="fn1"><p>except in Florida voting machines<a href="#fnref1" class="footnote-back" role="doc-backlink">↩︎</a></p></li>
+<li id="fn2"><p>all cards must be face down, nine-edge first, of course.<a href="#fnref2" class="footnote-back" role="doc-backlink">↩︎</a></p></li>
+</ol>
+</section>

 <!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
 <!-- START: this line starts content for HTML phase 22 by: bin/output-index-inventory.sh via bin/md2html.sh -->
@@ -4,7 +4,7 @@
    make
 ```

-NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
+**NOTE**: this entry requires the `X11/Xlib.h` header file and the X11 library to
 compile.  For more information see the
 FAQ on "[X11](../../faq.html#X11)".

@@ -409,7 +409,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <!-- BEFORE: 1st line of markdown file: 2001/williams/README.md -->
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
-<p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
+<p><strong>NOTE</strong>: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
 compile. For more information see the
 FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
@@ -1938,22 +1938,14 @@ elves of Imladris :-(</p>
 <h2 id="bellard">2001/bellard</h2>
 </div>
 <h3 id="status-inabiaf---please-do-not-fix-36">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
-<h3 id="status-doesnt-work-with-some-platforms---please-help-us-fix-it">STATUS: doesn’t work with some platforms - please help us fix it</h3>
 <h3 id="source-code-2001bellardbellard.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/bellard/bellard.c">2001/bellard/bellard.c</a></h3>
 <h3 id="information-2001bellardindex.html">Information: <a href="2001/bellard/index.html">2001/bellard/index.html</a></h3>
-<p>The two statuses might seem contradictory but that is a complicated question.
-The author stated that it only works with i386 linux so on the one hand the fact
-it doesn’t work in modern systems is considered a feature and not a bug. But on
-the other hand it would be nice if there was an alternate version which worked
-for modern systems. This does seem quite unlikely but some fixes, described
-next, were made.</p>
+<p>The author stated that it only works with i386 linux so the fact it doesn’t work
+in modern systems is considered a feature and not a bug.</p>
 <p><a href="authors.html#Cody_Boone_Ferguson">Cody Boone Ferguson</a> fixed an initial
 segfault (trying to open the file) and he also fixed the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/bellard/bellard.otccex.c">supplementary program
 bellard.otccex.c</a> but this still crashes in
 systems not i386 linux which is what the author stated.</p>
-<p>On the other hand if you do have a fix for 64-bit systems you’re welcome to
-provide it as an alternate version. If by chance you have a fix so that it works
-for both 32-bit and 64-bit systems that is also okay.</p>
 <p>The author said that they compiled it with <a href="https://ftp.gnu.org/gnu/gcc/gcc-2.95.2/gcc-everything-2.95.2.tar.gz">gcc version
 2.95.2</a>. We
 don’t know if a certain gcc version is necessary but it might be helpful to
@@ -1968,12 +1960,9 @@ explicitly stated that it requires i386 linux.</p>
 modification by Yusuke noted in the <a href="thanks-for-help.html">thanks</a>
 file) but it appears this <em>also</em> requires i386 linux; indeed looking at the code
 it hard codes paths that are i386 specific to linux.</p>
-<p>Another point of interest is that the author provided de-obfuscated versions
+<p>Another point of interest is that the author provided unobfuscated versions
 which might be of value to look at.</p>
-<p>If you have a fix for 64-bit systems this is welcome as an alternate version, as
-stated above. You might like to look at the otccelf version but note that it (at
-least in 64-bit linux and macOS) has compilation errors.</p>
-<h3 id="aside-why-were-there-changes-made-if-inabiaf">Aside: why were there changes made if INABIAF ?</h3>
+<h4 id="aside-why-were-there-changes-made-if-inabiaf">Aside: why were there changes made if INABIAF ?</h4>
 <p>This is a good question. The reason is we believe it better to fix some obvious
 problems: there were some bugs that would very possibly prevent it from working
 even if it was in i386 linux though Yusuke seemed to get it to work in an
@@ -2040,20 +2029,23 @@ provide enough args.</p>
 <div id="2001_rosten">
 <h2 id="rosten">2001/rosten</h2>
 </div>
-<h3 id="status-missing-files---please-provide-them-1">STATUS: missing files - please provide them</h3>
+<h3 id="status-inabiaf---please-do-not-fix-41">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2001rostenrosten.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/rosten/rosten.c">2001/rosten/rosten.c</a></h3>
 <h3 id="information-2001rostenindex.html">Information: <a href="2001/rosten/index.html">2001/rosten/index.html</a></h3>
+<p>See list of bugs <a href="2001/rosten/index.html#bugs">here</a>.</p>
+<h3 id="status-missing-files---please-provide-them-1">STATUS: missing files - please provide them</h3>
 <p>The author stated that there is a cat man page for this program in case one
 wanted to install it as a tool but this is missing.</p>
 <div id="2001_schweikh">
 <h2 id="schweikh">2001/schweikh</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-41">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-42">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2001schweikhschweikh.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/schweikh.c">2001/schweikh/schweikh.c</a></h3>
 <h3 id="information-2001schweikhindex.html">Information: <a href="2001/schweikh/index.html">2001/schweikh/index.html</a></h3>
 <p>The glob pattern must match the whole string. See the author’s comments for
 details and a workaround.</p>
 <p>There’s also no way to escape meta characters.</p>
+<p>See also the author’s list of bugs <a href="2001/schweikh/index.html#bugs">here</a>.</p>
 <div id="2001_westley">
 <h2 id="westley-4">2001/westley</h2>
 </div>
@@ -2134,7 +2126,7 @@ sleeping.</p>
 <h2 id="gavin">2004/gavin</h2>
 </div>
 <h3 id="status-compiled-executable-crashes---please-help-us-fix">STATUS: compiled executable crashes - please help us fix</h3>
-<h3 id="status-doesnt-work-with-some-platforms---please-help-us-fix-it-1">STATUS: doesn’t work with some platforms - please help us fix it</h3>
+<h3 id="status-doesnt-work-with-some-platforms---please-help-us-fix-it">STATUS: doesn’t work with some platforms - please help us fix it</h3>
 <h3 id="source-code-2004gavingavin.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/gavin/gavin.c">2004/gavin/gavin.c</a></h3>
 <h3 id="information-2004gavinindex.html">Information: <a href="2004/gavin//index.html">2004/gavin//index.html</a></h3>
 <p>Segmentation fault will occur in some systems. For instance on macOS with the
@@ -2216,13 +2208,13 @@ compile under clang. The following patch was applied:</p>
    gavin_files: boot.b lilo.conf prim gavin_install.txt</code></pre>
 <p>The current (<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/gavin/Makefile">Makefile</a> was modified to try and
 fit into the current IOCCC build environment.</p>
-<h3 id="status-inabiaf---please-do-not-fix-42">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-43">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <p>See <a href="2004/gavin/index.html#known-features">known features in the index.html</a> for
 things that are not bugs but documented (mis)features.</p>
 <div id="2004_jdalbec">
 <h2 id="jdalbec">2004/jdalbec</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-43">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-44">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2004jdalbecjdalbec.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/jdalbec/jdalbec.c">2004/jdalbec/jdalbec.c</a></h3>
 <h3 id="information-2004jdalbecindex.html">Information: <a href="2004/jdalbec/index.html">2004/jdalbec/index.html</a></h3>
 <p>The author stated that:</p>
@@ -2247,7 +2239,7 @@ things that are not bugs but documented (mis)features.</p>
 <div id="2004_sds">
 <h2 id="sds">2004/sds</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-44">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-45">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2004sdssds.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/sds.c">2004/sds/sds.c</a></h3>
 <h3 id="information-2004sdsindex.html">Information: <a href="2004/sds/index.html">2004/sds/index.html</a></h3>
 <p>The generated code will very likely segfault or do something not intended if not
@@ -2260,7 +2252,7 @@ given the right args. See the index.html file for the correct syntax.</p>
 <div id="2005_anon">
 <h2 id="anon">2005/anon</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-45">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-46">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2005anonanon.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/anon/anon.c">2005/anon/anon.c</a></h3>
 <h3 id="information-2005anonindex.html">Information: <a href="2005/anon/index.html">2005/anon/index.html</a></h3>
 <p>This program sometimes will create unsolvable puzzles :-) just to hook you.
@@ -2274,7 +2266,7 @@ dimensions. Try <code>100 100 100</code> for instance and see what happens!</p>
 <div id="2005_giljade">
 <h2 id="giljade">2005/giljade</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-46">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-47">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2005giljadegiljade.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/giljade/giljade.c">2005/giljade/giljade.c</a></h3>
 <h3 id="information-2005giljadeindex.html">Information: <a href="2005/giljade/index.html">2005/giljade/index.html</a></h3>
 <p>This entry will very likely segfault or do something strange if the source code
@@ -2283,7 +2275,7 @@ does not exist.</p>
 <div id="2005_mikeash">
 <h2 id="mikeash">2005/mikeash</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-47">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-48">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2005mikeashmikeash.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/mikeash.c">2005/mikeash/mikeash.c</a></h3>
 <h3 id="information-2005mikeashindex.html">Information: <a href="2005/mikeash/index.html">2005/mikeash/index.html</a></h3>
 <p>The author states:</p>
@@ -2317,7 +2309,7 @@ for running itself.</p>
 <div id="2005_mynx">
 <h2 id="mynx">2005/mynx</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-48">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-49">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2005mynxmynx.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mynx/mynx.c">2005/mynx/mynx.c</a></h3>
 <h3 id="information-2005mynxindex.html">Information: <a href="2005/mynx/index.html">2005/mynx/index.html</a></h3>
 <p><a href="authors.html#Cody_Boone_Ferguson">Cody Boone Ferguson</a> notes that, though
@@ -2331,7 +2323,7 @@ website</a> itself.</p>
 <div id="2005_sykes">
 <h2 id="sykes">2005/sykes</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-49">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-50">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2005sykessykes.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/sykes/sykes.c">2005/sykes/sykes.c</a></h3>
 <h3 id="information-2005sykesindex.html">Information: <a href="2005/sykes/index.html">2005/sykes/index.html</a></h3>
 <p>The author stated the below points of interest.</p>
@@ -2372,7 +2364,7 @@ with at least <code>computer.tofu</code> input file:</p>
 <div id="2006_borsanyi">
 <h2 id="borsanyi">2006/borsanyi</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-50">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-51">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2006borsanyiborsanyi.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/borsanyi/borsanyi.c">2006/borsanyi/borsanyi.c</a></h3>
 <h3 id="information-2006borsanyiindex.html">Information: <a href="2006/borsanyi/index.html">2006/borsanyi/index.html</a></h3>
 <p>The string specified must be &lt;= 42 characters and may only consist of the
@@ -2381,14 +2373,14 @@ with possibly corrupt GIF files.</p>
 <div id="2006_hamre">
 <h2 id="hamre">2006/hamre</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-51">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-52">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2006hamrehamre.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/hamre/hamre.c">2006/hamre/hamre.c</a></h3>
 <h3 id="information-2006hamreindex.html">Information: <a href="2006/hamre/index.html">2006/hamre/index.html</a></h3>
 <p>This program will likely crash or do something funny without an arg.</p>
 <div id="2006_monge">
 <h2 id="monge">2006/monge</h2>
 </div>
-<h3 id="status-doesnt-work-with-some-platforms---please-help-us-fix-it-2">STATUS: doesn’t work with some platforms - please help us fix it</h3>
+<h3 id="status-doesnt-work-with-some-platforms---please-help-us-fix-it-1">STATUS: doesn’t work with some platforms - please help us fix it</h3>
 <h3 id="source-code-2006mongemonge.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/monge/monge.c">2006/monge/monge.c</a></h3>
 <h3 id="information-2006mongeindex.html">Information: <a href="2006/monge/index.html">2006/monge/index.html</a></h3>
 <p>This program requires x86 (with an x87 FPU) or x86_64 machine and it requires
@@ -2400,12 +2392,12 @@ but you are welcome to try and fix it.</p>
 provide it as an additional alt version. Fixing this is very likely to be very
 challenging and in some systems it will not be possible to fix but you are
 welcome to try and fix it if you wish to!</p>
-<h3 id="status-inabiaf---please-do-not-fix-52">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-53">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <p>Incorrect formulas will ungracefully crash the program.</p>
 <div id="2006_stewart">
 <h2 id="stewart">2006/stewart</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-53">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-54">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2006stewartstewart.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/stewart/stewart.c">2006/stewart/stewart.c</a></h3>
 <h3 id="information-2006stewartindex.html">Information: <a href="2006/stewart/index.html">2006/stewart/index.html</a></h3>
 <p>This program will likely crash or do something funny if the file cannot be
@@ -2413,7 +2405,7 @@ opened. The number of args is however checked.</p>
 <div id="2006_sykes1">
 <h2 id="sykes1">2006/sykes1</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-54">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-55">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2006sykes1sykes1.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/sykes1/sykes1.c">2006/sykes1/sykes1.c</a></h3>
 <h3 id="information-2006sykes1index.html">Information: <a href="2006/sykes1/index.html">2006/sykes1/index.html</a></h3>
 <p>The author stated:</p>
@@ -2430,7 +2422,7 @@ opened. The number of args is however checked.</p>
 <div id="2006_toledo2">
 <h2 id="toledo2">2006/toledo2</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-55">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-56">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2006toledo2toledo2.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/toledo2/toledo2.c">2006/toledo2/toledo2.c</a></h3>
 <h3 id="information-2006toledo2index.html">Information: <a href="2006/toledo2/index.html">2006/toledo2/index.html</a></h3>
 <p><a href="authors.html#Cody_Boone_Ferguson">Cody Boone Ferguson</a> fixed this program to
@@ -2477,7 +2469,7 @@ case-sensitive.</p>
 <div id="2011_borsanyi">
 <h2 id="borsanyi-1">2011/borsanyi</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-56">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-57">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2011borsanyiborsanyi.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/borsanyi/borsanyi.c">2011/borsanyi/borsanyi.c</a></h3>
 <h3 id="information-2011borsanyiindex.html">Information: <a href="2011/borsanyi/index.html">2011/borsanyi/index.html</a></h3>
 <p>For a great amount of data points the program will crash, depending on your
@@ -2502,7 +2494,7 @@ for security in modern days!</strong>). Do you have a server with enough bandwid
 would like to set it up? We’ll gladly thank you in the <a href="thanks-for-help.html">thanks
 file</a> file and link to the page as well! You’ll also have
 IOCCC fame for reviving a pootifier! :-)</p>
-<h3 id="status-inabiaf---please-do-not-fix-57">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-58">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <p>The author states the following:</p>
 <ul>
 <li><p>Bad input (e.g. nonexistent files, non-numeric number of iterations, etc.)
@@ -2514,7 +2506,7 @@ tends to result in empty output.</p></li>
 <div id="2011_fredriksson">
 <h2 id="fredriksson">2011/fredriksson</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-58">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-59">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2011fredrikssonfredriksson.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/fredriksson/fredriksson.c">2011/fredriksson/fredriksson.c</a></h3>
 <h3 id="information-2011fredrikssonindex.html">Information: <a href="2011/fredriksson/index.html">2011/fredriksson/index.html</a></h3>
 <p>The author stated that there are a number of features and limitations. As the
@@ -2524,14 +2516,14 @@ remarks</a> instead.</p>
 <div id="2011_konno">
 <h2 id="konno">2011/konno</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-59">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-60">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2011konnokonno.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/konno/konno.c">2011/konno/konno.c</a></h3>
 <h3 id="information-2011konnoindex.html">Information: <a href="2011/konno/index.html">2011/konno/index.html</a></h3>
 <p>This program will very likely crash or do something funny without an arg.</p>
 <div id="2011_richards">
 <h2 id="richards">2011/richards</h2>
 </div>
-<h3 id="status-doesnt-work-with-some-platforms---please-help-us-fix-it-3">STATUS: doesn’t work with some platforms - please help us fix it</h3>
+<h3 id="status-doesnt-work-with-some-platforms---please-help-us-fix-it-2">STATUS: doesn’t work with some platforms - please help us fix it</h3>
 <h3 id="source-code-2011richardsrichards.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/richards/richards.c">2011/richards/richards.c</a></h3>
 <h3 id="information-2011richardsindex.html">Information: <a href="2011/richards/index.html">2011/richards/index.html</a></h3>
 <p>This does not appear to work with macOS, resulting in a segfault (and sometimes
@@ -2693,7 +2685,7 @@ defined.</p>
 <div id="2011_vik">
 <h2 id="vik">2011/vik</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-60">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-61">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2011vikvik.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/vik/vik.c">2011/vik/vik.c</a></h3>
 <h3 id="information-2011vikindex.html">Information: <a href="2011/vik/index.html">2011/vik/index.html</a></h3>
 <p>The author stated that the program will crash if no argument is passed to the
@@ -2707,7 +2699,7 @@ fire</a> :-)</p>
 <div id="2012_blakely">
 <h2 id="blakely">2012/blakely</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-61">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-62">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2012blakelyblakely.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/blakely/blakely.c">2012/blakely/blakely.c</a></h3>
 <h3 id="information-2012blakelyindex.html">Information: <a href="2012/blakely/index.html">2012/blakely/index.html</a></h3>
 <p>The author stated:</p>
@@ -2716,7 +2708,7 @@ fire</a> :-)</p>
 <div id="2012_deckmyn">
 <h2 id="deckmyn">2012/deckmyn</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-62">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-63">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2012deckmyndeckmyn.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/deckmyn/deckmyn.c">2012/deckmyn/deckmyn.c</a></h3>
 <h3 id="information-2012deckmynindex.html">Information: <a href="2012/deckmyn/index.html">2012/deckmyn/index.html</a></h3>
 <p>The author stated:</p>
@@ -2749,7 +2741,7 @@ fire</a> :-)</p>
 <div id="2012_dlowe">
 <h2 id="dlowe-3">2012/dlowe</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-63">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-64">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2012dlowedlowe.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/dlowe/dlowe.c">2012/dlowe/dlowe.c</a></h3>
 <h3 id="information-2012dloweindex.html">Information: <a href="2012/dlowe/index.html">2012/dlowe/index.html</a></h3>
 <p>The author stated:</p>
@@ -2763,7 +2755,7 @@ doesn’t make it possible to lock drawing to the display refresh rate.)</li>
 <div id="2012_tromp">
 <h2 id="tromp">2012/tromp</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-64">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-65">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2012tromptromp.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/tromp/tromp.c">2012/tromp/tromp.c</a></h3>
 <h3 id="information-2012trompindex.html">Information: <a href="2012/tromp/index.html">2012/tromp/index.html</a></h3>
 <p>The author stated:</p>
@@ -2784,7 +2776,7 @@ doesn’t make it possible to lock drawing to the display refresh rate.)</li>
 <div id="2012_vik">
 <h2 id="vik-1">2012/vik</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-65">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-66">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2012vikvik.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/vik.c">2012/vik/vik.c</a></h3>
 <h3 id="information-2012vikindex.html">Information: <a href="2012/vik/index.html">2012/vik/index.html</a></h3>
 <p>The author stated that the program will crash if no argument is passed to the
@@ -2800,7 +2792,7 @@ fire</a> :-)</p>
 <div id="2013_cable2">
 <h2 id="cable2">2013/cable2</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-66">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-67">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2013cable2cable2.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/cable2/cable2.c">2013/cable2/cable2.c</a></h3>
 <h3 id="information-2013cable2index.html">Information: <a href="2013/cable2/index.html">2013/cable2/index.html</a></h3>
 <p>The author stated:</p>
@@ -2820,7 +2812,7 @@ and endianness conversion would make the source too large for IOCCC rule 2).</li
 <div id="2013_dlowe">
 <h2 id="dlowe-4">2013/dlowe</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-67">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-68">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2013dlowedlowe.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/dlowe/dlowe.c">2013/dlowe/dlowe.c</a></h3>
 <h3 id="information-2013dloweindex.html">Information: <a href="2013/dlowe/index.html">2013/dlowe/index.html</a></h3>
 <p>This program will possibly crash or draw something strange with 0 args. Then
@@ -2839,7 +2831,7 @@ used.</li>
 <div id="2013_endoh1">
 <h2 id="endoh1">2013/endoh1</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-68">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-69">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2013endoh1endoh1.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/endoh1/endoh1.c">2013/endoh1/endoh1.c</a></h3>
 <h3 id="information-2013endoh1index.html">Information: <a href="2013/endoh1/index.html">2013/endoh1/index.html</a></h3>
 <p>From the author:</p>
@@ -2855,7 +2847,7 @@ used.</li>
 <div id="2013_endoh3">
 <h2 id="endoh3">2013/endoh3</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-69">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-70">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2013endoh3endoh3.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/endoh3/endoh3.c">2013/endoh3/endoh3.c</a></h3>
 <h3 id="information-2013endoh3index.html">Information: <a href="2013/endoh3/index.html">2013/endoh3/index.html</a></h3>
 <p>From the author:</p>
@@ -2868,14 +2860,14 @@ such as <code>C2E2</code>.</p>
 <div id="2013_endoh4">
 <h2 id="endoh4">2013/endoh4</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-70">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-71">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2013endoh4endoh4.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/endoh4/endoh4.c">2013/endoh4/endoh4.c</a></h3>
 <h3 id="information-2013endoh4index.html">Information: <a href="2013/endoh4/index.html">2013/endoh4/index.html</a></h3>
 <p>Invalid input files will very likely crash the program.</p>
 <div id="2013_hou">
 <h2 id="hou">2013/hou</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-71">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-72">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2013houhou.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/hou/hou.c">2013/hou/hou.c</a></h3>
 <h3 id="information-2013houindex.html">Information: <a href="2013/hou/index.html">2013/hou/index.html</a></h3>
 <p>This program will not terminate on its own; you must kill <code>hou</code> (but not Qiming
@@ -2883,7 +2875,7 @@ Hou :-) ) yourself. This should not be fixed.</p>
 <div id="2013_mills">
 <h2 id="mills">2013/mills</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-72">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-73">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2013millsmills.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/mills/mills.c">2013/mills/mills.c</a></h3>
 <h3 id="information-2013millsindex.html">Information: <a href="2013/mills/index.html">2013/mills/index.html</a></h3>
 <p>The author reminds us that if you kill the program you will have to wait a short
@@ -2900,7 +2892,7 @@ it out as a known limitation it is not a bug but a feature.</p>
 <div id="2014_maffiodo1">
 <h2 id="maffiodo1">2014/maffiodo1</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-73">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-74">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2014maffiodo1prog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/maffiodo1/prog.c">2014/maffiodo1/prog.c</a></h3>
 <h3 id="information-2014maffiodo1index.html">Information: <a href="2014/maffiodo1/index.html">2014/maffiodo1/index.html</a></h3>
 <p>The author noted that in macOS the colours might be wrong. They gave a solution.
@@ -2924,7 +2916,7 @@ player become bigger, stay away from blocks!</p>
 <div id="2014_maffiodo2">
 <h2 id="maffiodo2">2014/maffiodo2</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-74">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-75">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2014maffiodo2prog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/maffiodo2/prog.c">2014/maffiodo2/prog.c</a></h3>
 <h3 id="information-2014maffiodo2index.html">Information: <a href="2014/maffiodo2/index.html">2014/maffiodo2/index.html</a></h3>
 <p>This program will very likely crash if no arg is given.</p>
@@ -2965,7 +2957,7 @@ rely on the entry as the below shows. One should be able to do:</p>
 <div id="2015_hou">
 <h2 id="hou-1">2015/hou</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-75">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-76">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2015houprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2015/hou/prog.c">2015/hou/prog.c</a></h3>
 <h3 id="information-2015houindex.html">Information: <a href="2015/hou/index.html">2015/hou/index.html</a></h3>
 <p>The author stated:</p>
@@ -3009,7 +3001,7 @@ because it is the same thing as the other, just updated to use <code>prog.alt</c
 <div id="2015_mills2">
 <h2 id="mills2">2015/mills2</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-76">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-77">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2015mills2prog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2015/mills2/prog.c">2015/mills2/prog.c</a></h3>
 <h3 id="information-2015mills2index.html">Information: <a href="2015/mills2/index.html">2015/mills2/index.html</a></h3>
 <p>The program doesn’t look at the header of files so if it’s passed something hat
@@ -3018,7 +3010,7 @@ is not compressed data it’s likely to crash.</p>
 <div id="2015_schweikhardt">
 <h2 id="schweikhardt">2015/schweikhardt</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-77">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-78">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2015schweikhardtprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2015/schweikhardt/prog.c">2015/schweikhardt/prog.c</a></h3>
 <h3 id="information-2015schweikhardtindex.html">Information: <a href="2015/schweikhardt/index.html">2015/schweikhardt/index.html</a></h3>
 <p>The program assumes that <code>EOF</code> is <code>-1</code>. This can be fixed but at this time it is
@@ -3051,7 +3043,7 @@ use <code>8 * sizeof(typ)</code> bits per place. It does not work when <code>CHA
 <div id="2018_algmyr">
 <h2 id="algmyr">2018/algmyr</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-78">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-79">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2018algmyrprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/prog.c">2018/algmyr/prog.c</a></h3>
 <h3 id="information-2018algmyrindex.html">Information: <a href="2018/algmyr/index.html">2018/algmyr/index.html</a></h3>
 <p>The author wrote:</p>
@@ -3070,7 +3062,7 @@ loop printing whitespace.</li>
 <div id="2018_hou">
 <h2 id="hou-2">2018/hou</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-79">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-80">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2018houprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/hou/prog.c">2018/hou/prog.c</a></h3>
 <h3 id="information-2018houindex.html">Information: <a href="2018/hou/index.html">2018/hou/index.html</a></h3>
 <p>When you run it on a JSON file you will see something like:</p>
@@ -3095,7 +3087,7 @@ likely see:</p>
 <p>where <code>[]</code> is the cursor. When this happens if you hit enter (this is necessary
 or else it’ll happen again) and then exit again (ctrl-e) and run <code>prog</code> again
 it’ll be okay.</p>
-<h3 id="status-inabiaf---please-do-not-fix-80">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-81">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <p>The author stated that if you make a typo it can happen that the boot loader can
 crash and halt. If this is the case type ctrl-e to quit the emulator and try
 again.</p>
@@ -3110,7 +3102,7 @@ in the case of compiled code it won’t be executable).</p>
 <div id="2018_vokes">
 <h2 id="vokes">2018/vokes</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-81">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-82">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2018vokesprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/vokes/prog.c">2018/vokes/prog.c</a></h3>
 <h3 id="information-2018vokesindex.html">Information: <a href="2018/vokes/index.html">2018/vokes/index.html</a></h3>
 <p>The author wrote the following:</p>
@@ -3160,7 +3152,7 @@ this program has nothing to do with a hand.</p></li>
 <div id="2019_adamovsky">
 <h2 id="adamovsky">2019/adamovsky</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-82">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-83">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019adamovskyprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/prog.c">2019/adamovsky/prog.c</a></h3>
 <h3 id="information-2019adamovskyindex.html">Information: <a href="2019/adamovsky/index.html">2019/adamovsky/index.html</a></h3>
 <p>Certain input can crash this program. The file
@@ -3168,7 +3160,7 @@ this program has nothing to do with a hand.</p></li>
 <div id="2019_burton">
 <h2 id="burton">2019/burton</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-83">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-84">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019burtonprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/burton/prog.c">2019/burton/prog.c</a></h3>
 <h3 id="information-2019burtonindex.html">Information: <a href="2019/burton/index.html">2019/burton/index.html</a></h3>
 <p>The author pointed out that some implementations of <code>wc(1)</code> show different
@@ -3176,7 +3168,7 @@ values but his implementation matches that of macOS and FreeBSD.</p>
 <div id="2019_ciura">
 <h2 id="ciura">2019/ciura</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-84">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-85">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019ciuraprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/ciura/prog.c">2019/ciura/prog.c</a></h3>
 <h3 id="information-2019ciuraindex.html">Information: <a href="2019/ciura/index.html">2019/ciura/index.html</a></h3>
 <p><a href="authors.html#Cody_Boone_Ferguson">Cody Boone Ferguson</a> fixed the scripts so
@@ -3210,7 +3202,7 @@ for more information on the change to <code>fgets(3)</code>.</p>
 <div id="2019_duble">
 <h2 id="duble">2019/duble</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-85">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-86">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019dubleprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/prog.c">2019/duble/prog.c</a></h3>
 <h3 id="information-2019dubleindex.html">Information: <a href="2019/duble/index.html">2019/duble/index.html</a></h3>
 <p>There are two things to be aware of with this entry.</p>
@@ -3239,7 +3231,7 @@ in the directory:</p>
 <div id="2019_endoh">
 <h2 id="endoh">2019/endoh</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-86">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-87">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019endohprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/endoh/prog.c">2019/endoh/prog.c</a></h3>
 <h3 id="information-2019endohindex.html">Information: <a href="2019/endoh/index.html">2019/endoh/index.html</a></h3>
 <p>As a backtrace quine this entry is <strong>SUPPOSED to segfault</strong> so this should not be
@@ -3247,7 +3239,7 @@ touched either.</p>
 <div id="2019_karns">
 <h2 id="karns">2019/karns</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-87">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-88">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019karnsprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/karns/prog.c">2019/karns/prog.c</a></h3>
 <h3 id="information-2019karnsindex.html">Information: <a href="2019/karns/index.html">2019/karns/index.html</a></h3>
 <p>The author stated the following:</p>
@@ -3277,7 +3269,7 @@ touched either.</p>
 <div id="2019_lynn">
 <h2 id="lynn">2019/lynn</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-88">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-89">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019lynnprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/lynn/prog.c">2019/lynn/prog.c</a></h3>
 <h3 id="information-2019lynnindex.html">Information: <a href="2019/lynn/index.html">2019/lynn/index.html</a></h3>
 <p>The author wrote that there are a number of differences from what one might
@@ -3287,7 +3279,7 @@ remarks in the sections <a href="2019/lynn/index.html#syntax">Syntax</a> and
 <div id="2019_mills">
 <h2 id="mills-2">2019/mills</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-89">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-90">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019millsprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/mills/prog.c">2019/mills/prog.c</a></h3>
 <h3 id="information-2019millsindex.html">Information: <a href="2019/mills/index.html">2019/mills/index.html</a></h3>
 <p>The author wrote that if you decide to change networks or use a different input
@@ -3307,7 +3299,7 @@ a crash.</p>
 <div id="2019_poikola">
 <h2 id="poikola">2019/poikola</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-90">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-91">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019poikolaprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/poikola/prog.c">2019/poikola/prog.c</a></h3>
 <h3 id="information-2019poikolaindex.html">Information: <a href="2019/poikola/index.html">2019/poikola/index.html</a></h3>
 <p>This program will not validate input so it might fail or get stuck if invoked
@@ -3316,7 +3308,7 @@ erroneously.</p>
 <div id="2019_yang">
 <h2 id="yang">2019/yang</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-91">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-92">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2019yangprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/yang/prog.c">2019/yang/prog.c</a></h3>
 <h3 id="information-2019yangindex.html">Information: <a href="2019/yang/index.html">2019/yang/index.html</a></h3>
 <p>The author noted that if the program runs out of memory it is likely to crash.</p>
@@ -3331,7 +3323,7 @@ ignored except line feeds (preserved) and tabs (expanded to 8 spaces).’</p>
 <div id="2020_burton">
 <h2 id="burton-1">2020/burton</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-92">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-93">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2020burtonprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/burton/prog.c">2020/burton/prog.c</a></h3>
 <h3 id="information-2020burtonindex.html">Information: <a href="2020/burton/index.html">2020/burton/index.html</a></h3>
 <p>This entry is known to crash if no arg is specified. Although easy to fix it is
@@ -3342,7 +3334,7 @@ either. But can you figure out why this happens?</p>
 <div id="2020_carlini">
 <h2 id="carlini">2020/carlini</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-93">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-94">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2020carliniprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/carlini/prog.c">2020/carlini/prog.c</a></h3>
 <h3 id="information-2020carliniindex.html">Information: <a href="2020/carlini/index.html">2020/carlini/index.html</a></h3>
 <p>The author stated that bad things happen if the entered move is outside of the
@@ -3356,7 +3348,7 @@ move.</p>
 <div id="2020_ferguson1">
 <h2 id="ferguson1">2020/ferguson1</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-94">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-95">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2020ferguson1prog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson1/prog.c">2020/ferguson1/prog.c</a></h3>
 <h3 id="information-2020ferguson1index.html">Information: <a href="2020/ferguson1/index.html">2020/ferguson1/index.html</a></h3>
 <p>There are some things that might appear to be bugs but are actually features or
@@ -3366,7 +3358,7 @@ things that are misinterpreted as bugs. See the
 <div id="2020_giles">
 <h2 id="giles">2020/giles</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-95">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-96">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2020gilesprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/giles/prog.c">2020/giles/prog.c</a></h3>
 <h3 id="information-2020gilesindex.html">Information: <a href="2020/giles/index.html">2020/giles/index.html</a></h3>
 <p>The author noted that the program only supports WAV files that have
@@ -3375,7 +3367,7 @@ audio channels.</p>
 <div id="2020_otterness">
 <h2 id="otterness">2020/otterness</h2>
 </div>
-<h3 id="status-inabiaf---please-do-not-fix-96">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
+<h3 id="status-inabiaf---please-do-not-fix-97">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
 <h3 id="source-code-2020otternessprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/otterness/prog.c">2020/otterness/prog.c</a></h3>
 <h3 id="information-2020otternessindex.html">Information: <a href="2020/otterness/index.html">2020/otterness/index.html</a></h3>
 <p>The author listed the following limitations:</p>
@@ -2248,26 +2248,17 @@ elves of Imladris :-(
 </div>

 ### STATUS: INABIAF - please **DO NOT** fix
-### STATUS: doesn't work with some platforms - please help us fix it
 ### Source code: [2001/bellard/bellard.c](%%REPO_URL%%/2001/bellard/bellard.c)
 ### Information: [2001/bellard/index.html](2001/bellard/index.html)

-The two statuses might seem contradictory but that is a complicated question.
-The author stated that it only works with i386 linux so on the one hand the fact
-it doesn't work in modern systems is considered a feature and not a bug. But on
-the other hand it would be nice if there was an alternate version which worked
-for modern systems. This does seem quite unlikely but some fixes, described
-next, were made.
+The author stated that it only works with i386 linux so the fact it doesn't work
+in modern systems is considered a feature and not a bug.

 [Cody Boone Ferguson](authors.html#Cody_Boone_Ferguson) fixed an initial
 segfault (trying to open the file) and he also fixed the [supplementary program
 bellard.otccex.c](%%REPO_URL%%/2001/bellard/bellard.otccex.c) but this still crashes in
 systems not i386 linux which is what the author stated.

-On the other hand if you do have a fix for 64-bit systems you're welcome to
-provide it as an alternate version. If by chance you have a fix so that it works
-for both 32-bit and 64-bit systems that is also okay.
-
 The author said that they compiled it with [gcc version
 2.95.2](https://ftp.gnu.org/gnu/gcc/gcc-2.95.2/gcc-everything-2.95.2.tar.gz). We
 don't know if a certain gcc version is necessary but it might be helpful to
@@ -2286,15 +2277,11 @@ modification by Yusuke noted in the [thanks](thanks-for-help.html)
 file) but it appears this *also* requires i386 linux; indeed looking at the code
 it hard codes paths that are i386 specific to linux.

-Another point of interest is that the author provided de-obfuscated versions
+Another point of interest is that the author provided unobfuscated versions
 which might be of value to look at.

-If you have a fix for 64-bit systems this is welcome as an alternate version, as
-stated above. You might like to look at the otccelf version but note that it (at
-least in 64-bit linux and macOS) has compilation errors.

-
-### Aside: why were there changes made if INABIAF ?
+#### Aside: why were there changes made if INABIAF ?

 This is a good question. The reason is we believe it better to fix some obvious
 problems: there were some bugs that would very possibly prevent it from working
@@ -2307,6 +2294,7 @@ Also the supplementary program, which did not work at all, was fixed (by Cody)
 and it can be run by itself for fun in modern systems, which was not possible
 before the fixes there.

+
 <div id="2001_cheong">
 ## 2001/cheong
 </div>
@@ -2395,10 +2383,15 @@ provide enough args.
 </div>


-### STATUS: missing files - please provide them
+### STATUS: INABIAF - please **DO NOT** fix
 ### Source code: [2001/rosten/rosten.c](%%REPO_URL%%/2001/rosten/rosten.c)
 ### Information: [2001/rosten/index.html](2001/rosten/index.html)

+See list of bugs [here](2001/rosten/index.html#bugs).
+
+
+### STATUS: missing files - please provide them
+
 The author stated that there is a cat man page for this program in case one
 wanted to install it as a tool but this is missing.

@@ -2417,6 +2410,8 @@ details and a workaround.

 There's also no way to escape meta characters.

+See also the author's list of bugs [here](2001/schweikh/index.html#bugs).
+

 <div id="2001_westley">
 ## 2001/westley