update year level README files

Move copyright notice to the end.

Add a standard comment about the newly added `README.md` files.

Clean up trailing whitespace.

Fixed a few minor typos.

1984/README

@@ -1,10 +1,18 @@
 In 1984, the first contest was held.  The name of the contest was simply
 ``Obfuscated C Code Contest''.
 
+
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 Restrictions against machine dependent code were not in the rules in 1984.
 The source file size restriction was only 512 bytes.  Rules and results
 were posted to net.lang.c and net.unix-wizards.
 
+=-=
+
 Copyright (c) 1984, Landon Curt Noll.
 All Rights Reserved.  Permission for personal, educational or non-profit use is
 granted provided this this copyright and notice are included in its entirety

1985/README

@@ -1,4 +1,10 @@
-185 marked the second year of the Obfuscated C Code Contest.
+1985 marked the second year of the Obfuscated C Code Contest.
+
+
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
 
 Hints against machine dependent code were added to the rules to avoid
 another 1984 style winner.  Rules and results were posted to net.lang.c
@@ -6,6 +12,8 @@ and net.unix-wizards.  Larry Bassel was invited to help in the
 judging.  Awards were given to 5 classes of programs since we were
 unable to select only the best 4.
 
+=-=
+
 Copyright (c) 1985, Landon Curt Noll & Larry Bassel.
 All Rights Reserved.  Permission for personal, educational or non-profit use is
 granted provided this this copyright and notice are included in its entirety

1986/README

@@ -1,10 +1,10 @@
 The 1986 contest was named: "The Third International Obfuscated C Code Contest"
 
-Copyright (c) 1986, Landon Curt Noll & Larry Bassel.
+
-All Rights Reserved.  Permission for personal, educational or non-profit use is
+Look at the README.md file for the given winner for information
-granted provided this this copyright and notice are included in its entirety
+on how to compile the winner and how to run the winning program.
-and remains unaltered.  All other uses must receive prior permission in writing
+Look at the winning source and try to figure how it does what it does!
-from both Landon Curt Noll and Larry Bassel.
+You may then wish to look at the Author's comments for even more details.
 
 The rules for 1986 suggested categories due to the success of the 1985
 judging method.  The maximum size was increased from 512 to 1024 bytes.
@@ -18,3 +18,11 @@ Rules and results were posted to net.lang.c and net.unix-wizards.
 Micro/Systems Journal published started regular publishing of the winners.
 The practice of making first announcement of the winners at the Summer
 Usenix BOF started this year.  A notice was posted to net.announce.
+
+=-=
+
+Copyright (c) 1986, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1987/README

@@ -1,10 +1,10 @@
 1987 marked the "The Fourth International Obfuscated C Code Contest"
 
-Copyright (c) 1987, Landon Curt Noll & Larry Bassel.
+
-All Rights Reserved.  Permission for personal, educational or non-profit use is
+Look at the README.md file for the given winner for information
-granted provided this this copyright and notice are included in its entirety
+on how to compile the winner and how to run the winning program.
-and remains unaltered.  All other uses must receive prior permission in writing
+Look at the winning source and try to figure how it does what it does!
-from both Landon Curt Noll and Larry Bassel.
+You may then wish to look at the Author's comments for even more details.
 
 The rules for 1987 suggested even more categories than in 1986.  Hints
 for what to do and not to do were also given in the rules.  For
@@ -19,3 +19,11 @@ published the 1987 winners.  Mark Horton included a version of the 1987
 winners in an appendix of his C book.  The first announcement of
 winners at the Summer 87 Usenix was helped by a small fly that
 danced all over the foils.
+
+=-=
+
+Copyright (c) 1987, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1988/README

@@ -1,10 +1,10 @@
 1988 marked the "The Fifth International Obfuscated C Code Contest"
 
-Copyright (c) 1988, Landon Curt Noll & Larry Bassel.
+
-All Rights Reserved.  Permission for personal, educational or non-profit use is
+Look at the README.md file for the given winner for information
-granted provided this this copyright and notice are included in its entirety
+on how to compile the winner and how to run the winning program.
-and remains unaltered.  All other uses must receive prior permission in writing
+Look at the winning source and try to figure how it does what it does!
-from both Landon Curt Noll and Larry Bassel.
+You may then wish to look at the Author's comments for even more details.
 
 The maximum size of entries was raised from 1024 to 1536 bytes, however
 smaller entries were encouraged.  Due to the "Best Abuse of the Rules"
@@ -21,3 +21,11 @@ Winning entries for previous years were repackaged with each year
 being in its own directory.  Make files and hints were also provided.
 The package was posted to the: comp.sources.unix newsgroup.  They are
 also available on a wide number of Usenet archive sites.
+
+=-=
+
+Copyright (c) 1988, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1989/README

@@ -1,16 +1,14 @@
 1989 marked the "The Sixth International Obfuscated C Code Contest"
 
-Copyright (c) 1989, Landon Curt Noll & Larry Bassel.
+
-All Rights Reserved.  Permission for personal, educational or non-profit use is
+Look at the README.md file for the given winner for information
-granted provided this this copyright and notice are included in its entirety
+on how to compile the winner and how to run the winning program.
-and remains unaltered.  All other uses must receive prior permission in writing
+Look at the winning source and try to figure how it does what it does!
-from both Landon Curt Noll and Larry Bassel.
+You may then wish to look at the Author's comments for even more details.
 
 Instructions for use: Run make to compile entries (it is possible
 that on System V or non-unix systems the makefile needs to be
-changed). Look at the source and try to figure out what the programs
+changed).
-do, and run them with various inputs. If you want to, look at the
-hints files for (minor) spoilers.
 
 This year, the Grand Prize was given to the most useful program.
 
@@ -18,8 +16,7 @@ The "Strangest abuse of the rules" award was given this year to stress
 the fact that starting in 1990, compiling entries must result an
 executable regular file.
 
-In two other cases, we included System V portable versions of winning
+The makefile always uses the portable version of the "Best
-programs.  The makefile always uses the portable version of the "Best
 self modifying program" because there as no loss of functionality in
 using it.  In the case of the "Best game" winner, however, some
 functionality is lost in the portable version and so the makefile uses
@@ -30,3 +27,11 @@ Rules and results were posted to comp.lang.c, comp.sources.unix, and
 alt.sources.  They have been made available on a wide number of Usenet
 archive sites such as uunet.  The 1989 winners will be published in the
 Micro/Systems Journal.
+
+=-=
+
+Copyright (c) 1989, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1990/README

@@ -1,18 +1,10 @@
 1990 marked the "The Seventh International Obfuscated C Code Contest"
 
-Copyright (c) 1990, Landon Curt Noll & Larry Bassel.
-All Rights Reserved.  Permission for personal, educational or non-profit use is
-granted provided this this copyright and notice are included in its entirety
-and remains unaltered.  All other uses must receive prior permission in writing
-from both Landon Curt Noll and Larry Bassel.
 
-Instructions for use: Run make to compile entries (it is possible that
+Look at the README.md file for the given winner for information
-on System V or non-unix systems the makefile needs to be changed). The
+on how to compile the winner and how to run the winning program.
-ansi.mk may need to be changed if your ANSI C compiler is not gcc.
+Look at the winning source and try to figure how it does what it does!
-
+You may then wish to look at the Author's comments for even more details.
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-(minor) spoilers.
 
 This year, the Grand Prize won a standing ovation at USENIX.
 
@@ -31,3 +23,11 @@ some of the contest entries were appreciated.
 Rules and results were posted to comp.lang.c, comp.sources.unix, and
 alt.sources.  They have been made available on a wide number of Usenet
 archive sites such as uunet.
+
+=-=
+
+Copyright (c) 1990, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1991/README

@@ -1,18 +1,14 @@
 1991 marked the "The Eighth International Obfuscated C Code Contest"
 
-Copyright (c) 1991, Landon Curt Noll & Larry Bassel.
+
-All Rights Reserved.  Permission for personal, educational or non-profit use is
+Look at the README.md file for the given winner for information
-granted provided this this copyright and notice are included in its entirety
+on how to compile the winner and how to run the winning program.
-and remains unaltered.  All other uses must receive prior permission in writing
+Look at the winning source and try to figure how it does what it does!
-from both Landon Curt Noll and Larry Bassel.
+You may then wish to look at the Author's comments for even more details.
 
 Instructions for use: Run make to compile entries.  It is possible that
 on BSD or non-unix systems the makefile needs to be changed.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-(minor) spoilers.
-
 This year, we did not single out an entry that was better than all of
 the rest.  We selected 3 entries that were, in our opinion, went beyond
 all of the other entries this year:
@@ -86,3 +82,11 @@ Credits:
 We would like to thank Barbara Frezza for her role as official chef
 of the contest.  Landon Noll appreciated the opportunity to serve
 as assistant pizza chef.  Larry Bassel was official taste tester. Yummo!
+
+=-=
+
+Copyright (c) 1991, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1992/README

@@ -1,19 +1,14 @@
 1992 marked the "The Ninth International Obfuscated C Code Contest"
 
-Copyright (c) 1992, Landon Curt Noll & Larry Bassel.
+
-All Rights Reserved.  Permission for personal, educational or non-profit use is
+Look at the README.md file for the given winner for information
-granted provided this this copyright and notice are included in its entirety
+on how to compile the winner and how to run the winning program.
-and remains unaltered.  All other uses must receive prior permission in writing
+Look at the winning source and try to figure how it does what it does!
-from both Landon Curt Noll and Larry Bassel.
+You may then wish to look at the Author's comments for even more details.
 
 Use make to compile entries.  It is possible that on BSD or non-unix
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitters.
-
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
 #define).  A number of compilers had problems optimizing certain
@@ -86,3 +81,11 @@ Credits:
 We would like to thank Barbara Frezza for her role as official chef of
 the contest.  Landon Noll and Larry Bassel appreciated the opportunity
 to serve as official taste testers. Yummo!
+
+=-=
+
+Copyright (c) 1992, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1993/README

@@ -1,19 +1,14 @@
 1993 marked the "The Tenth International Obfuscated C Code Contest"
 
-Copyright (c) 1993, Landon Curt Noll & Larry Bassel.
+
-All Rights Reserved.  Permission for personal, educational or non-profit use is
+Look at the README.md file for the given winner for information
-granted provided this this copyright and notice are included in its entirety
+on how to compile the winner and how to run the winning program.
-and remains unaltered.  All other uses must receive prior permission in writing
+Look at the winning source and try to figure how it does what it does!
-from both Landon Curt Noll and Larry Bassel.
+You may then wish to look at the Author's comments for even more details.
 
 Use make to compile entries.  It is possible that on BSD or non-unix
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitters.
-
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
 #define).
@@ -57,3 +52,11 @@ Credits:
 We would like to thank Barbara Frezza for her role as official chef
 of the contest.  Landon Noll and Larry Bassel appreciated the opportunity
 to serve as official taste testers.  And as usual, the food was excellent.
+
+=-=
+
+Copyright (c) 1993, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1994/README

@@ -1,20 +1,14 @@
 1994 marked the "The Eleventh International Obfuscated C Code Contest"
 
-Copyright (c) 1994, Landon Curt Noll & Larry Bassel.
-All Rights Reserved.  Permission for personal, educational or non-profit use is
-granted provided this this copyright and notice are included in its entirety
-and remains unaltered.  All other uses must receive prior permission in writing
-from both Landon Curt Noll and Larry Bassel.
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
 
 Use make to compile entries.  It is possible that on BSD or non-unix
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitters.
-
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
 #define).
@@ -136,3 +130,11 @@ Pasta: Linguine with wild mushrooms and Reggiano Parmesan
 Seafood: Salmon in cream sauce or lobster claws
 Vegetable: Zucchini
 Dessert: Homemade chocolate/pecan brownies, fruit
+
+=-=
+
+Copyright (c) 1994, Landon Curt Noll & Larry Bassel.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from both Landon Curt Noll and Larry Bassel.

1995/README

@@ -1,11 +1,10 @@
 1995 marked the "The Twelfth International Obfuscated C Code Contest"
 
-Copyright (c) 1996, Landon Curt Noll, Larry Bassel & Sriram Srinivasan.
-All Rights Reserved.  Permission for personal, educational or non-profit use is
-granted provided this this copyright and notice are included in its entirety
-and remains unaltered.  All other uses must receive prior permission in writing
-from Landon Curt Noll, Larry Bassel and Sriram Srinivasan.
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
 
 The IOCCC has an official home page:
 
@@ -17,11 +16,6 @@ announcements and much more.
 Use make to compile entries.  It is possible that on BSD or non-unix
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitters.
-
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
 #define).
@@ -140,3 +134,10 @@ Main Course: Cracked dungeness crab with lemon mayonnaise, broccoli,
 	mixture of white and brown rice
 Dessert: Key lime pie
 
+=-=
+
+Copyright (c) 1996, Landon Curt Noll, Larry Bassel & Sriram Srinivasan.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from Landon Curt Noll, Larry Bassel and Sriram Srinivasan.

1996/README

@@ -1,15 +1,14 @@
 1996 marked the "The Thirteenth International Obfuscated C Code Contest"
 
-Copyright (c) 1997, Landon Curt Noll & Sriram Srinivasan.
-All Rights Reserved.  Permission for personal, educational or non-profit use is
-granted provided this this copyright and notice are included in its entirety
-and remains unaltered.  All other uses must receive prior permission in writing
-from Landon Curt Noll and Sriram Srinivasan.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has an official home page:
 
 	http://www.ioccc.org
@@ -20,11 +19,6 @@ announcements and much more.
 Use make to compile entries.  It is possible that on BSD or non-unix
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitters.
-
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
 #define).
@@ -95,3 +89,11 @@ us a line.  We enjoy seeing who, where and how the contest is used.
 
 If you have problems with any of the entries, AND YOU HAVE A FIX, please
 email the fix (patch file or the entire changed file) to the above address.
+
+=-=
+
+Copyright (c) 1997, Landon Curt Noll & Sriram Srinivasan.
+All Rights Reserved.  Permission for personal, educational or non-profit use is
+granted provided this this copyright and notice are included in its entirety
+and remains unaltered.  All other uses must receive prior permission in writing
+from Landon Curt Noll and Sriram Srinivasan.

1998/README

@@ -1,16 +1,14 @@
 1998 marked the "The Fourteenth International Obfuscated C Code Contest"
 
-Copyright (c) Landon Curt Noll, Jeremy Horn, Peter Seebach
-and Leonid A. Broukhis, 1999.
-All Rights Reserved.  Permission for personal, educational or non-profit
-use is granted provided this this copyright and notice are included in its
-entirety and remains unaltered.  All other uses must receive prior permission
-from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has its own domain.  The IOCCC has an official home page is now:
 
 	http://www.ioccc.org
@@ -18,11 +16,6 @@ The IOCCC has its own domain.  The IOCCC has an official home page is now:
 Use make to compile entries.  It is possible that on BSD or non-unix
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitters.
-
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
 #define).
@@ -131,3 +124,12 @@ The next IOCCC is planned to start towards the end of 1999.  Watch:
 	http://www.ioccc.org
 
 for news of the next contest.
+
+=-=
+
+Copyright (c) Landon Curt Noll, Jeremy Horn, Peter Seebach
+and Leonid A. Broukhis, 1999.
+All Rights Reserved.  Permission for personal, educational or non-profit
+use is granted provided this this copyright and notice are included in its
+entirety and remains unaltered.  All other uses must receive prior permission
+from the contest judges.

2000/README

@@ -1,23 +1,16 @@
 2000 marked the "The Fifteenth International Obfuscated C Code Contest"
 
-Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach
-and Leonid A. Broukhis, 2000.
-All Rights Reserved.  Permission for personal, educational or non-profit
-use is granted provided this copyright and notice are included in its
-entirety and remains unaltered.  All other uses must receive prior permission
-from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
-Use make to compile entries.  It is possible that on non-Un*x / non-Linux
+Look at the README.md file for the given winner for information
-systems the makefile needs to be changed.  See the Makefile for details.
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
 
-Look at the source and try to figure out what the programs do, and run
+Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
-them with various inputs.  If you want to, look at the hints files for
+systems the makefile needs to be changed.  See the Makefile for details.
-spoilers - this year we included most of the information included
-by the submitters.
 
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
@@ -118,3 +111,11 @@ p.s. The has been mentioned in an Amici Curiae for the DeCSS case.  See:
 
 and seach on the word ioccc (twice).
 
+=-=
+
+Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach
+and Leonid A. Broukhis, 2000.
+All Rights Reserved.  Permission for personal, educational or non-profit
+use is granted provided this copyright and notice are included in its
+entirety and remains unaltered.  All other uses must receive prior permission
+from the contest judges.

2001/README

@@ -1,29 +1,22 @@
 2001 marked the "The Sixteenth International Obfuscated C Code Contest"
 
-Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach
-and Leonid A. Broukhis, 2001-2002.
-All Rights Reserved.  Permission for personal, educational or non-profit
-use is granted provided this copyright and notice are included in its
-entirety and remains unaltered.  All other uses must receive prior permission
-from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has a web site and now has a number of international mirrors.  The
 primary site can be found at,
 
      http://www.ioccc.org
 
-Use make to compile entries.  It is possible that on non-Un*x / non-Linux
+Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitters.
-
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
 #define).
@@ -95,3 +88,10 @@ Watch:
 for news of the next contest.
 
 =-=
+
+Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach
+and Leonid A. Broukhis, 2001-2002.
+All Rights Reserved.  Permission for personal, educational or non-profit
+use is granted provided this copyright and notice are included in its
+entirety and remains unaltered.  All other uses must receive prior permission
+from the contest judges.

2004/README

@@ -1,28 +1,22 @@
 2004 marked the "The Seventeenth International Obfuscated C Code Contest"
 
-Copyright (C) 2001-2004, Landon Curt Noll, Simon Cooper, Peter Seebach
-and Leonid A. Broukhis. All Rights Reserved. Permission for personal,
-educational or non-profit use is granted provided this copyright and
-notice are included in its entirety and remains unaltered.  All other
-uses must receive prior permission from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has a web site and now has a number of international mirrors.
 The primary site can be found at,
 
      http://www.ioccc.org/
 
-Use make to compile entries.  It is possible that on non-Un*x / non-Linux
+Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitters.
-
 Read over the makefile for compile/build issues.  Your system may
 require certain changes (add or remove a library, add or remove a
 #define).
@@ -84,3 +78,11 @@ Watch:
 	http://www.ioccc.org/
 
 for news of the next contest.
+
+=-=
+
+Copyright (C) 2001-2004, Landon Curt Noll, Simon Cooper, Peter Seebach
+and Leonid A. Broukhis. All Rights Reserved. Permission for personal,
+educational or non-profit use is granted provided this copyright and
+notice are included in its entirety and remains unaltered.  All other
+uses must receive prior permission from the contest judges.

2005/README.md

@@ -1,28 +1,25 @@
 2005 marked the "The Eighteenth International Obfuscated C Code Contest"
 ========================================================================
 
-Copyright (C) 2005, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has a web site and now has a number of international mirrors.
 The primary site can be found at,
 
 >	<http://www.ioccc.org/>
 
-Use make to compile entries.  It is possible that on `non-Un*x` / non-Linux
+Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
+This year we included most of the information included by the submitters
-them with various inputs.  If you want to, look at the hints files for
+in the README.md files.
-spoilers - this year we included most of the information included
-by the submitters.
 
 Read over the makefile for compile/build issues.  Your system may require
 certain changes (add or remove a library, add or remove a #define).
@@ -108,3 +105,10 @@ For news of the next contest watch:
 
 >	<http://www.ioccc.org/>
 
+=-=
+
+Copyright (C) 2005, Landon Curt Noll, Simon Cooper, and Leonid A.
+Broukhis. All Rights Reserved. Permission for personal, educational
+or non-profit use is granted provided this copyright and notice are
+included in its entirety and remains unaltered.  All other uses
+must receive prior permission from the contest judges.

2006/README.md

@@ -1,28 +1,25 @@
 2006 marked the "The Nineteenth International Obfuscated C Code Contest"
 ========================================================================
 
-Copyright (C) 2006, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has a web site and now has a number of international mirrors.
 The primary site can be found at,
 
 >	<http://www.ioccc.org/>
 
-Use make to compile entries.  It is possible that on non-Un*x / non-Linux
+Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
+This year we included most of the information included by the submitters
-them with various inputs.  If you want to, look at the hints files for
+in the README.md files.
-spoilers - this year we included most of the information included
-by the submitters.
 
 Read over the makefile for compile/build issues.  Your system may require
 certain changes (add or remove a library, add or remove a #define).
@@ -79,3 +76,10 @@ For news of the next contest watch:
 
 >	<http://www.ioccc.org/>
 
+=-=
+
+Copyright (C) 2006, Landon Curt Noll, Simon Cooper, and Leonid A.
+Broukhis. All Rights Reserved. Permission for personal, educational
+or non-profit use is granted provided this copyright and notice are
+included in its entirety and remains unaltered.  All other uses
+must receive prior permission from the contest judges.

2011/README.md

@@ -1,28 +1,25 @@
 2011 marked the "The Twentieth International Obfuscated C Code Contest"
 ========================================================================
 
-Copyright (C) 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has a web site and now has a number of international mirrors.
 The primary site can be found at,
 
 >	<http://www.ioccc.org/>
 
-Use make to compile entries.  It is possible that on non-Un*x / non-Linux
+Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
+This year we included most of the information included by the submitters
-them with various inputs.  If you want to, look at the hints files for
+in the README.md files.
-spoilers - this year we included most of the information included
-by the submitters.
 
 Read over the makefile for compile/build issues.  Your system may require
 certain changes (add or remove a library, add or remove a #define).
@@ -77,3 +74,10 @@ For news of the next contest watch:
 
 >	<http://www.ioccc.org/>
 
+=-=
+
+Copyright (C) 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
+Broukhis. All Rights Reserved. Permission for personal, educational
+or non-profit use is granted provided this copyright and notice are
+included in its entirety and remains unaltered.  All other uses
+must receive prior permission from the contest judges.

2012/README.html

@@ -1,135 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-  <meta name="GENERATOR" content="mkd2html 2.1.5a DL=DISCOUNT">
-  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
-  <link rel="stylesheet"
-        type="text/css"
-        href="hint.css">
-  <title>README</title>
-</head>
-<body>
-<h1>2012 marked the &ldquo;The Twenty First International Obfuscated C Code Contest&rdquo;</h1>
-
-<p>Copyright &copy; 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.</p>
-
-<h2>Standard IOCCC stuff</h2>
-
-<p>The IOCCC has a web site and now has a number of international mirrors.
-The primary site can be found at <b>www.ioccc.org</b>.
-
-<p>Use make to compile entries.  It is possible that on non-Un*x / non-Linux
-systems the makefile needs to be changed.  See the Makefile for details.</p>
-
-<p>Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitter.</p>
-
-<p>Read over the makefile for compile/build issues.  Your system may require
-certain changes (add or remove a library, add or remove a #define).</p>
-
-<p>Some ANSI C compilers are not quite as good as they should be.  If
-yours is lacking, you may need to compile using gcc instead of your
-local compiler.</p>
-
-<h2>Remarks on some of the entries</h2>
-
-<p>We believe you will be impressed with this year&rsquo;s winners.  We had
-a very difficult time picking a single best from among the other winners
-because the overall quality of the winners were so high.</p>
-
-<p>This year we selected the top 4 entries for particularly high honors:</p>
-
-<ul>
-<li><p>Gold award - Balanced use of obfuscation</p>
-
-<p>A very extremely subtle and twisted piece of source code!
-Even if you start with the zeitak_deobfucate.c source,
-you will still have a very challenging time to understand it!</p></li>
-<li><p>Silver award - Most elementary use of C</p>
-
-<p>A fun program that could also have won &ldquo;Best abuse of
-Ghostscript&rdquo; because it managed to create some PDF files
-that Ghostscript could not read.</p></li>
-<li><p>Bronze award - Best use of cocoa</p>
-
-<p>A picture within a picture is worth more than a
-thousand (4 byte) words. :-)</p></li>
-<li><p>Honorable mention - Most complex ASCII fluid</p>
-
-<p>When you see this program in action, you too will
-very likely say <a href="http://bit.ly/R6ALpK">wow</a> as we did!</p></li>
-</ul>
-
-
-<p>But don&rsquo;t ignore the other winners!  There are games, utilities,
-eye candy, calculators and graphical tools to explore.</p>
-
-<p>This year, Yusuke Endoh won with two entries, one of which (endoh1)
-won the special Honorable mention award.  Eight of the winning entries
-were from people who won in previous years.</p>
-
-<p>This year we had a number of winners from Asia.  We saw our second
-winner from China and first from Korea.  We are pleased to see
-outstanding entries from areas of the world that have not been
-active in past contests.  Will we see an upswing of entries
-from South America, Africa and Antarctica next year? :-)</p>
-
-<p>Please note that judging is done completely anonymously.  Please
-do NOT reveal your identity in your source code.  In the future we
-may disqualify entries that reveal the identity of the submitter!</p>
-
-<p>There were some outstanding entries that did not win.  Unfortunately
-some very good entries lost because they:</p>
-
-<ul>
-<li><p>would take years to execute</p></li>
-<li><p>were way way oversize and didn&rsquo;t even attempt to justify their
-excess by a clever abuse of the rules</p></li>
-<li><p>obfuscate themselves by simply invoking a complex
-state machine</p></li>
-<li><p>depend on a single obfuscation trick</p></li>
-<li><p>could only be run on a particular vendor&rsquo;s platform</p></li>
-<li><p>were very similar to previous winners</p></li>
-<li><p>were based on an overused theme such as yet another
-fractal display program</p></li>
-<li><p>didn&rsquo;t work as documented</p></li>
-</ul>
-
-
-<p>We hope the authors of some of those entries will fix and re-submit
-them for the next IOCCC.</p>
-
-<p>There is a risk in submitting an entry that is similar to a well
-used theme by previous winners.  Previous winners set a very high
-bar.  A new winner must not only compete against other submissions
-form the current year, they must also excel over similar winners
-in some particularly impressive way.</p>
-
-<h2>Final Comments</h2>
-
-<p>Please feel free to send us comments and suggestions about the
-competition, this README or anything else that you would like to see in
-future contests.</p>
-
-<p>If you use, distribute or publish these entries in some way, please drop
-us a line.  We enjoy seeing who, where and how the contest is used.</p>
-
-<p>If you have problems with any of the entries, AND YOU HAVE A FIX, please
-send us the fix (patch file or the entire changed file).</p>
-
-<TABLE><TR>
-<TD><a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/88x31.png" /></a></TD>
-<TD><P>&copy; Copyright 1984-2012, 
-<A HREF="/judges.html">Leo Broukhis, Simon Cooper, Landon Curt Noll</A>
-- All rights reserved<BR>
-This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.</P></TD>
-<TD>&nbsp;<!--<a href="http://validator.w3.org/check?uri=referer"><img src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01 Transitional" height="31" width="88"></a>--></TD>
-</TR></TABLE>
-</body>
-</html>

2012/README.md

@@ -1,16 +1,15 @@
 2012 marked the "The Twenty First International Obfuscated C Code Contest"
 ========================================================================
 
-Copyright (C) 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has a web site and now has a number of international mirrors.
 The primary site can be found at,
 
@@ -19,11 +18,6 @@ The primary site can be found at,
 Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitter.
-
 Read over the makefile for compile/build issues.  Your system may require
 certain changes (add or remove a library, add or remove a #define).
 
@@ -132,12 +126,10 @@ For news of the next contest watch:
 
 >	<http://www.ioccc.org/>
 
+=-=
 
---------------------------------------------------------------------------------
+Copyright (C) 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
-<!--
+Broukhis. All Rights Reserved. Permission for personal, educational
-(c) Copyright 1984-2012, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved
+or non-profit use is granted provided this copyright and notice are
-This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc].
+included in its entirety and remains unaltered.  All other uses
-
+must receive prior permission from the contest judges.
-[judges]: http://www.ioccc.org/judges.html
-[cc]: http://creativecommons.org/licenses/by-sa/3.0/
--->

2013/README.html

@@ -1,121 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-  <meta name="GENERATOR" content="mkd2html 2.1.5a DL=DISCOUNT">
-  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
-  <link rel="stylesheet"
-        type="text/css"
-        href="hint.css">
-  <title>README</title>
-</head>
-<body>
-<h1>2013 marked the &ldquo;The Twenty Second International Obfuscated C Code Contest&rdquo;</h1>
-
-<p>Copyright &copy; 2013, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.</p>
-
-<h2>Standard IOCCC stuff</h2>
-
-<p>The IOCCC has a web site and now has a number of international mirrors.
-The primary site can be found at <b>www.ioccc.org</b>.
-
-<p>Use make to compile entries.  It is possible that on non-Un*x / non-Linux
-systems the makefile needs to be changed.  See the Makefile for details.</p>
-
-<p>Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitter.</p>
-
-<p>Read over the makefile for compile/build issues.  Your system may require
-certain changes (add or remove a library, add or remove a #define).</p>
-
-<p>Some ANSI C compilers are not quite as good as they should be.  If
-yours is lacking, you may need to compile using gcc instead of your
-local compiler.</p>
-
-<h2>Remarks on some of the entries</h2>
-
-<p>We believe you will again be impressed with this year&rsquo;s winners.</p>
-
-<p>This year, several 8 people won 9 people won 15 awards.  For the
-first time in the history of the contest, one person, Yusuke Endoh,
-won 4 times while Adrian Cable won 3 times!  It is also worth noting
-that Chris Mills previous win was in 1993.  Welcome back Chris!</p>
-
-<p>We, the judges, were very surprised by this as many of the multiple
-winners submitted very different styles of entries.</p>
-
-<p>This year was the first time the IOCCC size tool was used.  Entries
-had to print a value 2053 or less when the -i flag was used.</p>
-
-<p>Several people discovered an undocumented feature in that
-certain comments such as:</p>
-
-<pre><code>///*
-</code></pre>
-
-<p>or:</p>
-
-<pre><code>*\
-/
-</code></pre>
-
-<p>were not correctly parsed by the tool.  The guidelines stated:</p>
-
-<pre><code>In cases where the above summary and the algorithm implemented by
-the IOCCC size tool source code conflict, the algorithm implemented
-by the IOCCC size tool source code is preferred by the judges.
-</code></pre>
-
-<p>so this abuse was allowed (and encouraged).  The judges hope that
-the IOCCC size tool author will patch the tool to block this kind
-of size abuse in future contests.</p>
-
-<p>There were some outstanding entries that did not win.  Unfortunately
-some very good entries lost because they:</p>
-
-<ul>
-<li><p>were way way oversize and didn&rsquo;t even attempt to justify their
-excess by a clever abuse of the rules</p></li>
-<li><p>depend on a single obfuscation trick</p></li>
-<li><p>could only be run on a particular vendor&rsquo;s platform</p></li>
-<li><p>were very similar to previous winners</p></li>
-<li><p>didn&rsquo;t work as documented</p></li>
-</ul>
-
-
-<p>We hope the authors of some of those entries will fix and re-submit
-them for the next IOCCC.</p>
-
-<p>There is a risk in submitting an entry that is similar to a well
-used theme by previous winners.  Previous winners set a very high
-bar.  A new winner must not only compete against other submissions
-from the current year, they must also excel over similar winners
-in some particularly impressive way.</p>
-
-<h2>Final Comments</h2>
-
-<p>Please feel free to send us comments and suggestions about the
-competition, this README or anything else that you would like to see in
-future contests.</p>
-
-<p>If you use, distribute or publish these entries in some way, please drop
-us a line.  We enjoy seeing who, where and how the contest is used.</p>
-
-<p>If you have problems with any of the entries, AND YOU HAVE A FIX, please
-send us the fix (patch file or the entire changed file).</p>
-
-<TABLE><TR>
-<TD><a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/88x31.png" /></a></TD>
-<TD><P>&copy; Copyright 1984-2013, 
-<A HREF="/judges.html">Leo Broukhis, Simon Cooper, Landon Curt Noll</A>
-- All rights reserved<BR>
-This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.</P></TD>
-<TD>&nbsp;<!--<a href="http://validator.w3.org/check?uri=referer"><img src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01 Transitional" height="31" width="88"></a>--></TD>
-</TR></TABLE>
-</body>
-</html>

2013/README.md

@@ -1,16 +1,15 @@
 2013 marked the "The Twenty Second International Obfuscated C Code Contest"
 ===========================================================================
 
-Copyright (C) 2013, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The IOCCC has a web site and now has a number of international mirrors.
 The primary site can be found at,
 
@@ -19,11 +18,6 @@ The primary site can be found at,
 Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitter.
-
 Read over the makefile for compile/build issues.  Your system may require
 certain changes (add or remove a library, add or remove a #define).
 
@@ -112,12 +106,10 @@ For news of the next contest watch:
 
 >	<http://www.ioccc.org/>
 
+=-=
 
---------------------------------------------------------------------------------
+Copyright (C) 2013, Landon Curt Noll, Simon Cooper, and Leonid A.
-<!--
+Broukhis. All Rights Reserved. Permission for personal, educational
-(c) Copyright 1984-2013, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved
+or non-profit use is granted provided this copyright and notice are
-This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc].
+included in its entirety and remains unaltered.  All other uses
-
+must receive prior permission from the contest judges.
-[judges]: http://www.ioccc.org/judges.html
-[cc]: http://creativecommons.org/licenses/by-sa/3.0/
--->

2019/README.html

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-  <meta name="GENERATOR" content="mkd2html 2.2.0">
-  <meta http-equiv="Content-Type"
-        content="text/html; charset=utf-8">  <link rel="stylesheet"
-        type="text/css"
-        href="hint.css">
-  <title>README</title>
-</head>
-<body>
-<h1>2016 marked the &ldquo;The Twenty Sixth International Obfuscated C Code Contest&rdquo;</h1>
-
-<p>Copyright &copy; 2019, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.</p>
-
-<h2>Standard IOCCC stuff</h2>
-
-The primary site can be found at <b>www.ioccc.org</b>.
-
-<p>Use make to compile entries.  It is possible that on non-Un*x / non-Linux
-systems the makefile needs to be changed.  See the Makefile for details.</p>
-
-<p>Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitter.</p>
-
-<p>Read over the makefile for compile/build issues.  Your system may require
-certain changes (add or remove a library, add or remove a #define).</p>
-
-<p>Some C compilers are not quite as good as they should be.  If yours is
-lacking, you may need to compile using clang or gcc instead of your local
-compiler.</p>
-
-<h2>Remarks on some of the winners</h2>
-
-<p>This year&rsquo;s winners are impressive!</p>
-
-<p>The &ldquo;Most in need of debugging&rdquo; (endoh) is very inventive in a way it produces its own text!</p>
-
-<p>The &ldquo;Most likely to be awarded&rdquo; (ciura) has an amazing vocabulary!</p>
-
-<p>There are again nods to winners of the years:</p>
-
-<pre><code>[1991/davidguy](http://ioccc.org/years.html#1991_davidguy)
-[2011/blakely](http://ioccc.org/years.html#2011_blakely)
-</code></pre>
-
-<p>These nods to not run afoul of the guideline:</p>
-
-<pre><code>We tend to dislike programs that:
-...
-are rather similar to previous winners
-</code></pre>
-
-<p>because the entry (dogon) appropriately pays homage to past winners
-without blatantly reusing their code.</p>
-
-<p>&hellip;We&rsquo;ll stop spouting spoilers now. Have fun exploring all the entries!</p>
-
-<h2>Remarks on some of submissions that did not win</h2>
-
-<p>Some entries tried to get around the size limit by submitting a data
-file that was really C code and then blindly including code in prog.c.</p>
-
-<p>Quite a few entries suffered from undefined behavior like accessing
-uninitialized locals and/or reading-writing below the stack.
-We advise running your entry through valgrind to make sure those mistakes
-are avoided.</p>
-
-<p>Using extra arguments to main, or arguments of wrong types as a quick and dirty
-way of declaring variables is now passé. Clang, for example, rejects them outright.</p>
-
-<p>We hope the authors of some of those entries will fix and re-submit
-them for the next IOCCC.</p>
-
-<p>Some entries seemed to have a good idea, but the implementation of
-the idea was limited in scope.</p>
-
-<h2>Final Comments</h2>
-
-<p>Please feel free to send us comments and suggestions about the
-competition, this README or anything else that you would like to see in
-future contests.</p>
-
-<p>If you use, distribute or publish these entries in some way, please drop
-us a line.  We enjoy seeing who, where and how the contest is used.</p>
-
-<p>If you have problems with any of the entries, AND YOU HAVE A FIX, please
-send us the fix (patch file or the entire changed file).</p>
-
-<TABLE><TR>
-<TD><a rel="license" href="https://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="/png/by-sa-3.0-88x31.png" /></a></TD>
-<TD><P>&copy; Copyright 1984-2019,
-<A HREF="/judges.html">Leo Broukhis, Simon Cooper, Landon Curt Noll</A>
-- All rights reserved<BR>
-This work is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.</P></TD>
-<TD>&nbsp;<!--<a href="https://validator.w3.org/check?uri=referer"><img src="https://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01 Transitional" height="31" width="88"></a>--></TD>
-</TR></TABLE>
-</body>
-</html>

2019/README.md

@@ -1,16 +1,15 @@
 2016 marked the "The Twenty Sixth International Obfuscated C Code Contest"
 ==========================================================================
 
-Copyright (C) 2019, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.
-
 
 Standard IOCCC stuff
 --------------------
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The primary IOCCC web site can be found at,
 
 >	<http://www.ioccc.org/>
@@ -18,11 +17,6 @@ The primary IOCCC web site can be found at,
 Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitter.
-
 Read over the makefile for compile/build issues.  Your system may require
 certain changes (add or remove a library, add or remove a #define).
 
@@ -99,11 +93,10 @@ For news of the next contest watch:
 
 >	<http://www.ioccc.org/>
 
---------------------------------------------------------------------------------
+=-=
-<!--
-(c) Copyright 1984-2019, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved
-This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc].
 
-[judges]: http://www.ioccc.org/judges.html
+Copyright (C) 2019, Landon Curt Noll, Simon Cooper, and Leonid A.
-[cc]: http://creativecommons.org/licenses/by-sa/3.0/
+Broukhis. All Rights Reserved. Permission for personal, educational
--->
+or non-profit use is granted provided this copyright and notice are
+included in its entirety and remains unaltered.  All other uses
+must receive prior permission from the contest judges.

2020/README.md

@@ -1,14 +1,13 @@
 ## 2020 marked the "The Twenty Seventh International Obfuscated C Code Contest"
 
-Copyright (C) 2020, Landon Curt Noll, Simon Cooper, and Leonid A.
-Broukhis. All Rights Reserved. Permission for personal, educational
-or non-profit use is granted provided this copyright and notice are
-included in its entirety and remains unaltered.  All other uses
-must receive prior permission from the contest judges.
-
 
 ## Standard IOCCC stuff
 
+Look at the README.md file for the given winner for information
+on how to compile the winner and how to run the winning program.
+Look at the winning source and try to figure how it does what it does!
+You may then wish to look at the Author's comments for even more details.
+
 The primary IOCCC web site can be found at,
 
 >	<http://www.ioccc.org/>
@@ -16,11 +15,6 @@ The primary IOCCC web site can be found at,
 Use make to compile entries.  It is possible that on non-Un\*x / non-Linux
 systems the makefile needs to be changed.  See the Makefile for details.
 
-Look at the source and try to figure out what the programs do, and run
-them with various inputs.  If you want to, look at the hints files for
-spoilers - this year we included most of the information included
-by the submitter.
-
 Read over the makefile for compile/build issues.  Your system may require
 certain changes (add or remove a library, add or remove a #define).
 
@@ -88,10 +82,10 @@ For news of the next contest watch:
 
 >	<http://www.ioccc.org/>
 
------------------------------------------------------------------------------------------------------
+=-=
-(c) Copyright 1984-2020, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved
-This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc].
 
-[judges]: http://www.ioccc.org/judges.html
+Copyright (C) 2020, Landon Curt Noll, Simon Cooper, and Leonid A.
-[cc]: http://creativecommons.org/licenses/by-sa/3.0/
+Broukhis. All Rights Reserved. Permission for personal, educational
------------------------------------------------------------------------------------------------------
+or non-profit use is granted provided this copyright and notice are
+included in its entirety and remains unaltered.  All other uses
+must receive prior permission from the contest judges.