checkpoint on fixing topbar for non-JavaScript browsers

2019/adamovsky/README.md

@@ -73,7 +73,7 @@ separator in the form of a single line followed by a section signifying the
 function of the program, a block with removed shape of lambda character. Even
 the official IOCCC size tool acknowledges this: When you call `./iocccsize -i
 <prog.c`, using the [2019 version of
-iocccsize](%%REPO_URL%%/2019/iocccsize.c), iocccsize returns **955**,
+iocccsize.c](%%REPO_URL%%/2019/iocccsize.c), iocccsize returns **955**,
 which is the Unicode codepoint of the **&#955;** character.
 
 It might be a surprise for you that according to the IOCCC size tool the program is
@@ -103,7 +103,7 @@ You can also try other programs from the Web. Many example programs are in the o
 entries from [quine contest][4].
 
 There is an alternative build path that requires the 2018 IOCCC size tool to complete. Put the tool
-source [iocccsize_2018.c](%%REPO_URL%%/2019/adamovskyiocccsize_2018.c) in the project directory and call
+source [iocccsize_2018.c](%%REPO_URL%%/2019/adamovsky/iocccsize_2018.c) in the project directory and call
 
 ``` <!---sh-->
     make identify
@@ -199,7 +199,7 @@ since it was developed using `char`s it should be always used safely.
 
 ### Spoilers:
 
-- You can examine the [progSpoiler.c](%%REPO_URL%%/2019/adamovskyprogSpoiler.c) file. It is the original
+- You can examine the [progSpoiler.c](%%REPO_URL%%/2019/adamovsky/progSpoiler.c) file. It is the original
 final version of the interpreter, before I started the downsizing. It accepts
 one more optional parameter that specifies a filename for the output Unlambda
 function (it's the Unlambda function that remains after all function

2019/ciura/README.md

@@ -163,7 +163,7 @@ among the programs that won IOCCC in the past), and _obscure bugs_ (see
 the questions about Linux core dumps below).
 
 To a casual eye, this entry may look similar to
-[2005/klausler](%%REPO_URL%%/2005/klausler/index.html).
+[2005/klausler](../../2005/klausler/index.html).
 However, `prog` is internationalized and way faster. On my machine,
 `./klausler abcdefghijklmnopqrstuvwxyz` printed only 3,965 perfect
 pangrams until I killed it after 144 hours running, while the

2019/diels-grabsch1/README.md

@@ -54,7 +54,7 @@ compresses differently? The judges know. :)
     diff -s guidelines.txt guidelines2.txt
 ```
 
-Of course you can  also use [2015/mills2](%%REPO_URL%%/2015/mills2/mills2.c) instead of
+Of course you can  also use [2015/mills2prog.c](%%REPO_URL%%/2015/mills2/prog.c) instead of
 `zcat` to verify the output file. The achieved compression ratio roughly matches
 that of the classic Unix `compress(1)` tool. And the source code is very
 compressed, too: It has exactly the same size as the  paragraph you are reading

2019/dogon/README.md

@@ -35,8 +35,8 @@ the program and the script.
 
 ## Judges' remarks:
 
-[1991/davidguy](%%REPO_URL%%/1991/davidguy/index.html),
-[2011/blakely](%%REPO_URL%%/2011/blakely/index.html), ...
+[1991/davidguy](../..//1991/davidguy/index.html),
+[2011/blakely](../../2011/blakely/index.html), ...
 
 ...This entry likely concludes the IOCCC category "Cellular automata simulators";
 it would be very hard to beat it on its field.

2019/poikola/README.md

@@ -162,7 +162,7 @@ White](https://www.glyphweb.com/arda/g/gandalf.html) and the [Judges of
 the IOCCC](../../judges.html).
 
 Output of `iocccsize`, using the [2019 version of
-iocccsize](%%REPO_URL%%/2019/iocccsize.c), is carefully selected.  For
+iocccsize](%%REPO_URL%%/2019/poikola/iocccsize.c), is carefully selected.  For
 the sake of clarity, I used single letter variables in the code. I also avoided
 unnecessary use of functions.  Like a
 [tripundra](https://en.wikipedia.org/wiki/Tripundra), this program has three