After commit c744a1c7942276c644832ced5ffc18aa38768525, the
location tool now assigns the location_code "ZZ"
with the name "Unknown location".
For those `author/author_handle.json` whose
"location_code" and/or "location_name" was a JSON null,
they now use a "location_name" of "ZZ" and
a "location_name" of "Unknown location".
HELP: It would be nice if we could figure out the true location or at
least a well justified guess of authors whose location is now "ZZ".
We cannot simply use a guess based on the name. But perhaps
there are clues as to the current (or past) location of
such IOCCC winner authors.
Updated manifest as per recent file changes.
Updated winner `.winner.json` to reflect the manifest changes.
Added [bin/all_run.sh](bin/all_run.sh) tool to run a command over
all winning entries.
These tools had slight improvements in the help usage message:
* bin/gen-author.sh VERSION="1.3.1 2024-01-16"
* bin/gen-inventory.sh VERSION="1.0.1 2024-01-16"
* bin/pandoc_wrapper.sh VERSION="1.3.1 2024-01-16"
* bin/subst.default.sh VERSION="1.1.1 2024-01-16"
* bin/subst.winner-index.sh VERSION="1.1.1 2024-01-16"
The `bin/readme2index.sh` tool was improved so that
if the `index.html` file exists and the tool forms
the exact same content, then the file `index.html`
file is NOT touched.
* bin/readme2index.sh VERSION="1.1 2024-01-16"
We used the following command to generate `index.html` files
for all winning entries:
```sh
bin/all_run.sh -v 3 bin/readme2index.sh
```
NOTE: We have not (yet) built HTML files above the winner directory
level (e.g., no year level nor top level HTML), nor have be built
non-index HTML files for winners.
NOTE: By default we are running `pandoc(1)` with:
```
--fail-if-warnings=true
```
This means that any problems with markdown to HTML
generates an error. This is done to be sure that
the HTML conversion is clean.
We had to fix the following `README.md` files:
* `2000/rince/README.md`
The reference [^2] was never used. We made a guess that [^2] applies
to the same spot as [^1]. Perhaps there is a better spot where
[^2] applies?
NOTE: For every reference, there MUST be some place where that
reference is used.
* 2012/vik/README.md
The string "$...$" is assumed to be a TeX encoded string.
NOTE: Every "$..$" needs to be backslashed as in "\$..\$".
* 2018/burton1/README.md
The reference [2] was duplicated. We changed the
second [2] to [3].
NOTE: Every reference needs to have a unique number.
* 2020/carlini/README.md
The string "$...$" is assumed to be a TeX encoded string.
NOTE: Every "$..$" needs to be backslashed as in "\$..\$".
We also found 2 errors in the `author/author_handle.json` file set:
* author/Anonymous_2001.json
The `author/Anonymous_2001.json` file was missing.
* author/Jari_Arkko.json
The winner ID for `1989_jar.1` had a typo.
This is because it was decided quite some time ago that there is not
actually a need to escape the '/' in JSON strings and using our jparse
verifies that files with this form are valid JSON.
The mastodon handle that was listed is for his Greek/Greece one and not
the technical one. It seems for the IOCCC it would be better to have the
tech one.
Also added his GitHub handle.
The following characters are no longer encoded
and are represented as themselves:
- & is no longer encoded
- / is no longer encoded
- < is no longer encoded
- > is no longer encoded
- [\x80-\xff] is no longer encoded
The author ID JSON files under `/author` have
been updated accordingly.
Fixed author/author_handle.json situations where "location_code",
"location_name", and/or "deprecated_twitter_handle" was an empty
JSON string. In those cases the JSON null is used instead.
The `author/author_handle.json` file content was generated
by the commands:
```sh
cd tmp
rm -rf ../author
./gen_author_json.sh author_handle.txt author.csv author-wins.csv ../author
```
Also installed is `author/README.md` that describes the `author/`
directory tree and author_handle.json format.
Some tmp files were slightly modified before to help the
`gen_author_json.sh` tool.
NOTE: The `gen_author_json.sh` tool is under the `tmp/` directory
and **NOT** the `bin/` directory. Like the files under tmp/`
directory, the `gen_author_json.sh` tool will go away as the files
and tool are not needed.
The `author/author_handle.json` files will become authoritative,
replacing the `gen_author_json.sh` tool and files under tmp/`
directory. However we will keep them around for a while, at least
a git of time after issue #4 is resolved.
Landon Curt Noll