We reverse the workaround for UTF-8 character in 2001/ollinger/README.md
from 76d2e9d053 and put back the é
character in that file.
We did this because the test for reversing a similar workaround
for 2011/borsanyi/README.md worked with commit
43350972c9.
The commit 00ae59cd47 had a
mistake that introduces changes to Makefiles for 1996 thru 2020
that should not have been included.
This change reverses these intermediate changes until
the given year's Makefiles are ready.
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.
There are some places where this was not done: in data files that refer
to binaries (examples being 2001/herrmann1/{README.md,herrmann1.c} and
those related to 1990/theorem for Turing and Fibonacci respectively). In
comments in code it was changed to be capitalised though this is
potentially problematic in that maybe it was intentional by the authors.
The file `2001/ollinger/README.md` contained a single lower case
small letter e with a acute mark as defined by the UTF-8 character
for the 2 bytes: 0xc3 0xa9.
Replaced the RAW UTF-8 character: "LATIN SMALL LETTER E WITH ACUTE"
with the HTML "é". Not sure what the best way to handle this,
however.
This character crashed markdown tools such as _qlmarkdown_
AND it prevented GitHub from rendering the web site. GitHub
reported in "Build with Jekyll":
```
Conversion error: Jekyll::Converters::Markdown encountered an error while converting '2001/ollinger/README.md':
847
The source text contains invalid characters for the used encoding UTF-8
848
/usr/local/bundle/gems/kramdown-2.3.2/lib/kramdown/parser/base.rb:93:in `adapt_source': The source text contains invalid characters for the used encoding UTF-8 (RuntimeError)
849
from /usr/local/bundle/gems/kramdown-2.3.2/lib/kramdown/parser/kramdown.rb:90:in `parse'
850
from /usr/local/bundle/gems/kramdown-parser-gfm-1.1.0/lib/kramdown/parser/gfm.rb:56:in `parse'
851
from /usr/local/bundle/gems/kramdown-2.3.2/lib/kramdown/parser/base.rb:69:in `parse'
852
from /usr/local/bundle/gems/kramdown-2.3.2/lib/kramdown/document.rb:102:in `initialize'
853
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/converters/markdown/kramdown_parser.rb:42:in `new'
854
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/converters/markdown/kramdown_parser.rb:42:in `convert'
855
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/converters/markdown.rb:77:in `convert'
856
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/renderer.rb:101:in `block in convert'
857
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/renderer.rb:99:in `each'
858
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/renderer.rb:99:in `reduce'
859
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/renderer.rb:99:in `convert'
860
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/renderer.rb:83:in `render_document'
861
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/renderer.rb:62:in `run'
862
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/site.rb:479:in `render_regenerated'
863
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/site.rb:472:in `block in render_pages'
864
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/site.rb:471:in `each'
865
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/site.rb:471:in `render_pages'
866
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/site.rb:192:in `render'
867
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/site.rb:71:in `process'
868
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/command.rb:28:in `process_site'
869
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/commands/build.rb:65:in `build'
870
from /usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/commands/build.rb:36:in `process'
871
from /usr/local/bundle/gems/github-pages-228/bin/github-pages:70:in `block (3 levels) in <top (required)>'
872
from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
873
from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
874
from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
875
from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
876
from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
877
from /usr/local/bundle/gems/github-pages-228/bin/github-pages:6:in `<top (required)>'
878
from /usr/local/bundle/bin/github-pages:23:in `load'
879
from /usr/local/bundle/bin/github-pages:23:in `<main>'
```
Depending on if it was the beginning of the sentence the EMail would
become 'Email' or 'email'.
Some references of 'Email' were changed to 'email' as well as those were
not in the beginning of a sentence.
A few places some consistency of capitalised email address (made lower
case) were changed to match other places of the same pattern.
There is one exception:
$ find . -name '*.hint' -execdir git mv '{}' README.md \;
git statufatal: destination exists, source=1992/albert/albert.hint, destination=1992/albert/README.md
Looking at the two files they differ quite a bit so I've not changed it.
I'll bring this up on GitHub.
We we move 1988-2004 entries from all of a year's winning entries
in a single directory to each winner being in their own sub-directory
under the given year directory.
The 2020 winners are hinted it, but the source code is not there,
nor are the hints. Someone could look into the HTML and
see what was commented out, but that is not a problem because
WHO won is known and the name of their AWARD is known already.
Moreover a number of the winners have talked about what their
entirs do, so the commented out spoiler text is not a bit problem.
One will find HTML commented out with:
<!-- XXX remove when 2020 is ready
2020 links here
XXX remove when 2020 is ready -->
The "XXX remove when 2020 is ready" string is found at the
start and end comment blocks. Again, soneone could read
what was commented out, but that is OK since most of that
information is known or can be known. The following files
have such HTML comment blocks in them.
./winners.html
./years-spoiler.html
./years.html
In addition, ./all/summary.txt was modified to not
include the 2020 entries for the momemt.
The 2020 winner code AND write-ups are NOT part of this set.
p.s. The all/all.tar.bz2 does not contain the 2020 source code (yet?).
Landon Curt Noll