fix internal links in entry index.html from 1984 thru 2012

2024-04-22 03:17:20 -07:00
1 parent 2da0a6c05f
commit 99cd17401e
@@ -42,7 +42,7 @@ If you let it, the program will continue to print a numerical sequence (can you
 guess in what base it is printed by looking at the code?) until you run out of
 memory or until they sell your computer, whichever comes first.

-If you use the [primes.sh](primes.sh) script can you figure out if there's
+If you use the [primes.sh](%%REPO_URL%%/1985/august/primes.sh) script can you figure out if there's
 anything funny going on with the output?


@@ -173,7 +173,7 @@ action of the program?</p>
 <p>If you let it, the program will continue to print a numerical sequence (can you
 guess in what base it is printed by looking at the code?) until you run out of
 memory or until they sell your computer, whichever comes first.</p>
-<p>If you use the <a href="primes.sh">primes.sh</a> script can you figure out if there’s
+<p>If you use the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1985/august/primes.sh">primes.sh</a> script can you figure out if there’s
 anything funny going on with the output?</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>No remarks were provided by the author.</p>
@@ -30,10 +30,10 @@ more details on it.

 ## Alternate code:

-The [sicherman.alt.c](sicherman.alt.c) is a slight change in the fixed version
+The [sicherman.alt.c](%%REPO_URL%%/1985/sicherman/sicherman.alt.c) is a slight change in the fixed version
 (fixed so it does not require `-traditional-cpp`) in that it has two args to
 `main()` as some compilers object to certain number of args in `main()`. This
-will be built in the case of the [sicherman.c](sicherman.c) failing to compile.
+will be built in the case of the [sicherman.c](%%REPO_URL%%/1985/sicherman/sicherman.c) failing to compile.
 In this case it'll be compiled to `sicherman` to simplify it for the larger
 audience.

@@ -167,10 +167,10 @@ more details on it.</p>
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
-<p>The <a href="sicherman.alt.c">sicherman.alt.c</a> is a slight change in the fixed version
+<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1985/sicherman/sicherman.alt.c">sicherman.alt.c</a> is a slight change in the fixed version
 (fixed so it does not require <code>-traditional-cpp</code>) in that it has two args to
 <code>main()</code> as some compilers object to certain number of args in <code>main()</code>. This
-will be built in the case of the <a href="sicherman.c">sicherman.c</a> failing to compile.
+will be built in the case of the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1985/sicherman/sicherman.c">sicherman.c</a> failing to compile.
 In this case it’ll be compiled to <code>sicherman</code> to simplify it for the larger
 audience.</p>
 <h3 id="alternate-build">Alternate build:</h3>
@@ -44,7 +44,7 @@ pruning](https://en.wikipedia.org/wiki/Alpha-beta_pruning), and it plays for
 instance on mobility(!).  Most important: it can play a pretty good game of Reversi!

 The Author was kind enough to supply the fully functional version of the
-program.  The file [lievaart2.c](lievaart2.c) contains what the program would
+program.  The file [lievaart2.c](%%REPO_URL%%/1987/lievaart/lievaart2.c) contains what the program would
 have been without the size restriction.  This version has the full end game
 logic and displays the board after each move! See above for how to use this.

@@ -178,7 +178,7 @@ ending-game rather poor. But further it knows all the rules, uses <a href="https
 pruning</a>, and it plays for
 instance on mobility(!). Most important: it can play a pretty good game of Reversi!</p>
 <p>The Author was kind enough to supply the fully functional version of the
-program. The file <a href="lievaart2.c">lievaart2.c</a> contains what the program would
+program. The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1987/lievaart/lievaart2.c">lievaart2.c</a> contains what the program would
 have been without the size restriction. This version has the full end game
 logic and displays the board after each move! See above for how to use this.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
@@ -5,8 +5,8 @@
 ```

 A smaller version, originally called `zsmall.c` (and still exists as such, as
-the source of the alt code), of [applin.c](applin.c), can be found in
-[applin.alt.c](applin.alt.c).  Your machine may have an easier time with this
+the source of the alt code), of [applin.c](%%REPO_URL%%/1988/applin/applin.c), can be found in
+[applin.alt.c](%%REPO_URL%%/1988/applin/applin.alt.c).  Your machine may have an easier time with this
 program.  See the [Alternate code](#alternate-code) section below for details.


@@ -40,8 +40,8 @@ Dhyrstone/sec/cpu machine) using the System V `cpp`.  (The GNU `cpp` when define
 `BIG_CPP` took only 45 seconds.)

 Your `cpp` may not be able to compile it due to a common bug that results in
-`cpp` running out of space.  The routine [zsmall](zsmall.c) is a smaller version
-of the [applin.c](applin.c) entry.
+`cpp` running out of space.  The routine [zsmall](%%REPO_URL%%/1988/applin/zsmall.c) is a smaller version
+of the [applin.c](%%REPO_URL%%/1988/applin/applin.c) entry.


 ## Judges' remarks:
@@ -50,11 +50,11 @@ This entry is by far the most unusual abuse of the C preprocessor that
 we have received thus far.  Nearly all of the real work is done in the
 C preprocessor!

-When we compiled [applin.c](applin.c) on an
+When we compiled [applin.c](%%REPO_URL%%/1988/applin/applin.c) on an
 [Amdahl](https://en.wikipedia.org/wiki/Amdahl_Corporation) 5890-300E, we found that it
 spent over 75 minutes in the System V C preprocessor!  Besides showing that the
 standard System V `cpp` is slow, it showed that it contained a memory usage
-problem.  The [applin.c](applin.c) only uses 29 different preprocessor symbols
+problem.  The [applin.c](%%REPO_URL%%/1988/applin/applin.c) only uses 29 different preprocessor symbols
 (besides `stdio.h`) and yet the preprocessor ran out of space!

 The GNU C preprocessor took under 45 seconds to perform the 2nd pass
@@ -155,8 +155,8 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <h2 id="to-build">To build:</h2>
 <pre><code>    make all</code></pre>
 <p>A smaller version, originally called <code>zsmall.c</code> (and still exists as such, as
-the source of the alt code), of <a href="applin.c">applin.c</a>, can be found in
-<a href="applin.alt.c">applin.alt.c</a>. Your machine may have an easier time with this
+the source of the alt code), of <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a>, can be found in
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.alt.c">applin.alt.c</a>. Your machine may have an easier time with this
 program. See the <a href="#alternate-code">Alternate code</a> section below for details.</p>
 <h2 id="try">Try:</h2>
 <pre><code>    ./applin</code></pre>
@@ -172,17 +172,17 @@ with this entry.</p>
 Dhyrstone/sec/cpu machine) using the System V <code>cpp</code>. (The GNU <code>cpp</code> when defined as
 <code>BIG_CPP</code> took only 45 seconds.)</p>
 <p>Your <code>cpp</code> may not be able to compile it due to a common bug that results in
-<code>cpp</code> running out of space. The routine <a href="zsmall.c">zsmall</a> is a smaller version
-of the <a href="applin.c">applin.c</a> entry.</p>
+<code>cpp</code> running out of space. The routine <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/zsmall.c">zsmall</a> is a smaller version
+of the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a> entry.</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>This entry is by far the most unusual abuse of the C preprocessor that
 we have received thus far. Nearly all of the real work is done in the
 C preprocessor!</p>
-<p>When we compiled <a href="applin.c">applin.c</a> on an
+<p>When we compiled <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a> on an
 <a href="https://en.wikipedia.org/wiki/Amdahl_Corporation">Amdahl</a> 5890-300E, we found that it
 spent over 75 minutes in the System V C preprocessor! Besides showing that the
 standard System V <code>cpp</code> is slow, it showed that it contained a memory usage
-problem. The <a href="applin.c">applin.c</a> only uses 29 different preprocessor symbols
+problem. The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a> only uses 29 different preprocessor symbols
 (besides <code>stdio.h</code>) and yet the preprocessor ran out of space!</p>
 <p>The GNU C preprocessor took under 45 seconds to perform the 2nd pass
 on the Amdahl 5890-300E. But due to the ANSI-likeness of GNU <code>cpp</code> (v. 1-21),
@@ -18,7 +18,7 @@ code](#alternate-code) below.

 ## Alternate code:

-The original version of this code is in [isaak.alt.c](isaak.alt.c).
+The original version of this code is in [isaak.alt.c](%%REPO_URL%%/1988/isaak/isaak.alt.c).
 The original entry starts with the line:

 ``` <!---c-->
@@ -51,7 +51,7 @@ an EBCDIC machine.

 ### Historical notes about the original entry:

-NOTE: If you named the file anything other than [isaak.c](isaak.c), you had to
+NOTE: If you named the file anything other than [isaak.c](%%REPO_URL%%/1988/isaak/isaak.c), you had to
 change the `#include` on line 6. This limitation has been fixed by using the
 `__FILE__` macro.

@@ -70,7 +70,7 @@ file: isaak.encode.  To read this file do.
 ```

 Since this was fixed, this file is not strictly necessary. See the
-[isaak.alt.c](isaak.alt.c) for the original source.
+[isaak.alt.c](%%REPO_URL%%/1988/isaak/isaak.alt.c) for the original source.

 FYI: We are likely to be more strict about portability in the future.

@@ -160,7 +160,7 @@ code</a> below.</p>
 <h2 id="to-use">To use:</h2>
 <pre><code>    ./isaak</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
-<p>The original version of this code is in <a href="isaak.alt.c">isaak.alt.c</a>.
+<p>The original version of this code is in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/isaak/isaak.alt.c">isaak.alt.c</a>.
 The original entry starts with the line:</p>
 <pre><code>    main(){};</code></pre>
 <p>This works on some systems. Why? Note that <code>#include &lt;stdio.h&gt;</code> is given on
@@ -176,7 +176,7 @@ compile.</p>
 <p>The program relies heavily on ASCII. Don’t even think of running it on
 an EBCDIC machine.</p>
 <h3 id="historical-notes-about-the-original-entry">Historical notes about the original entry:</h3>
-<p>NOTE: If you named the file anything other than <a href="isaak.c">isaak.c</a>, you had to
+<p>NOTE: If you named the file anything other than <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/isaak/isaak.c">isaak.c</a>, you had to
 change the <code>#include</code> on line 6. This limitation has been fixed by using the
 <code>__FILE__</code> macro.</p>
 <p>NOTE: The use of null comments to separate macros to construct different tokens
@@ -188,7 +188,7 @@ file: isaak.encode. To read this file do.</p>
 <pre><code>    uudecode &lt; isaak.encode
    cat isaak.output</code></pre>
 <p>Since this was fixed, this file is not strictly necessary. See the
-<a href="isaak.alt.c">isaak.alt.c</a> for the original source.</p>
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/isaak/isaak.alt.c">isaak.alt.c</a> for the original source.</p>
 <p>FYI: We are likely to be more strict about portability in the future.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>No remarks were provided by the author.</p>
@@ -66,7 +66,7 @@ by changing the #define line to:
    #define _ F-->00||F-OO--;
 ```

-This is what the modified code in [westley.c](westley.c) does whereas the alt
+This is what the modified code in [westley.c](%%REPO_URL%%/1988/westley/westley.c) does whereas the alt
 code is the original.

 You might enjoy looking at the output of:
@@ -180,7 +180,7 @@ conforming ANSI C Preprocessors may object to this: for such
 compilers, you can elide the non-standard token-pasting requirement
 by changing the #define line to:</p>
 <pre><code>    #define _ F--&gt;00||F-OO--;</code></pre>
-<p>This is what the modified code in <a href="westley.c">westley.c</a> does whereas the alt
+<p>This is what the modified code in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/westley/westley.c">westley.c</a> does whereas the alt
 code is the original.</p>
 <p>You might enjoy looking at the output of:</p>
 <pre><code>    cc -E westley.alt.c</code></pre>
@@ -34,7 +34,7 @@ The program, in its base form, implements two useful utilities:

 Included with this entry is a shell script (with comments edited down to reduce
 it to 1530 bytes) which implements the complete shark utility. The script,
-[shark.sh](shark.sh), contains a `jaw.c` embedded within it!
+[shark.sh](%%REPO_URL%%/1990/jaw/shark.sh), contains a `jaw.c` embedded within it!

 The sender must have `compress` and `btoa`. To send, try:

@@ -177,7 +177,7 @@ sentence.</p>
 </ul>
 <p>Included with this entry is a shell script (with comments edited down to reduce
 it to 1530 bytes) which implements the complete shark utility. The script,
-<a href="shark.sh">shark.sh</a>, contains a <code>jaw.c</code> embedded within it!</p>
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/jaw/shark.sh">shark.sh</a>, contains a <code>jaw.c</code> embedded within it!</p>
 <p>The sender must have <code>compress</code> and <code>btoa</code>. To send, try:</p>
 <pre><code>    ./shark.sh jaw.* README.md &gt; receive</code></pre>
 <p>The resulting file, <code>receive</code>, unpacks the input files
@@ -23,7 +23,7 @@ NOTE: that's not a typo or mistake but one can also do:
 We changed the alias that the author's suggested alias from a
 C-shell alias to a Bourne-like shell alias.

-Note that `shst.c` is renamed to [stig.c](stig.c) in the distribution.
+Note that `shst.c` is renamed to [stig.c](%%REPO_URL%%/1990/stigstig.c) in the distribution.

 WARNING: This program's `how to compile` is too specific to a particular shell.
 The obfuscation of this program is more related to shell obfuscation than C
@@ -161,7 +161,7 @@ Location: <a href="../../location.html#NO">NO</a> - <em>Kingdom of Norway</em> (
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>We changed the alias that the author’s suggested alias from a
 C-shell alias to a Bourne-like shell alias.</p>
-<p>Note that <code>shst.c</code> is renamed to <a href="stig.c">stig.c</a> in the distribution.</p>
+<p>Note that <code>shst.c</code> is renamed to <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/stigstig.c">stig.c</a> in the distribution.</p>
 <p>WARNING: This program’s <code>how to compile</code> is too specific to a particular shell.
 The obfuscation of this program is more related to shell obfuscation than C
 obfuscation. This type of entry will not be permitted in future contests.</p>
@@ -45,7 +45,7 @@ where:
 The program's source implements four functions, all from the
 same source file!

-When you compile [theorem.c](theorem.c) as is and run with 5 args, it
+When you compile [theorem.c](%%REPO_URL%%/1990/theorem/Rtheorem.c) as is and run with 5 args, it
 numerically solves the equation `y'=f(x,y)`, with a step size of `h` (see above
 usage), over the interval `x=[x1,x2]`, with the initial condition of `y(x1)=y1`.

@@ -171,7 +171,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>The program’s source implements four functions, all from the
 same source file!</p>
-<p>When you compile <a href="theorem.c">theorem.c</a> as is and run with 5 args, it
+<p>When you compile <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/theorem/Rtheorem.c">theorem.c</a> as is and run with 5 args, it
 numerically solves the equation <code>y'=f(x,y)</code>, with a step size of <code>h</code> (see above
 usage), over the interval <code>x=[x1,x2]</code>, with the initial condition of <code>y(x1)=y1</code>.</p>
 <p>The ‘expression’ <code>f(x,y)</code> is any function of <code>x</code> and <code>y</code> with the
@@ -23,7 +23,7 @@ The author suggests trying:
 ```

 Notice that a file `a.c` has been generated.  Can you tell how `a.c` was
-produced?  How does `a.c` relate to [LANDER.BAS](LANDER.BAS)?
+produced?  How does `a.c` relate to [LANDER.BAS](%%REPO_URL%%/1991/ddsLANDER.BAS)?

 What happens if you give the program a C program like itself? Try:

@@ -162,7 +162,7 @@ Location: <a href="../../location.html#GR">GR</a> - <em>Hellenic Republic</em> (
 <pre><code>    ./dds LANDER.BAS
    ./a.out</code></pre>
 <p>Notice that a file <code>a.c</code> has been generated. Can you tell how <code>a.c</code> was
-produced? How does <code>a.c</code> relate to <a href="LANDER.BAS">LANDER.BAS</a>?</p>
+produced? How does <code>a.c</code> relate to <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/ddsLANDER.BAS">LANDER.BAS</a>?</p>
 <p>What happens if you give the program a C program like itself? Try:</p>
 <pre><code>    ./dds dds.c</code></pre>
 <p>You’ll get errors yes but what does the generated file look like? What about
@@ -18,10 +18,10 @@ that's fewer than the original program.

 ## Alternate code:

-The first alternate version, [rince.alt.c](rince.alt.c), disables a maximum move
+The first alternate version, [rince.alt.c](%%REPO_URL%%/1991/rince/rince.alt.c), disables a maximum move
 count so that anyone with enough patience and time can complete the puzzle,
 without having to worry about how many moves they make, assuming they don't get
-stuck. The second version, [rince.alt2.c](rince.alt2.c), allows one to
+stuck. The second version, [rince.alt2.c](%%REPO_URL%%/1991/rince/rince.alt2.c), allows one to
 reconfigure at compilation the maximum number of moves, even if that is lowering
 the count.

@@ -160,10 +160,10 @@ that’s fewer than the original program.</p>
 <h2 id="to-use">To use:</h2>
 <pre><code>    ./rince</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
-<p>The first alternate version, <a href="rince.alt.c">rince.alt.c</a>, disables a maximum move
+<p>The first alternate version, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/rince/rince.alt.c">rince.alt.c</a>, disables a maximum move
 count so that anyone with enough patience and time can complete the puzzle,
 without having to worry about how many moves they make, assuming they don’t get
-stuck. The second version, <a href="rince.alt2.c">rince.alt2.c</a>, allows one to
+stuck. The second version, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/rince/rince.alt2.c">rince.alt2.c</a>, allows one to
 reconfigure at compilation the maximum number of moves, even if that is lowering
 the count.</p>
 <p>The author set the maximum number of moves to 484.</p>
@@ -51,7 +51,7 @@ next move, recompile `nextmove.c` and play it again:

 ## Try:

-We have provided the shell script, [ttt](ttt.sh), to make it easier to play the
+We have provided the shell script, [ttt](%%REPO_URL%%/1991/westley/ttt.sh), to make it easier to play the
 game:

 ``` <!---sh-->
@@ -62,7 +62,7 @@ game:

 The shell script determines when the game is over, and automatically replaces
 `merlyn.c` (copied from [westley.c](westley.c) with an improved version after a
-loss).  The [ttt](ttt.sh) script has two other modes:
+loss).  The [ttt](%%REPO_URL%%/1991/westley/ttt.sh) script has two other modes:

 ``` <!---sh-->
    ./ttt quitgame	# cancel any game in progress, revert to merlyn.c
@@ -136,7 +136,7 @@ Rather than use `ttt` try the script `ttt.alt` instead.
 ## Judges' remarks:

 Can you figure out why the board looks different than the
-[westley.c](westley.c)?
+[westley.c](%%REPO_URL%%/1991/westley/westley.c)?

 What happens if you make a move already made?

@@ -175,14 +175,14 @@ next move, recompile <code>nextmove.c</code> and play it again:</p>
 <pre><code>    make nextmove
    ./nextmove move_location | tee nextmove.c</code></pre>
 <h2 id="try">Try:</h2>
-<p>We have provided the shell script, <a href="ttt.sh">ttt</a>, to make it easier to play the
+<p>We have provided the shell script, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/westley/ttt.sh">ttt</a>, to make it easier to play the
 game:</p>
 <pre><code>    make ttt
    ./ttt [first_move]  # &lt;- omit first arg to have it move first
    ./ttt next_move</code></pre>
 <p>The shell script determines when the game is over, and automatically replaces
 <code>merlyn.c</code> (copied from <a href="westley.c">westley.c</a> with an improved version after a
-loss). The <a href="ttt.sh">ttt</a> script has two other modes:</p>
+loss). The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/westley/ttt.sh">ttt</a> script has two other modes:</p>
 <pre><code>    ./ttt quitgame      # cancel any game in progress, revert to merlyn.c
    ./ttt clobber       # remove all game files, revert to original source</code></pre>
 <p>For example here is a potentially losing game:</p>
@@ -229,7 +229,7 @@ can lose if you cheat. That’s supposed to happen. Can you win any other time?<
 <p>Rather than use <code>ttt</code> try the script <code>ttt.alt</code> instead.</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>Can you figure out why the board looks different than the
-<a href="westley.c">westley.c</a>?</p>
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/westley/westley.c">westley.c</a>?</p>
 <p>What happens if you make a move already made?</p>
 <p>Now go try and draw or better yet win (without cheating which is very easy :-) )!
 Why is win better than draw? Because everyone knows how to draw:</p>
@@ -35,7 +35,7 @@ For more detailed information see [1992 albert bugs](../../bugs.html#1992_albert

 ## Alternate code:

-An alternate version of this entry, [albert.alt.c](albert.alt.c), is provided.
+An alternate version of this entry, [albert.alt.c](%%REPO_URL%%/1992/albert/albert.alt.c), is provided.
 Leo Broukhis, before he was an IOCCC judge, sent the IOCCC
 judges this Email message:

@@ -56,8 +56,8 @@ judges this Email message:
    the first factor is 101 and is usually found in an instant.
 ```

-The [albert.alt.c](albert.c) file is the fixed file, whereas the
-[albert.c](albert.c) is the file before applying Leo Broukhis' fix.
+The [albert.alt.c](%%REPO_URL%%/1992/albert/albert.c) file is the fixed file, whereas the
+[albert.c](1992/albert/1992/albert/lbert.c) is the file before applying Leo Broukhis' fix.


 ### Alternate build:
@@ -164,7 +164,7 @@ Location: <a href="../../location.html#NL">NL</a> - <em>Kingdom of the Netherlan
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
-<p>An alternate version of this entry, <a href="albert.alt.c">albert.alt.c</a>, is provided.
+<p>An alternate version of this entry, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/albert/albert.alt.c">albert.alt.c</a>, is provided.
 Leo Broukhis, before he was an IOCCC judge, sent the IOCCC
 judges this Email message:</p>
 <pre><code>    From: leo _at_ zycad -dot- com (Leo Broukhis)
@@ -181,8 +181,8 @@ judges this Email message:</p>
    I&#39;ve found a number exposing another bug: 10000000001 (that&#39;s 9 0&#39;s).
    Both albert and albert.orig loop without printing anything, although
    the first factor is 101 and is usually found in an instant.</code></pre>
-<p>The <a href="albert.c">albert.alt.c</a> file is the fixed file, whereas the
-<a href="albert.c">albert.c</a> is the file before applying Leo Broukhis’ fix.</p>
+<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/albert/albert.c">albert.alt.c</a> file is the fixed file, whereas the
+<a href="1992/albert/1992/albert/lbert.c">albert.c</a> is the file before applying Leo Broukhis’ fix.</p>
 <h3 id="alternate-build">Alternate build:</h3>
 <p>To compile this alternate version:</p>
 <pre><code>    make alt</code></pre>
@@ -42,7 +42,7 @@
 	    "entry_text" : "how to run"
 	},
 	{
-	    "file_path" : "ant.README",
+	    "file_path" : "ant.README.txt",
 	    "inventory_order" : 150,
 	    "OK_to_edit" : true,
 	    "display_as" : "text",
@@ -35,7 +35,7 @@ P1003 subcommittee.

 ## Author's remarks:

-See the file [ant.README](ant.README).
+See the file [ant.README.txt](%%REPO_URL%%/1992/ant/ant.README).


 <!--
@@ -168,7 +168,7 @@ figure out where.</p>
 Interested POSIX balloters should lobby the IEEE for an obfuscated
 P1003 subcommittee.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
-<p>See the file <a href="ant.README">ant.README</a>.</p>
+<p>See the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/ant/ant.README">ant.README.txt</a>.</p>
 <!--

    Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
@@ -198,7 +198,7 @@ P1003 subcommittee.</p>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/ant/Makefile">Makefile</a> - entry Makefile</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/ant/ant.orig.c">ant.orig.c</a> - original source</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/ant/try.sh">try.sh</a> - how to run</li>
-<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/ant/ant.README">ant.README</a> - am man page</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/ant/ant.README.txt">ant.README.txt</a> - am man page</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/ant/ant.test.mk">ant.test.mk</a> - how to compile</li>
 </ul>
 <h2 id="secondary-files">Secondary files</h2>
@@ -57,7 +57,7 @@ Fourth:

 ## Alternate code:

-This alternate version, [buzzard.2.alt.c](buzzard.2.alt.c), does not contain a
+This alternate version, [buzzard.2.alt.c](%%REPO_URL%%/1992/buzzard.2/buzzard.2.alt.c), does not contain a
 fix that the author notes in their remarks.


@@ -123,7 +123,7 @@ included, but it only works on ASCII systems.
 Do not expect to be able to do anything interesting with `first`.

 To do something interesting, you need to feed `first` the file
-[third](third) first.  In unix, you can do
+[third](%%REPO_URL%%/1992/buzzard.2/third) first.  In unix, you can do

 ``` <!---sh-->
    cat third help.th - | ./first
@@ -132,10 +132,10 @@ To do something interesting, you need to feed `first` the file
 to do this.  Hopefully most operating systems will provide a way to do this.  It
 may take some time for this to complete (I seem to remember it taking several
 minutes on an 8086 PC); `THIRD` will prompt you when it is finished.  The file
-[third](third) has not been obfuscated, due to sheer kindness on the author's
+[third](%%REPO_URL%%/1992/buzzard.2/third) has not been obfuscated, due to sheer kindness on the author's
 part.

-For more information on what you can do once you've piped [third](third) into
+For more information on what you can do once you've piped [third](%%REPO_URL%%/1992/buzzard.2/third) into
 first, type `help` and consult
 [FORTH](https://en.wikipedia.org/wiki/Forth_(programming_language)) manuals for
 further reference.  Six sample THIRD programs are included in the files
@@ -176,7 +176,7 @@ should make first first :-) ):</p>
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
-<p>This alternate version, <a href="buzzard.2.alt.c">buzzard.2.alt.c</a>, does not contain a
+<p>This alternate version, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/buzzard.2/buzzard.2.alt.c">buzzard.2.alt.c</a>, does not contain a
 fix that the author notes in their remarks.</p>
 <h3 id="alternate-build">Alternate build:</h3>
 <pre><code>    make alt</code></pre>
@@ -215,14 +215,14 @@ but gives no warning messages. A sample program, <code>demo1.1st</code>, is
 included, but it only works on ASCII systems.</p>
 <p>Do not expect to be able to do anything interesting with <code>first</code>.</p>
 <p>To do something interesting, you need to feed <code>first</code> the file
-<a href="third">third</a> first. In unix, you can do</p>
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/buzzard.2/third">third</a> first. In unix, you can do</p>
 <pre><code>    cat third help.th - | ./first</code></pre>
 <p>to do this. Hopefully most operating systems will provide a way to do this. It
 may take some time for this to complete (I seem to remember it taking several
 minutes on an 8086 PC); <code>THIRD</code> will prompt you when it is finished. The file
-<a href="third">third</a> has not been obfuscated, due to sheer kindness on the author’s
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/buzzard.2/third">third</a> has not been obfuscated, due to sheer kindness on the author’s
 part.</p>
-<p>For more information on what you can do once you’ve piped <a href="third">third</a> into
+<p>For more information on what you can do once you’ve piped <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/buzzard.2/third">third</a> into
 first, type <code>help</code> and consult
 <a href="https://en.wikipedia.org/wiki/Forth_(programming_language)">FORTH</a> manuals for
 further reference. Six sample THIRD programs are included in the files
@@ -57,9 +57,9 @@ Then using the proper dictionary file it does:

 where `/usr/share/dict/words` is the dictionary file.

-Then it uses the [mkdict.sh](mkdict.sh) script to create a dictionary file out
-of the files [README.md](README.md), [try.sh](try.sh) (itself) and
-[Makefile](Makefile) and it repeats the same commands as above. In the case no
+Then it uses the [mkdict.sh](%%REPO_URL%%/1992/gson/mkdict.sh) script to create a dictionary file out
+of the files [README.md](%%REPO_URL%%/1992/gson/README.md), [try.sh](try.sh) (itself) and
+[Makefile](%%REPO_URL%%/1992/gson/Makefile) and it repeats the same commands as above. In the case no
 dictionary file can be found in the first step it only runs the commands once
 with the created dictionary file.

@@ -71,7 +71,7 @@ names listed above.  Run this program to find the anagrams they
 weren't allowed to print!

 The author provided an obfuscated script that can be used to construct
-dictionaries which has been put in as [mkdict.sh](mkdict.sh). To use try:
+dictionaries which has been put in as [mkdict.sh](%%REPO_URL%%/1992/gson/mkdict.sh). To use try:

 ``` <!---sh-->
    cat README.md | ./mkdict.sh > words
@@ -180,9 +180,9 @@ following locations though the last one is more ironic:</p>
    ./ag ross perot                     &lt; /usr/share/dict/words
    ./ag paul e tsongas         &lt; /usr/share/dict/words</code></pre>
 <p>where <code>/usr/share/dict/words</code> is the dictionary file.</p>
-<p>Then it uses the <a href="mkdict.sh">mkdict.sh</a> script to create a dictionary file out
-of the files <a href="README.md">README.md</a>, <a href="try.sh">try.sh</a> (itself) and
-<a href="Makefile">Makefile</a> and it repeats the same commands as above. In the case no
+<p>Then it uses the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/gson/mkdict.sh">mkdict.sh</a> script to create a dictionary file out
+of the files <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/gson/README.md">README.md</a>, <a href="try.sh">try.sh</a> (itself) and
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/gson/Makefile">Makefile</a> and it repeats the same commands as above. In the case no
 dictionary file can be found in the first step it only runs the commands once
 with the created dictionary file.</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
@@ -190,7 +190,7 @@ with the created dictionary file.</p>
 names listed above. Run this program to find the anagrams they
 weren’t allowed to print!</p>
 <p>The author provided an obfuscated script that can be used to construct
-dictionaries which has been put in as <a href="mkdict.sh">mkdict.sh</a>. To use try:</p>
+dictionaries which has been put in as <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/gson/mkdict.sh">mkdict.sh</a>. To use try:</p>
 <pre><code>    cat README.md | ./mkdict.sh &gt; words</code></pre>
 <p>Then try using the program as shown above with the file <code>words</code>.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
@@ -34,7 +34,7 @@ Of course, the source (layout) is self-documenting!  :-)

 NOTE: The original winning source assumed that `exit(3)` returned a value which
 cause problems for some systems where `exit(3)` returns a void.  The file
-[imc.c](imc.c) has been modified to avoid this problem. The original file also
+[imc.c](%%REPO_URL%%/1992/imc/imc.c) has been modified to avoid this problem. The original file also
 declared argc to be a `long` which was fixed.


@@ -169,7 +169,7 @@ output.</p>
 <p>Of course, the source (layout) is self-documenting! :-)</p>
 <p>NOTE: The original winning source assumed that <code>exit(3)</code> returned a value which
 cause problems for some systems where <code>exit(3)</code> returns a void. The file
-<a href="imc.c">imc.c</a> has been modified to avoid this problem. The original file also
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/imc.c">imc.c</a> has been modified to avoid this problem. The original file also
 declared argc to be a <code>long</code> which was fixed.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <h3 id="portability">Portability</h3>
@@ -79,7 +79,7 @@ Such systems should compile using `-lX11`.

 NOTE: The original winning source [kivinen.orig.c](kivinen.orig.c) assumed that
 `exit(3)` returned a value which cause problems for some systems where `exit(3)` returns
-`void`.  The file [kivinen.c](kivinen.c) avoids this problem.
+`void`.  The file [kivinen.c](%%REPO_URL%%/1992/kivinen/kivinen.c) avoids this problem.


 ## Author's remarks:
@@ -191,7 +191,7 @@ you have with the program. :-)</p>
 Such systems should compile using <code>-lX11</code>.</p>
 <p>NOTE: The original winning source <a href="kivinen.orig.c">kivinen.orig.c</a> assumed that
 <code>exit(3)</code> returned a value which cause problems for some systems where <code>exit(3)</code> returns
-<code>void</code>. The file <a href="kivinen.c">kivinen.c</a> avoids this problem.</p>
+<code>void</code>. The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/kivinen/kivinen.c">kivinen.c</a> avoids this problem.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <h3 id="x-entertainment-kit">X Entertainment Kit</h3>
 <p>This kit includes three games from the early era of video games designed for
@@ -25,7 +25,7 @@ NOTE: Some systems need to compile with `-ltermcap` as well as `-lcurses`.
 NOTE: The original winning source [marangon.orig.c](marangon.orig.c), found in
 the archive directory, assumed that `exit(3)` returns a value which cause
 problems for some systems where `exit(3)` returns a `void`.  The file
-[marangon.c](marangon.c) avoids this problem.
+[marangon.c](%%REPO_URL%%/1992/marangon/marangon.c) avoids this problem.


 ## Author's remarks:
@@ -165,7 +165,7 @@ are not careful, you may find things “at 6’s and 7’s”. :-)</p>
 <p>NOTE: The original winning source <a href="marangon.orig.c">marangon.orig.c</a>, found in
 the archive directory, assumed that <code>exit(3)</code> returns a value which cause
 problems for some systems where <code>exit(3)</code> returns a <code>void</code>. The file
-<a href="marangon.c">marangon.c</a> avoids this problem.</p>
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/marangon/marangon.c">marangon.c</a> avoids this problem.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>It starts off by creating a table with number 5 in all places. The CPU melts
 the numbers and you must return them in original state. When you increase a
@@ -64,7 +64,7 @@ NOTE: this alternative version also needs a terminal with at least 80 columns.

 ### Alternate try:

-The [try.sh](try.sh) script uses both the original entry and the alternate code
+The [try.sh](%%REPO_URL%%/1992/westley/try.sh) script uses both the original entry and the alternate code
 so one can try the same script for both:

 ``` <!---sh-->
@@ -177,7 +177,7 @@ should just use the <code>westley</code> and <code>westley.alt</code> programs d
 <pre><code>    ./whereami.alt.sh lat long</code></pre>
 <p>NOTE: this alternative version also needs a terminal with at least 80 columns.</p>
 <h3 id="alternate-try">Alternate try:</h3>
-<p>The <a href="try.sh">try.sh</a> script uses both the original entry and the alternate code
+<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/westley/try.sh">try.sh</a> script uses both the original entry and the alternate code
 so one can try the same script for both:</p>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
@@ -73,20 +73,20 @@ Use `rince.alt` or `rince.alt2` as you would `rince` above.

 The author has provided several CABBAGE files for your amusement:

- [rince.data1](rince.data1) plays
+- [rince.data1](%%REPO_URL%%/1993/rince/rince.data1) plays
 [Breakout](https://en.wikipedia.org/wiki/Breakout_(video_game).  Keys are `,`
 for left, `/` for right, and `.` for 'fire the ball'.

- [rince.data2](rince.data2) plays the old [James Bonfield](../../authors.html#James_Bonfield)'s
+- [rince.data2](%%REPO_URL%%/1993/rince/rince.data2) plays the old [James Bonfield](../../authors.html#James_Bonfield)'s
 ([1991/rince](../../1991/rince/index.html) game from IOCCC 1991.

- [rince.data3](rince.data3) Sokoban screen 11. You are the `o` character.
+- [rince.data3](%%REPO_URL%%/1993/rince/rince.data3) Sokoban screen 11. You are the `o` character.
 You must push the money `m` into the dotted region of the screen. The game is
 considered finished when all the `m`s are then `M`s.

- [rince.data4](rince.data4) Sokoban screen 13. Same rules as above.
+- [rince.data4](%%REPO_URL%%/1993/rince/rince.data4) Sokoban screen 13. Same rules as above.

-For a brief design description, see [design.html](design.html).
+For a brief design description, see [design.html](%%REPO_URL%%/1993/rince/design.html).


 ### WARNING for SunOS 4.1.x:
@@ -184,17 +184,17 @@ changed).</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>The author has provided several CABBAGE files for your amusement:</p>
 <ul>
-<li><p><a href="rince.data1">rince.data1</a> plays
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/rince/rince.data1">rince.data1</a> plays
 [Breakout](https://en.wikipedia.org/wiki/Breakout_(video_game). Keys are <code>,</code>
 for left, <code>/</code> for right, and <code>.</code> for ‘fire the ball’.</p></li>
-<li><p><a href="rince.data2">rince.data2</a> plays the old <a href="../../authors.html#James_Bonfield">James Bonfield</a>’s
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/rince/rince.data2">rince.data2</a> plays the old <a href="../../authors.html#James_Bonfield">James Bonfield</a>’s
 (<a href="../../1991/rince/index.html">1991/rince</a> game from IOCCC 1991.</p></li>
-<li><p><a href="rince.data3">rince.data3</a> Sokoban screen 11. You are the <code>o</code> character.
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/rince/rince.data3">rince.data3</a> Sokoban screen 11. You are the <code>o</code> character.
 You must push the money <code>m</code> into the dotted region of the screen. The game is
 considered finished when all the <code>m</code>s are then <code>M</code>s.</p></li>
-<li><p><a href="rince.data4">rince.data4</a> Sokoban screen 13. Same rules as above.</p></li>
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/rince/rince.data4">rince.data4</a> Sokoban screen 13. Same rules as above.</p></li>
 </ul>
-<p>For a brief design description, see <a href="design.html">design.html</a>.</p>
+<p>For a brief design description, see <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/rince/design.html">design.html</a>.</p>
 <h3 id="warning-for-sunos-4.1.x">WARNING for SunOS 4.1.x:</h3>
 <p>If you are running SunOS 4.1.x (assuming you can find an ANSI
 compiler in the first place), this program may be used to log
@@ -66,7 +66,7 @@ After this program prints the contents of 'file', ask it
 some questions related to the text.

 The author suggests the following questions when using
-[schnitzi.info](schnitzi.info):
+[schnitzi.info](%%REPO_URL%%/1993/schnitzi/schnitzi.info):


 - Who is Mark Schnitzius?
@@ -182,7 +182,7 @@ intentional spelling error there.</p>
 <p>After this program prints the contents of ‘file’, ask it
 some questions related to the text.</p>
 <p>The author suggests the following questions when using
-<a href="schnitzi.info">schnitzi.info</a>:</p>
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/schnitzi/schnitzi.info">schnitzi.info</a>:</p>
 <ul>
 <li>Who is Mark Schnitzius?</li>
 <li>What exactly does this program do?</li>
@@ -85,13 +85,13 @@ in an effort to get around the 1994 version of Rule 2:
 ```

 Indeed, when [dodsond2.gz](dodsond2.gz) is uncompressed, it is identical
-to the [dodsond2.c](dodsond2.c) file you find today.
+to the [dodsond2.c](%%REPO_URL%%/1994/dodsond2/dodsond2.c) file you find today.

 The IOCCC rules and guidelines were modified in an effort to address
 this fun "_abuse of the rules_" style hack.

 It is worth noting that without this compression "_abuse of the rules_"
-style hack, the [dodsond2.c](dodsond2.c) is further obfuscated.
+style hack, the [dodsond2.c](%%REPO_URL%%/1994/dodsond2/dodsond2.c) is further obfuscated.


 ## Author's remarks:
@@ -190,11 +190,11 @@ in an effort to get around the 1994 version of Rule 2:</p>
       excluding whitespace (tab, space, newline), and excluding any ; { or }
       followed by either whitespace or end of file, must be &lt;= 1536.</code></pre>
 <p>Indeed, when <a href="dodsond2.gz">dodsond2.gz</a> is uncompressed, it is identical
-to the <a href="dodsond2.c">dodsond2.c</a> file you find today.</p>
+to the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/dodsond2/dodsond2.c">dodsond2.c</a> file you find today.</p>
 <p>The IOCCC rules and guidelines were modified in an effort to address
 this fun “<em>abuse of the rules</em>” style hack.</p>
 <p>It is worth noting that without this compression “<em>abuse of the rules</em>”
-style hack, the <a href="dodsond2.c">dodsond2.c</a> is further obfuscated.</p>
+style hack, the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/dodsond2/dodsond2.c">dodsond2.c</a> is further obfuscated.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>Go searching for the Wumpus in the Caverns of Doom! But be careful…
 There are pits and bats waiting to seal your fate, as well as a
@@ -23,7 +23,7 @@

 ## Alternate code:

-This confuses cb greatly. See [horton.alt.c](horton.alt.c) for an unobfuscated/enhanced
+This confuses cb greatly. See [horton.alt.c](%%REPO_URL%%/1994/horton/horton.alt.c) for an unobfuscated/enhanced
 version.


@@ -78,7 +78,7 @@ cogs in the wheels of the grand plot to overthrow the cubics!
 Oh, by the way, it uses a self-contained graphtab and frame buffer.
 It's easily modified to graph *any* 96x160 bitmap on a dumb terminal.

-See the [gtface](gtface.c) program for another example.  Try:
+See the [gtface](%%REPO_URL%%/1994/horton/gtface.c) program for another example.  Try:

 ``` <!---sh-->
    make gtface
@@ -160,7 +160,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
-<p>This confuses cb greatly. See <a href="horton.alt.c">horton.alt.c</a> for an unobfuscated/enhanced
+<p>This confuses cb greatly. See <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/horton/horton.alt.c">horton.alt.c</a> for an unobfuscated/enhanced
 version.</p>
 <h3 id="alternate-build">Alternate build:</h3>
 <pre><code>    make alt</code></pre>
@@ -187,7 +187,7 @@ of their cubic equations. Those dastardly arguments are mere coefficients,
 cogs in the wheels of the grand plot to overthrow the cubics!</p>
 <p>Oh, by the way, it uses a self-contained graphtab and frame buffer.
 It’s easily modified to graph <em>any</em> 96x160 bitmap on a dumb terminal.</p>
-<p>See the <a href="gtface.c">gtface</a> program for another example. Try:</p>
+<p>See the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/horton/gtface.c">gtface</a> program for another example. Try:</p>
 <pre><code>    make gtface
    ./gtface &lt; gtface.data</code></pre>
 <p>For more information, see my article</p>
@@ -26,7 +26,7 @@ was the world's smallest self reproducing program.  While the sizes
 of these submissions varied, a quick glance would reveal that they
 were too big, until this entry came along.

-While strictly speaking, [smr.c](smr.c) is not a valid C program, it is not an
+While strictly speaking, [smr.c](%%REPO_URL%%/1994/smr/smr.c) is not a valid C program, it is not an
 invalid C program either!  Some C compilers will compile an empty file into a
 program that does nothing.  But even if your compiler can't, the build
 instructions supplied with this entry will produce an executable file.  On most
@@ -163,7 +163,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 was the world’s smallest self reproducing program. While the sizes
 of these submissions varied, a quick glance would reveal that they
 were too big, until this entry came along.</p>
-<p>While strictly speaking, <a href="smr.c">smr.c</a> is not a valid C program, it is not an
+<p>While strictly speaking, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/smr/smr.c">smr.c</a> is not a valid C program, it is not an
 invalid C program either! Some C compilers will compile an empty file into a
 program that does nothing. But even if your compiler can’t, the build
 instructions supplied with this entry will produce an executable file. On most
@@ -27,7 +27,7 @@ If you have `primes(1)` installed you might also wish to try:
    ./primes.sh number
 ```

-where `number` is a positive number, defaulting to 15. The [try.sh](try.sh)
+where `number` is a positive number, defaulting to 15. The [try.sh](%%REPO_URL%%/1994/weisberg/try.sh)
 script will also do this.


@@ -162,7 +162,7 @@ code</a> below for more details.</p>
 <pre><code>    ./try.sh</code></pre>
 <p>If you have <code>primes(1)</code> installed you might also wish to try:</p>
 <pre><code>    ./primes.sh number</code></pre>
-<p>where <code>number</code> is a positive number, defaulting to 15. The <a href="try.sh">try.sh</a>
+<p>where <code>number</code> is a positive number, defaulting to 15. The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/weisberg/try.sh">try.sh</a>
 script will also do this.</p>
 <h2 id="alternate-code">Alternate code:</h2>
 <p>If you liked what you saw from the above program, and happen to
@@ -29,7 +29,7 @@ invocations_ specified. That means with the right compiler invocation you can
 'win' the game on the first go.

 There are a variety of different `-D` flags you give to `cc` that change the
-message you get. You might wish to look at the [source code](westley.alt.c) to
+message you get. You might wish to look at the [source code](%%REPO_URL%%/1994/westley/westley.alt.c) to
 get a better idea or see below in the [Try](#try) section for running the game
 from start to finish.

@@ -70,7 +70,7 @@ reason that we recommend you try it first.
 ```

 There are a variety of different `-D` flags you can give to `cc` that change the
-message you get. You might wish to look at the [source code](westley.c) to get a
+message you get. You might wish to look at the [source code](%%REPO_URL%%/1994/westley/westley.c) to get a
 better idea or see below in the [Original try](#original-try) section for
 running the game from start to finish.

@@ -170,7 +170,7 @@ else.</p>
 invocations</em> specified. That means with the right compiler invocation you can
 ‘win’ the game on the first go.</p>
 <p>There are a variety of different <code>-D</code> flags you give to <code>cc</code> that change the
-message you get. You might wish to look at the <a href="westley.alt.c">source code</a> to
+message you get. You might wish to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.alt.c">source code</a> to
 get a better idea or see below in the <a href="#try">Try</a> section for running the game
 from start to finish.</p>
 <h2 id="try">Try:</h2>
@@ -191,7 +191,7 @@ reason that we recommend you try it first.</p>
 <h3 id="original-build">Original build:</h3>
 <pre><code>    make all</code></pre>
 <p>There are a variety of different <code>-D</code> flags you can give to <code>cc</code> that change the
-message you get. You might wish to look at the <a href="westley.c">source code</a> to get a
+message you get. You might wish to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.c">source code</a> to get a
 better idea or see below in the <a href="#original-try">Original try</a> section for
 running the game from start to finish.</p>
 <h3 id="original-use">Original use:</h3>
@@ -24,7 +24,7 @@
 While it may not have been the intention of the author, the
 judges noted that the C pre-processed version (with the `#include`s
 left intact) looked very much like a rat "dropping core".  See
-[garry.alt.c](garry.alt.c) and judge for yourself!
+[garry.alt.c](%%REPO_URL%%/1995/garry/garry.alt.c) and judge for yourself!


 ### Alternate build:
@@ -51,7 +51,7 @@ left intact) looked very much like a rat "dropping core".  See
 ## Judges' remarks:

 The author was kind enough to provide a less obfuscated version of
-the source called [garry.fmt.c](garry.fmt.c).
+the source called [garry.fmt.c](%%REPO_URL%%/1995/garry/garry.fmt.c).


 ## Author's remarks:
@@ -162,7 +162,7 @@ Location: <a href="../../location.html#DE">DE</a> - <em>Federal Republic of Germ
 <p>While it may not have been the intention of the author, the
 judges noted that the C pre-processed version (with the <code>#include</code>s
 left intact) looked very much like a rat “dropping core”. See
-<a href="garry.alt.c">garry.alt.c</a> and judge for yourself!</p>
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1995/garry/garry.alt.c">garry.alt.c</a> and judge for yourself!</p>
 <h3 id="alternate-build">Alternate build:</h3>
 <pre><code>    make alt</code></pre>
 <h3 id="alternate-use">Alternate use:</h3>
@@ -171,7 +171,7 @@ left intact) looked very much like a rat “dropping core”. See
 <pre><code>    ./try.alt.sh</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>The author was kind enough to provide a less obfuscated version of
-the source called <a href="garry.fmt.c">garry.fmt.c</a>.</p>
+the source called <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1995/garry/garry.fmt.c">garry.fmt.c</a>.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>This program is a file filter, designed to do environment-expansion and
 incorporating the ability to create binary from escaped data in the
@@ -36,7 +36,7 @@ For more detailed information see [1995 vanschnitz bugs](../../bugs.html#1995_va
 ## Alternate code:

 The authors provided a spoiler version of the program. Originally uuencoded we
-have decoded it for the wider audience in [vanschnitz.alt.c](vanschnitz.alt.c). The
+have decoded it for the wider audience in [vanschnitz.alt.c](%%REPO_URL%%/1995/vanschnitz/vanschnitz.alt.c). The
 `uuencode`d blob is still available in their remarks below. They encourage you
 to first try and figure out the program without the spoiler.

@@ -120,7 +120,7 @@ solution wherein the disks end up on peg 2; for an even
 number of disks, they will end on peg 3.  This should
 provide some hint as to what sort of algorithm is used.

-We have included a [spoiler](spoiler.c) version of the program, with
+We have included a [spoiler](%%REPO_URL%%/1995/vanschnitz/spoiler.c) version of the program, with
 meaningful symbol names and comments, but we encourage you
 to try to decipher the program without it...

@@ -171,7 +171,7 @@ in 2023. See <a href="#alternate-code">Alternate code</a> below.</p>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
 <p>The authors provided a spoiler version of the program. Originally uuencoded we
-have decoded it for the wider audience in <a href="vanschnitz.alt.c">vanschnitz.alt.c</a>. The
+have decoded it for the wider audience in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1995/vanschnitz/vanschnitz.alt.c">vanschnitz.alt.c</a>. The
 <code>uuencode</code>d blob is still available in their remarks below. They encourage you
 to first try and figure out the program without the spoiler.</p>
 <h3 id="alternate-build">Alternate build:</h3>
@@ -227,7 +227,7 @@ the resulting program (on a Unix system) is to do the command</p>
 solution wherein the disks end up on peg 2; for an even
 number of disks, they will end on peg 3. This should
 provide some hint as to what sort of algorithm is used.</p>
-<p>We have included a <a href="spoiler.c">spoiler</a> version of the program, with
+<p>We have included a <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1995/vanschnitz/spoiler.c">spoiler</a> version of the program, with
 meaningful symbol names and comments, but we encourage you
 to try to decipher the program without it…</p>
 <pre><code>    begin 444 spoiler.c
@@ -129,15 +129,15 @@ Or even simpler:
    cat august.c test.oc | ./august | ./august
 ```

-A larger example is included [fac.oc](fac.oc).
+A larger example is included [fac.oc](%%REPO_URL%%/1996/august/fac.oc).

 The compiler for OC is naturally written in OC (where did you think the byte
-code came from?).  It is in the file [parse.oc](parse.oc).
+code came from?).  It is in the file [parse.oc](%%REPO_URL%%/1996/august/parse.oc).

 Hmm...  So now we have an interpreter written in OC and a compiler for OC, can
 we compile the interpreter?  Yes, we can!  The OC compiler does not have a
 preprocessor (hey, what do you expect from a program that is this small), so we
-need to use an external one.  To pre-process [august.c](august.c) use the
+need to use an external one.  To pre-process [august.c](%%REPO_URL%%/1996/august/august.c) use the
 command from the Makefile, but add the `-E` flag and change 60000 to 40000,
 i.e.:

@@ -213,13 +213,13 @@ and binary in august) and that we have this in a file named <code>test.oc</code>
 <pre><code>    ./august &lt; test.oo</code></pre>
 <p>Or even simpler:</p>
 <pre><code>    cat august.c test.oc | ./august | ./august</code></pre>
-<p>A larger example is included <a href="fac.oc">fac.oc</a>.</p>
+<p>A larger example is included <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/august/fac.oc">fac.oc</a>.</p>
 <p>The compiler for OC is naturally written in OC (where did you think the byte
-code came from?). It is in the file <a href="parse.oc">parse.oc</a>.</p>
+code came from?). It is in the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/august/parse.oc">parse.oc</a>.</p>
 <p>Hmm… So now we have an interpreter written in OC and a compiler for OC, can
 we compile the interpreter? Yes, we can! The OC compiler does not have a
 preprocessor (hey, what do you expect from a program that is this small), so we
-need to use an external one. To pre-process <a href="august.c">august.c</a> use the
+need to use an external one. To pre-process <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/august/august.c">august.c</a> use the
 command from the Makefile, but add the <code>-E</code> flag and change 60000 to 40000,
 i.e.:</p>
 <pre><code>    cc -E -DZ=40000 .... august.c &gt; august.oc</code></pre>
@@ -31,7 +31,7 @@ For a good no-op try:
    gzip -c < rcm.c | ./rcm
 ```

-NOTE: this is done in the [try.sh](try.sh) script as well, along with some other
+NOTE: this is done in the [try.sh](%%REPO_URL%%/1996/rcm/try.sh) script as well, along with some other
 commands including a way to do the above command but with more steps.


@@ -163,7 +163,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>For a good no-op try:</p>
 <pre><code>    gzip -c &lt; rcm.c | ./rcm</code></pre>
-<p>NOTE: this is done in the <a href="try.sh">try.sh</a> script as well, along with some other
+<p>NOTE: this is done in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/rcm/try.sh">try.sh</a> script as well, along with some other
 commands including a way to do the above command but with more steps.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>Except for some silly requirements regarding input validation, CRC checking, and
@@ -41,14 +41,14 @@ The author also suggests:
 ```

 (and we do too) which works with `sh`, `bash`, `ksh` and `zsh` as well. Press
-ctrl-c to stop it. Observe how the [try.sh](try.sh) script does this once to
+ctrl-c to stop it. Observe how the [try.sh](%%REPO_URL%%/1996/schweikh2/try.sh) script does this once to
 make it easier to see what is happening.


 ## Judges' remarks:

 The original program, with only slight obfuscations, may be found
-in [hunni.c](hunni.c). The perl script, [hunni.pl](hunni.pl), obfuscates it
+in [hunni.c](%%REPO_URL%%/1996/schweikh2/hunni.c). The perl script, [hunni.pl](hunni.pl), obfuscates it
 appropriately. Try:

 ``` <!---sh-->
@@ -170,11 +170,11 @@ Location: <a href="../../location.html#DE">DE</a> - <em>Federal Republic of Germ
 <p>The author also suggests:</p>
 <pre><code>    while :; do grep -v &#39;#&#39; schweikh2.c; done</code></pre>
 <p>(and we do too) which works with <code>sh</code>, <code>bash</code>, <code>ksh</code> and <code>zsh</code> as well. Press
-ctrl-c to stop it. Observe how the <a href="try.sh">try.sh</a> script does this once to
+ctrl-c to stop it. Observe how the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh2/try.sh">try.sh</a> script does this once to
 make it easier to see what is happening.</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>The original program, with only slight obfuscations, may be found
-in <a href="hunni.c">hunni.c</a>. The perl script, <a href="hunni.pl">hunni.pl</a>, obfuscates it
+in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh2/hunni.c">hunni.c</a>. The perl script, <a href="hunni.pl">hunni.pl</a>, obfuscates it
 appropriately. Try:</p>
 <pre><code>    less hunni.c

@@ -22,7 +22,7 @@ You have been warned.
 The source fails to compile on compilers that recognize the inline
 keyword by default.  For gcc, you may need to use `-ansi`.

-See the file [schweikh3.info](schweikh3.info) for example output from various
+See the file [schweikh3.info](%%REPO_URL%%/1996/schweikh3/schweikh3.info) for example output from various
 systems.

 But still it is a useful utility.  To use try:
@@ -163,7 +163,7 @@ You have been warned.</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>The source fails to compile on compilers that recognize the inline
 keyword by default. For gcc, you may need to use <code>-ansi</code>.</p>
-<p>See the file <a href="schweikh3.info">schweikh3.info</a> for example output from various
+<p>See the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh3/schweikh3.info">schweikh3.info</a> for example output from various
 systems.</p>
 <p>But still it is a useful utility. To use try:</p>
 <pre><code>    ./schweikh3</code></pre>
@@ -28,7 +28,7 @@ on this in the author's comments in the [Alternate Build
 Instructions](#alternate-build-instructions) section.

 If however you wish to change the above controls, see the header file
-[keysym.h](keysym.h) for the definitions of other characters that you might wish
+[keysym.h](%%REPO_URL%%/1998/banks/keysym.h) for the definitions of other characters that you might wish
 to use. The name of the macro in the header file is what you need to set the
 macros to, depending on what controls you wish to redefine. For instance, to set
 the throttle up and down to `u` and `d`:
@@ -46,7 +46,7 @@ corresponds to `d`:
    #define XK_u                             0x0075  /* U+0075 LATIN SMALL LETTER U */
 ```

-Note that the [keysym.h](keysym.h) file is not complete from X11; it's just the
+Note that the [keysym.h](%%REPO_URL%%/1998/banks/keysym.h) file is not complete from X11; it's just the
 more likely candidates (and some that are probably unlikely :-) ).

 The upper case letters would be `XK_U` and `XK_D` and you can search the header
@@ -200,31 +200,31 @@ less than 1000 total lines of input.

 Here is a brief description of the scenery files:

- [horizon.sc](horizon.sc)
+- [horizon.sc](%%REPO_URL%%/1998/banks/horizon.sc)

    A horizon, nothing more.  You will probably always want to input this piece
    of scenery.

- [mountains.sc](mountains.sc)
+- [mountains.sc](%%REPO_URL%%/1998/banks/mountains.sc)

    An alternate horizon; a little more mountainous.

- [pittsburgh.sc]([pittsburgh.sc])
+- [pittsburgh.sc](%%REPO_URL%%/1998/banks/pittsburgh.sc)

    Scenery of downtown Pittsburgh.  The downtown area is initially located
    to your right.

- [bb.sc](bb.sc)
+- [bb.sc](%%REPO_URL%%/1998/banks/bb.sc)

    Simple obstacle course.  Try to fly over the buildings and under the
    bridges.

- [pyramids.sc](pyramids.sc)
+- [pyramids.sc](1998/banks/pyramids.sc)

    Fly over the tombs of the ancient Pharaohs, in this (fictitious) Egyptian
    landscape.

- [river.sc](river.sc)
+- [river.sc](%%REPO_URL%%/1998/banks/river.sc)

    Follow a flowing river from the sky.

@@ -261,7 +261,7 @@ I'm sure you'll be making your own scenery files very soon!!!
 ### Alternate Build Instructions

 Several options must be passed to the compiler to make the build
-work.  The provided [Makefile](Makefile) has the appropriate options set
+work.  The provided [Makefile](%%REPO_URL%%/1998/banks/Makefile) has the appropriate options set
 to default values.  Use this section if you want to compile with
 different options.

@@ -172,7 +172,7 @@ default value. The author provided the following table:</p>
 on this in the author’s comments in the <a href="#alternate-build-instructions">Alternate Build
 Instructions</a> section.</p>
 <p>If however you wish to change the above controls, see the header file
-<a href="keysym.h">keysym.h</a> for the definitions of other characters that you might wish
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/keysym.h">keysym.h</a> for the definitions of other characters that you might wish
 to use. The name of the macro in the header file is what you need to set the
 macros to, depending on what controls you wish to redefine. For instance, to set
 the throttle up and down to <code>u</code> and <code>d</code>:</p>
@@ -181,7 +181,7 @@ the throttle up and down to <code>u</code> and <code>d</code>:</p>
 corresponds to <code>d</code>:</p>
 <pre><code>    #define XK_d                             0x0064  /* U+0064 LATIN SMALL LETTER D */
    #define XK_u                             0x0075  /* U+0075 LATIN SMALL LETTER U */</code></pre>
-<p>Note that the <a href="keysym.h">keysym.h</a> file is not complete from X11; it’s just the
+<p>Note that the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/keysym.h">keysym.h</a> file is not complete from X11; it’s just the
 more likely candidates (and some that are probably unlikely :-) ).</p>
 <p>The upper case letters would be <code>XK_U</code> and <code>XK_D</code> and you can search the header
 file for ‘LATIN CAPITAL D’, for example.</p>
@@ -283,21 +283,21 @@ You may input more than one scenery file, as long as there are
 less than 1000 total lines of input.</p>
 <p>Here is a brief description of the scenery files:</p>
 <ul>
-<li><p><a href="horizon.sc">horizon.sc</a></p>
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/horizon.sc">horizon.sc</a></p>
 <p>A horizon, nothing more. You will probably always want to input this piece
 of scenery.</p></li>
-<li><p><a href="mountains.sc">mountains.sc</a></p>
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/mountains.sc">mountains.sc</a></p>
 <p>An alternate horizon; a little more mountainous.</p></li>
-<li><p><a href="%5Bpittsburgh.sc%5D">pittsburgh.sc</a></p>
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/pittsburgh.sc">pittsburgh.sc</a></p>
 <p>Scenery of downtown Pittsburgh. The downtown area is initially located
 to your right.</p></li>
-<li><p><a href="bb.sc">bb.sc</a></p>
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/bb.sc">bb.sc</a></p>
 <p>Simple obstacle course. Try to fly over the buildings and under the
 bridges.</p></li>
-<li><p><a href="pyramids.sc">pyramids.sc</a></p>
+<li><p><a href="1998/banks/pyramids.sc">pyramids.sc</a></p>
 <p>Fly over the tombs of the ancient Pharaohs, in this (fictitious) Egyptian
 landscape.</p></li>
-<li><p><a href="river.sc">river.sc</a></p>
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/river.sc">river.sc</a></p>
 <p>Follow a flowing river from the sky.</p></li>
 </ul>
 <p>A few examples of how to input scenery:</p>
@@ -316,7 +316,7 @@ positive altitudes</em>.</p>
 <p>I’m sure you’ll be making your own scenery files very soon!!!</p>
 <h3 id="alternate-build-instructions">Alternate Build Instructions</h3>
 <p>Several options must be passed to the compiler to make the build
-work. The provided <a href="Makefile">Makefile</a> has the appropriate options set
+work. The provided <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/Makefile">Makefile</a> has the appropriate options set
 to default values. Use this section if you want to compile with
 different options.</p>
 <p>To map a key to a control, you must pass an option to the
@@ -118,17 +118,17 @@ A CGI script such as:
 ```

 can be used to pootify web pages. This has been added as
-[pootify.cgi.sh](pootify.cgi.sh) which forbids `file://` based URLs and which
+[pootify.cgi.sh](%%REPO_URL%%/1998/dlowe/pootify.cgi.sh) which forbids `file://` based URLs and which
 uses `lynx(1)` with the option referred to above. This will not, of course,
 render it as html but rather show the modified html. Nevertheless, this has
 **NOT** been tested as a CGI script with a webserver to display a pootified web
 page.

-The [pootify.sh](pootify.sh) script has also been added which is a modification
+The [pootify.sh](%%REPO_URL%%/1998/dlowe/pootify.sh) script has also been added which is a modification
 to the above script which can be used to render html files locally with the
 added bonus that one can use `file://` URLs. If one wants a CGI script they
 should use the above one instead. You can use the script
-[pootify.sh](pootify.sh), however, to download and generate html files that you
+[pootify.sh](%%REPO_URL%%/1998/dlowe/pootify.sh), however, to download and generate html files that you
 can look at locally in a browser or pipe through `less(1)`. For instance:

 ``` <!---sh-->
@@ -213,16 +213,16 @@ more consistent level of quality. :-)</p>
        fi
    fi</code></pre>
 <p>can be used to pootify web pages. This has been added as
-<a href="pootify.cgi.sh">pootify.cgi.sh</a> which forbids <code>file://</code> based URLs and which
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/pootify.cgi.sh">pootify.cgi.sh</a> which forbids <code>file://</code> based URLs and which
 uses <code>lynx(1)</code> with the option referred to above. This will not, of course,
 render it as html but rather show the modified html. Nevertheless, this has
 <strong>NOT</strong> been tested as a CGI script with a webserver to display a pootified web
 page.</p>
-<p>The <a href="pootify.sh">pootify.sh</a> script has also been added which is a modification
+<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/pootify.sh">pootify.sh</a> script has also been added which is a modification
 to the above script which can be used to render html files locally with the
 added bonus that one can use <code>file://</code> URLs. If one wants a CGI script they
 should use the above one instead. You can use the script
-<a href="pootify.sh">pootify.sh</a>, however, to download and generate html files that you
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/pootify.sh">pootify.sh</a>, however, to download and generate html files that you
 can look at locally in a browser or pipe through <code>less(1)</code>. For instance:</p>
 <pre><code>    ./pootify.sh URL=https://microsoft.com | less

@@ -45,7 +45,7 @@ altering the behavior ?

 ### Extra credit:

-Try doing what the last part of the last command in [try.sh](try.sh) suggests.
+Try doing what the last part of the last command in [try.sh](%%REPO_URL%%/1998/dorssel/try.sh) suggests.
 As in, do the following:

 ``` <!---sh-->
@@ -111,7 +111,7 @@ is the same as
    ./dorssel < dorssel.c | ./dorssel
 ```

- The file [dorssel.md](dorssel.md) contains all the information needed to
+- The file [dorssel.html](dorssel.html) contains all the information needed to
 understand this program.  For an obfuscated spoiler, try

 ``` <!---sh-->
@@ -176,7 +176,7 @@ what values may they be changed without altering the behavior?</p></li>
 altering the behavior ?</p></li>
 </ul>
 <h3 id="extra-credit">Extra credit:</h3>
-<p>Try doing what the last part of the last command in <a href="try.sh">try.sh</a> suggests.
+<p>Try doing what the last part of the last command in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dorssel/try.sh">try.sh</a> suggests.
 As in, do the following:</p>
 <pre><code>    echo &quot;. -..- . .-. -.-. .. ... .
    -.-. .... .- -. --. .  - .... .  .--. .-. --- --. .-. .- --  ... ---  .. -  -.. --- . ...  -. --- -  ... .... --- ..- -&quot; | ./dorssel</code></pre>
@@ -218,7 +218,7 @@ text that can be reversibly Morsified, i.e.</li>
 <p>is the same as</p>
 <pre><code>    ./dorssel &lt; dorssel.c | ./dorssel</code></pre>
 <ul>
-<li>The file <a href="dorssel.md">dorssel.md</a> contains all the information needed to
+<li>The file <a href="dorssel.html">dorssel.html</a> contains all the information needed to
 understand this program. For an obfuscated spoiler, try</li>
 </ul>
 <pre><code>    ./dorssel &lt; dorssel.md</code></pre>
@@ -28,7 +28,7 @@ Enter an expression on standard input.  To try some we have selected:

 ### Historical aside:

-At a time the code in [fanf.c](fanf.c) was that of [fanf.orig.c](fanf.orig.c)
+At a time the code in [fanf.c](%%REPO_URL%%/1998/fanf/fanf.c) was that of [fanf.orig.c](fanf.orig.c)
 but to get this to compile in modern systems it had to be translated to what you
 now see. The intermediate steps can still be performed but they might be
 different from the past. This should be kept in mind as you read the below
@@ -38,10 +38,10 @@ This program translates lambda expressions into combinator
 expressions.  But you do not need to know Lambda Calculus to be
 impressed by this program!

-See the file [fanf.lambda](fanf.lambda) for more examples of lambda calculus
+See the file [fanf.lambda](%%REPO_URL%%/1998/fanf/fanf.lambda) for more examples of lambda calculus
 source.

-Notice how large the code grows from the [fanf.c](fanf.c) into the final
+Notice how large the code grows from the [fanf.c](%%REPO_URL%%/1998/fanf/fanf.c) into the final
 `fanftmp2.c` C program.  Take a look at that final C program again,
 can you begin to understand what it is doing?

@@ -163,7 +163,7 @@ this entry because of the system resources it requires.</p>
 <pre><code>    ./try.sh</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <h3 id="historical-aside">Historical aside:</h3>
-<p>At a time the code in <a href="fanf.c">fanf.c</a> was that of <a href="fanf.orig.c">fanf.orig.c</a>
+<p>At a time the code in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/fanf/fanf.c">fanf.c</a> was that of <a href="fanf.orig.c">fanf.orig.c</a>
 but to get this to compile in modern systems it had to be translated to what you
 now see. The intermediate steps can still be performed but they might be
 different from the past. This should be kept in mind as you read the below
@@ -171,9 +171,9 @@ remarks.</p>
 <p>This program translates lambda expressions into combinator
 expressions. But you do not need to know Lambda Calculus to be
 impressed by this program!</p>
-<p>See the file <a href="fanf.lambda">fanf.lambda</a> for more examples of lambda calculus
+<p>See the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/fanf/fanf.lambda">fanf.lambda</a> for more examples of lambda calculus
 source.</p>
-<p>Notice how large the code grows from the <a href="fanf.c">fanf.c</a> into the final
+<p>Notice how large the code grows from the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/fanf/fanf.c">fanf.c</a> into the final
 <code>fanftmp2.c</code> C program. Take a look at that final C program again,
 can you begin to understand what it is doing?</p>
 <p>Look at the first stage of the C pre-processing which was done like:</p>
@@ -109,7 +109,7 @@ itself. Just load it in your favorite editor.

 `gcc` (the GNU C compiler) must be available at runtime. It is assumed that your
 C implementation keeps headers as files in the `/usr/include` directory. The
-[info](info) file must be readable and reside in the current working directory.
+[info](%%REPO_URL%%/1998/schweikh1/info) file must be readable and reside in the current working directory.
 The current working directory must be writable in order to create a temporary
 file (which is removed upon program termination). In case you don't have gcc at
 runtime, not all is lost if your compiler or preprocessor can produce a list of
@@ -219,7 +219,7 @@ itself. Just load it in your favorite editor.</p>
 <h3 id="requirements">Requirements</h3>
 <p><code>gcc</code> (the GNU C compiler) must be available at runtime. It is assumed that your
 C implementation keeps headers as files in the <code>/usr/include</code> directory. The
-<a href="info">info</a> file must be readable and reside in the current working directory.
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/schweikh1/info">info</a> file must be readable and reside in the current working directory.
 The current working directory must be writable in order to create a temporary
 file (which is removed upon program termination). In case you don’t have gcc at
 runtime, not all is lost if your compiler or preprocessor can produce a list of
@@ -81,7 +81,7 @@ Thank God the IEEE does not standardize a coding style...
 ###    What this program does

 This is best explained in the man page. The troff source for this
-man page can be found in the file [samefile.1](samefile.1). To render try:
+man page can be found in the file [samefile.1](%%REPO_URL%%/1998/schweikh3/samefile.1). To render try:

 ``` <!---sh-->
    `man ./samefile.1
@@ -192,7 +192,7 @@ the tool as well at <a href="http://www.schweikhardt.net/samefile" class="uri">h
 Thank God the IEEE does not standardize a coding style…</p>
 <h3 id="what-this-program-does">What this program does</h3>
 <p>This is best explained in the man page. The troff source for this
-man page can be found in the file <a href="samefile.1">samefile.1</a>. To render try:</p>
+man page can be found in the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/schweikh3/samefile.1">samefile.1</a>. To render try:</p>
 <pre><code>    `man ./samefile.1</code></pre>
 <p>Otherwise:</p>
 <h3 id="samefile1-user-manuals-samefile1">SAMEFILE(1) User Manuals SAMEFILE(1)</h3>
@@ -39,12 +39,12 @@ them with cool layout!

 For your enjoyment:

-1. Compile [dhyang.c](dhyang.c).
+1. Compile [dhyang.c](%%REPO_URL%%/2000/dhyang/dhyang.c).
 2. Run `./dhyang` and redirect output to another `.c` file.
 3. Compile that file.
 4. Repeat steps 2 and 3 until eventually the output cycles.

-To interpret the output: the [dhyang.c](dhyang.c.c) is an image of Saitou
+To interpret the output: the [dhyang.c](%%REPO_URL%%/2000/dhyang/dhyang.c.c) is an image of Saitou
 Hajime, which eventually generates three sources files that are images of "aku
 soku zan" (sin swift slay), Saitou's motto ;)

@@ -52,7 +52,7 @@ For best viewing, set tab spaces to 8 characters, and set your
 terminal fonts to as close to square as possible.  I hate to do this
 but you know, size...

-[dhyang.c](dhyang.c) and all its output compiles with gcc if your OS uses ASCII
+[dhyang.c](%%REPO_URL%%/2000/dhyang/dhyang.c) and all its output compiles with gcc if your OS uses ASCII
 character set.  No file is included and all functions assume default `int` return
 type (a source of compile warnings).

@@ -171,18 +171,18 @@ program that generates a set of mutually reproducing programs, all of
 them with cool layout!</p>
 <p>For your enjoyment:</p>
 <ol type="1">
-<li>Compile <a href="dhyang.c">dhyang.c</a>.</li>
+<li>Compile <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dhyang/dhyang.c">dhyang.c</a>.</li>
 <li>Run <code>./dhyang</code> and redirect output to another <code>.c</code> file.</li>
 <li>Compile that file.</li>
 <li>Repeat steps 2 and 3 until eventually the output cycles.</li>
 </ol>
-<p>To interpret the output: the <a href="dhyang.c.c">dhyang.c</a> is an image of Saitou
+<p>To interpret the output: the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dhyang/dhyang.c.c">dhyang.c</a> is an image of Saitou
 Hajime, which eventually generates three sources files that are images of “aku
 soku zan” (sin swift slay), Saitou’s motto ;)</p>
 <p>For best viewing, set tab spaces to 8 characters, and set your
 terminal fonts to as close to square as possible. I hate to do this
 but you know, size…</p>
-<p><a href="dhyang.c">dhyang.c</a> and all its output compiles with gcc if your OS uses ASCII
+<p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dhyang/dhyang.c">dhyang.c</a> and all its output compiles with gcc if your OS uses ASCII
 character set. No file is included and all functions assume default <code>int</code> return
 type (a source of compile warnings).</p>
 <!--
@@ -141,14 +141,14 @@ Finish the formula with `!` to create the histogram.
 #### 2.2. Starting and Loading Spreadsheets

 To start the spreadsheet program with an existing
-spreadsheet, for instance [finance.sheet](finance.sheet), use the following
+spreadsheet, for instance [finance.sheet](%%REPO_URL%%/2000/jarijyrki/finance.sheet), use the following
 command line:

 ``` <!---sh-->
    ./jarijyrki < finance.sheet
 ```

-The file [finance.sheet](finance.sheet) has been provided as an example.  This
+The file [finance.sheet](%%REPO_URL%%/2000/jarijyrki/finance.sheet) has been provided as an example.  This
 file contains a set of financial numbers and two graphical entities - a pie
 chart and a histogram - based on them. We recommend starting the use of the
 program from this file, as a way to study and learn the formula language
@@ -184,7 +184,7 @@ Below the Formula Area is the Column Letters Area: `A`, `B`, and so on.
 Correspondingly, on the left side of the window is the Row Numbers Area: `1`, `2`,
 and so on.  The rest of the window is dedicated to the actual spreadsheet cells.

-The example spreadsheet, [finance.sheet](finance.sheet), provided with this
+The example spreadsheet, [finance.sheet](%%REPO_URL%%/2000/jarijyrki/finance.sheet), provided with this
 program contains two sets of numbers in the visible area of the spreadsheet. The
 top set of numbers forms the product-by-product turnover breakdown of an
 imaginary company. Below it is the yearly development of the company profits. On
@@ -226,10 +226,10 @@ character at the end of the formula; press backspace to delete the last one.</p>
 <p>Finish the formula with <code>!</code> to create the histogram.</p>
 <h4 id="starting-and-loading-spreadsheets">2.2. Starting and Loading Spreadsheets</h4>
 <p>To start the spreadsheet program with an existing
-spreadsheet, for instance <a href="finance.sheet">finance.sheet</a>, use the following
+spreadsheet, for instance <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/jarijyrki/finance.sheet">finance.sheet</a>, use the following
 command line:</p>
 <pre><code>    ./jarijyrki &lt; finance.sheet</code></pre>
-<p>The file <a href="finance.sheet">finance.sheet</a> has been provided as an example. This
+<p>The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/jarijyrki/finance.sheet">finance.sheet</a> has been provided as an example. This
 file contains a set of financial numbers and two graphical entities - a pie
 chart and a histogram - based on them. We recommend starting the use of the
 program from this file, as a way to study and learn the formula language
@@ -250,7 +250,7 @@ currently selected cell. The program starts with <code>A1</code> as being the cu
 Below the Formula Area is the Column Letters Area: <code>A</code>, <code>B</code>, and so on.
 Correspondingly, on the left side of the window is the Row Numbers Area: <code>1</code>, <code>2</code>,
 and so on. The rest of the window is dedicated to the actual spreadsheet cells.</p>
-<p>The example spreadsheet, <a href="finance.sheet">finance.sheet</a>, provided with this
+<p>The example spreadsheet, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/jarijyrki/finance.sheet">finance.sheet</a>, provided with this
 program contains two sets of numbers in the visible area of the spreadsheet. The
 top set of numbers forms the product-by-product turnover breakdown of an
 imaginary company. Below it is the yearly development of the company profits. On
@@ -25,8 +25,8 @@ There is an alternate version that compiles [mkentry.c](mkentry.c). See
 ## Alternate code:

 This alternate code is based on the author's remarks with a slight fix so that
-it will do what it once did, compile and run [mkentry.c](mkentry.c). You can use
-it in a similar way as [tomx.c](tomx.c), both executing the source file and
+it will do what it once did, compile and run [mkentry.c](%%REPO_URL%%/2000/tomx/mkentry.c). You can use
+it in a similar way as [tomx.c](%%REPO_URL%%/2000/tomx/tomx.c), both executing the source file and
 using it as a Makefile and running the code ends up running `mkentry`.


@@ -98,7 +98,7 @@ like a C program.
 program that it is. It is possible to do `#include "prog2.c"` in the place of
 the `main()`, leaving the complexities of the C file elsewhere and making this
 source still acceptable to `make` and `sh`. The following modification to the
-last few lines will compile the IOCCC's famous [mkentry.c](mkentry.c).
+last few lines will compile the IOCCC's famous [mkentry.c](%%REPO_URL%%/2000/tomx/mkentry.c).

 ```
    .PHONY: /* true clean */
@@ -162,8 +162,8 @@ Location: <a href="../../location.html#NL">NL</a> - <em>Kingdom of the Netherlan
 <pre><code>    ./try.sh</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
 <p>This alternate code is based on the author’s remarks with a slight fix so that
-it will do what it once did, compile and run <a href="mkentry.c">mkentry.c</a>. You can use
-it in a similar way as <a href="tomx.c">tomx.c</a>, both executing the source file and
+it will do what it once did, compile and run <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/tomx/mkentry.c">mkentry.c</a>. You can use
+it in a similar way as <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/tomx/tomx.c">tomx.c</a>, both executing the source file and
 using it as a Makefile and running the code ends up running <code>mkentry</code>.</p>
 <h3 id="alternate-build">Alternate build:</h3>
 <pre><code>    make alt</code></pre>
@@ -210,7 +210,7 @@ like a C program.</p></li>
 program that it is. It is possible to do <code>#include "prog2.c"</code> in the place of
 the <code>main()</code>, leaving the complexities of the C file elsewhere and making this
 source still acceptable to <code>make</code> and <code>sh</code>. The following modification to the
-last few lines will compile the IOCCC’s famous <a href="mkentry.c">mkentry.c</a>.</li>
+last few lines will compile the IOCCC’s famous <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/tomx/mkentry.c">mkentry.c</a>.</li>
 </ol>
 <pre><code>    .PHONY: /* true clean */
    #undef   true
@@ -5,7 +5,7 @@
 ```

 The programs that this program is supposed to act on,
-[anonymous.ten.c](anonymous.ten.c) and [anonymous.bed.c](anonymous.bed.c),
+[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
 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
@@ -47,7 +47,7 @@ set to) and run it directly.
 What happens if the x86 program has already been modified by this program? The
 judges' remarks below might give you a hint!

-What happens if you try it on another file like [anonymous.c](anonymous.c)? Can
+What happens if you try it on another file like [anonymous.c](%%REPO_URL%%/2001/anonymous/anonymous.c)? Can
 you recompile it okay? What if you run it on `anonymous` itself? Can you run the
 program successfully after it without recompiling?

@@ -218,10 +218,10 @@ In short, please consider this a full disclaimer for any bug that may
 turn up - yes the program is unsafe, but it's pretty cool anyway.

 Despite all this, the translator is not exclusively limited to running the
-[anonymous.ten](anonymous.ten.c) program.  Other trivial **_x86_** programs may
+[anonymous.ten](%%REPO_URL%%/2001/anonymous/anonymous.ten.c) program.  Other trivial **_x86_** programs may
 run on the translator \- and I have successfully run a wide range of "Hello
 World" programs, including one of last year's IOCCC entries,
-[tomx](../../2000/tomx/tomx.c).
+[tomx](2001/anonymous/2000/tomx/tomx.c).


 ### Complete Program
@@ -233,7 +233,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](../../2000/dhyang/dhyang.c); both are
+program and one like last year's entry [dhyang](%%REPO_URL%%/2000/dhyang/dhyang.c); both are
 just C programs that generate C code as their output.

 Enjoy and thanks!
@@ -155,7 +155,7 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
 <p>The programs that this program is supposed to act on,
-<a href="anonymous.ten.c">anonymous.ten.c</a> and <a href="anonymous.bed.c">anonymous.bed.c</a>,
+<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
 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
@@ -177,7 +177,7 @@ whatever your system will compile them as).</p>
 set to) and run it directly.</p>
 <p>What happens if the x86 program has already been modified by this program? The
 judges’ remarks below might give you a hint!</p>
-<p>What happens if you try it on another file like <a href="anonymous.c">anonymous.c</a>? Can
+<p>What happens if you try it on another file like <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.c">anonymous.c</a>? Can
 you recompile it okay? What if you run it on <code>anonymous</code> itself? Can you run the
 program successfully after it without recompiling?</p>
 <h2 id="alternate-code">Alternate code:</h2>
@@ -295,10 +295,10 @@ can only pass up to 3 parameters to the target library function, etc.</p>
 <p>In short, please consider this a full disclaimer for any bug that may
 turn up - yes the program is unsafe, but it’s pretty cool anyway.</p>
 <p>Despite all this, the translator is not exclusively limited to running the
-<a href="anonymous.ten.c">anonymous.ten</a> program. Other trivial <strong><em>x86</em></strong> programs may
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.ten.c">anonymous.ten</a> program. Other trivial <strong><em>x86</em></strong> programs may
 run on the translator - and I have successfully run a wide range of “Hello
 World” programs, including one of last year’s IOCCC entries,
-<a href="../../2000/tomx/tomx.c">tomx</a>.</p>
+<a href="2001/anonymous/2000/tomx/tomx.c">tomx</a>.</p>
 <h3 id="complete-program">Complete Program</h3>
 <p>The fact that the program makes calls to <code>system(3)</code> and <code>execv(3)</code> may imply that
 it is not a complete program in its own right, as it relies on other programs.
@@ -307,7 +307,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="../../2000/dhyang/dhyang.c">dhyang</a>; both are
+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
 just C programs that generate C code as their output.</p>
 <p>Enjoy and thanks!</p>
 <!--
@@ -54,7 +54,7 @@ You can use it by typing:
 or by giving the C source to its standard input.

 `args` are given to the `main()` function of `bellard.c` (`argv[0]` is
-[bellard.c](bellard.c)).
+[bellard.c](%%REPO_URL%%/2001/bellard/bellard.c)).


 ### Examples:
@@ -176,7 +176,7 @@ program.</p>
 <pre><code>    ./bellard bellard.c [args]...</code></pre>
 <p>or by giving the C source to its standard input.</p>
 <p><code>args</code> are given to the <code>main()</code> function of <code>bellard.c</code> (<code>argv[0]</code> is
-<a href="bellard.c">bellard.c</a>).</p>
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/bellard/bellard.c">bellard.c</a>).</p>
 <h3 id="examples">Examples:</h3>
 <ul>
 <li>Sample compilation and execution:</li>
@@ -39,8 +39,8 @@ of sight: this program is a self-contained speech synthesizer that
 tells the current time through the computer's sound card - in just under
 2 Kb of source code !

-In the 2001 IOCCC [rules](../../2001/rules.txt) and
-[guidelines](../../2001/guidelines.txt) documents, there is no mention of
+In the 2001 IOCCC [rules](../rules.txt) and
+[guidelines](../guidelines.txt) documents, there is no mention of
 what is or isn't acceptable regarding audio I/O, but it is mentioned
 that hardware-specific and/or non-portable programs are not welcome. So,
 in order to do audio and satisfy those requirements, the format required
@@ -172,8 +172,8 @@ to read obviously): when they interact with the user, they only
 of sight: this program is a self-contained speech synthesizer that
 tells the current time through the computer’s sound card - in just under
 2 Kb of source code !</p>
-<p>In the 2001 IOCCC <a href="../../2001/rules.txt">rules</a> and
-<a href="../../2001/guidelines.txt">guidelines</a> documents, there is no mention of
+<p>In the 2001 IOCCC <a href="../rules.txt">rules</a> and
+<a href="../guidelines.txt">guidelines</a> documents, there is no mention of
 what is or isn’t acceptable regarding audio I/O, but it is mentioned
 that hardware-specific and/or non-portable programs are not welcome. So,
 in order to do audio and satisfy those requirements, the format required
@@ -83,7 +83,7 @@ terminal!

 #### For the impatient

-The info files `herrmann1.turing` and [herrmann1.gcd](herrmann1.gcd) are sample
+The info files `herrmann1.turing` and [herrmann1.gcd](%%REPO_URL%%/2001/herrmann1/herrmann1.gcd) are sample
 programs for the Turing machine. For example, type

 ``` <!---sh-->
@@ -202,7 +202,7 @@ terminal!</p></li>
 </ul>
 <h3 id="how-to-use-it">How to use it</h3>
 <h4 id="for-the-impatient">For the impatient</h4>
-<p>The info files <code>herrmann1.turing</code> and <a href="herrmann1.gcd">herrmann1.gcd</a> are sample
+<p>The info files <code>herrmann1.turing</code> and <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann1/herrmann1.gcd">herrmann1.gcd</a> are sample
 programs for the Turing machine. For example, type</p>
 <pre><code>    ./herrmann1.sh &#39;prg=herrmann1.times2&#39;</code></pre>
 <p>and watch the animated Turing machine multiply 8 by two (in
@@ -18,8 +18,8 @@
    ./try.sh
 ```

-If you use vi(m) you can see a pattern in [herrmann2.cup](herrmann2.cup) and
-[herrmann2.ioccc][(herrmann2.ioccc]) by say:
+If you use vi(m) you can see a pattern in [herrmann2.cup](%%REPO_URL%%/2001/herrmann2herrmann2.cup) and
+[herrmann2.ioccc][(%%REPO_URL%%/2001/herrmann2herrmann2.ioccc]) by say:


 ```
@@ -32,7 +32,7 @@ and
    /l
 ```

-For additional fun in [herrmann2.cup](herrmann2.cup) try:
+For additional fun in [herrmann2.cup](%%REPO_URL%%/2001/herrmann2herrmann2.cup) try:


 ```
@@ -40,7 +40,7 @@ For additional fun in [herrmann2.cup](herrmann2.cup) try:
    /q
 ```

-and in [herrmann2.ioccc](herrmann2.ioccc) try:
+and in [herrmann2.ioccc](%%REPO_URL%%/2001/herrmann2herrmann2.ioccc) try:

 ```
    /n
@@ -158,15 +158,15 @@ Location: <a href="../../location.html#DE">DE</a> - <em>Federal Republic of Germ
 <pre><code>    ./herrmann2</code></pre>
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh</code></pre>
-<p>If you use vi(m) you can see a pattern in <a href="herrmann2.cup">herrmann2.cup</a> and
-[herrmann2.ioccc][(herrmann2.ioccc]) by say:</p>
+<p>If you use vi(m) you can see a pattern in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2herrmann2.cup">herrmann2.cup</a> and
+[herrmann2.ioccc][(https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2herrmann2.ioccc]) by say:</p>
 <pre><code>    /[pon]\</code></pre>
 <p>and</p>
 <pre><code>    /l</code></pre>
-<p>For additional fun in <a href="herrmann2.cup">herrmann2.cup</a> try:</p>
+<p>For additional fun in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2herrmann2.cup">herrmann2.cup</a> try:</p>
 <pre><code>    /[po]
    /q</code></pre>
-<p>and in <a href="herrmann2.ioccc">herrmann2.ioccc</a> try:</p>
+<p>and in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2herrmann2.ioccc">herrmann2.ioccc</a> try:</p>
 <pre><code>    /n</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>Be careful when staring at the source code - your eyes might cross, but
@@ -163,7 +163,7 @@ the name of the machine running the server, e.g.
 ```

 Make sure that the terminals on both ends are the same size.  Also, the TCP port
-number (by default 5455) specified in the [Makefile](Makefile) mustn't be
+number (by default 5455) specified in the [Makefile](%%REPO_URL%%/2001/kev/Makefile) mustn't be
 blocked by a firewall.

 Here's a good quick example to see it in action on your own
@@ -229,7 +229,7 @@ getting the ball past your opponent’s paddle. It’s pretty fun! :)</p>
 the name of the machine running the server, e.g.</p>
 <pre><code>    ./kev localhost</code></pre>
 <p>Make sure that the terminals on both ends are the same size. Also, the TCP port
-number (by default 5455) specified in the <a href="Makefile">Makefile</a> mustn’t be
+number (by default 5455) specified in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/kev/Makefile">Makefile</a> mustn’t be
 blocked by a firewall.</p>
 <p>Here’s a good quick example to see it in action on your own
 machine, assuming you have <code>Xwindows</code>:</p>
@@ -54,7 +54,7 @@ This is compiled by default; use `westley.sort` as you would `westley` above.

 The author also stated that if you just sort the code you'll get the with
 `sort`) version that just prints out the punch card. The
-[westley.punch.c](westley.punch.c) code is specifically so that Westley can punch
+[westley.punch.c](%%REPO_URL%%/2001/westley/westley.punch.c) code is specifically so that Westley can punch
 everyone in the face! :-) This is also compiled by default.


@@ -67,7 +67,7 @@ everyone in the face! :-) This is also compiled by default.

 ## Alternate code:

-An alternate version of this entry, [westley.alt.c](westley.alt.c), is provided.
+An alternate version of this entry, [westley.alt.c](%%REPO_URL%%/2001/westley/westley.alt.c), is provided.
 This alternate code might be less portable.


@@ -180,12 +180,12 @@ code by line and it will always sort the order of the input.</p>
 <h2 id="punch-card-code">Punch card code:</h2>
 <p>The author also stated that if you just sort the code you’ll get the with
 <code>sort</code>) version that just prints out the punch card. The
-<a href="westley.punch.c">westley.punch.c</a> code is specifically so that Westley can punch
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/westley/westley.punch.c">westley.punch.c</a> code is specifically so that Westley can punch
 everyone in the face! :-) This is also compiled by default.</p>
 <h3 id="punch-card-try">Punch card try:</h3>
 <pre><code>    echo &#39;Brian Westley does it again!&#39; | ./westley.punch 2&gt;/dev/null</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
-<p>An alternate version of this entry, <a href="westley.alt.c">westley.alt.c</a>, is provided.
+<p>An alternate version of this entry, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/westley/westley.alt.c">westley.alt.c</a>, is provided.
 This alternate code might be less portable.</p>
 <h3 id="alternate-build">Alternate build:</h3>
 <pre><code>    make alt</code></pre>