fix many internal links

Fixed a number of internal links that need to
go to the GitHub site.

Ran `make www` to perform the above.

1998/banks/README.md

@@ -219,7 +219,7 @@ Here is a brief description of the scenery files:
     Simple obstacle course.  Try to fly over the buildings and under the
     bridges.
 
-- [pyramids.sc](1998/banks/pyramids.sc)
+- [pyramids.sc](%%REPO_URL%%/1998/banks/pyramids.sc)
 
     Fly over the tombs of the ancient Pharaohs, in this (fictitious) Egyptian
     landscape.

1998/banks/index.html

@@ -519,7 +519,7 @@ to your right.</p></li>
 <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="1998/banks/pyramids.sc">pyramids.sc</a></p>
+<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/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="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/river.sc">river.sc</a></p>

1998/fanf/README.md

@@ -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](%%REPO_URL%%/1998/fanf/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](%%REPO_URL%%/1998/fanf/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

1998/fanf/index.html

@@ -388,7 +388,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="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>
+<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="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/fanf/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

1998/schnitzi/README.md

@@ -78,7 +78,7 @@ the letter `e`.
 The IOCCC has been no stranger to this concept.  Several winning entries from
 years past have accomplished interesting feats while completely avoiding the use
 of certain C constructs thought to be essential (e.g.
-[1988/robison.c](../../1988/robison/robison.c)).  If you have to ask why they would
+[1988/robison.c](%%REPO_URL%%/1988/robison/robison.c)).  If you have to ask why they would
 do it this way, then this contest just isn't for you.
 
 In continuing with this fine tradition, this program suggests to the ANSI

1998/schnitzi/index.html

@@ -422,7 +422,7 @@ the letter <code>e</code>.</p>
 <p>The IOCCC has been no stranger to this concept. Several winning entries from
 years past have accomplished interesting feats while completely avoiding the use
 of certain C constructs thought to be essential (e.g.
-<a href="../../1988/robison/robison.c">1988/robison.c</a>). If you have to ask why they would
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/robison/robison.c">1988/robison.c</a>). If you have to ask why they would
 do it this way, then this contest just isn’t for you.</p>
 <p>In continuing with this fine tradition, this program suggests to the ANSI
 committee some new practical simplifications for the C language. For instance,

1998/schweikh1/README.md

@@ -247,7 +247,7 @@ printer when you make a hard copy of the source...
 
 While I'm at it, the rules state that only space, tab and newline
 are ignored for the count (plus '`{`', '`}`', '`;`' followed by
-whitespace). The [mkentry.c](../mkentry.c) program, however, uses `isspace(3)` which
+whitespace). The [mkentry.c](%%REPO_URL%%/1998/mkentry.c) program, however, uses `isspace(3)` which
 returns nonzero for `\v` and `\f` and other characters as well.
 I could have used a lot more `^K` and `^L` probably undetected by your
 counter but decided to err on the side of safety. I use a perl

1998/schweikh1/index.html

@@ -546,7 +546,7 @@ something new – after 14 years of IOCCC. Be sure to have enough paper in your
 printer when you make a hard copy of the source…</p>
 <p>While I’m at it, the rules state that only space, tab and newline
 are ignored for the count (plus ‘<code>{</code>’, ‘<code>}</code>’, ‘<code>;</code>’ followed by
-whitespace). The <a href="../mkentry.c">mkentry.c</a> program, however, uses <code>isspace(3)</code> which
+whitespace). The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/mkentry.c">mkentry.c</a> program, however, uses <code>isspace(3)</code> which
 returns nonzero for <code>\v</code> and <code>\f</code> and other characters as well.
 I could have used a lot more <code>^K</code> and <code>^L</code> probably undetected by your
 counter but decided to err on the side of safety. I use a perl