build index.html for all winners

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 commit is contained in:
Landon Curt Noll committed 2024-01-17 00:32:39 -08:00
1 parent 893cd915b6
commit c1466f5165
350 files changed
+95242 -4217

No files matched your search

+403 -13
View File
@@ -1,4 +1,6 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<!-- START: two lines up starts content from: inc/top.default.html -->
<!-- -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- !!! DO NOT MODIFY THIS FILE - This file is generated by a tool !!! -->
@@ -6,27 +8,415 @@
<!-- !!! DO NOT MODIFY THIS FILE - This file is generated by a tool !!! -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- -->
<!-- file: 2019/giles/index.html created by: fake.gen_index.sh version: 1.0.5 2023-10-31 -->
<html lang="en">
<!-- END: this line ends content from: inc/top.default.html -->
<!-- -->
<!-- This file was formed by the tool: bin/readme2index.sh version: 1.1 2024-01-16 -->
<!-- -->
<!-- START: this line starts content from: inc/head.default.html -->
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>2019 giles</title>
<meta name="description" content="IOCCC year: 2019 IOCCC winner: giles winner index page">
<meta name="keywords" content="IOCCC,2019,giles,winner index page">
<link rel="stylesheet" href="/temp-test-ioccc/ioccc.css">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
<title>2019/giles</title>
<meta name="description" content="2019 IOCCC winner giles">
<meta name="keywords" content="IOCCC, 2019, IOCCC 2019, IOCCC winner, giles">
</head>
<!-- END: this line ends content from: inc/head.default.html -->
<!-- START: this line starts content from: inc/body.default.html -->
<body>
<h1>2019 giles</h1>
<!-- END: this line ends content from: inc/body.default.html -->
<!-- START: this line starts content from: inc/header.default.html -->
<p>XXX - fake content until readme2index is working - XXX</p>
<div class="header">
<img src="/temp-test-ioccc/png/ioccc.png" alt="IOCCC image by Matt Zucker" width=300 height=110>
<h1>The International Obfuscated C Code Contest</h1>
<h2>2019/giles</h2>
</div>
<hr style="width:50%;text-align:left;margin-left:0">
<!-- END: this line ends content from: inc/header.default.html -->
<!-- START: this line starts content from: inc/topnav.first.html -->
<!-- Start Nu Html Checker -->
<p><a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2F2019%2Fgiles%2Findex.html">Nu Html check https://ioccc-src.github.io/temp-test-ioccc/2019/giles/index.html</a></p>
<!-- End Nu Html Checker -->
<div class="topnav">
<a class="Left Disabled" href="#">first entry</a>
<a class="Left" href="../index.html">&uarr; 2019 &uarr;</a>
<a class="Left" href="../diels-grabsch1/index.html">diels-grabsch1 &rarr;</a>
<a class="Right" href="#inventory">Inventory</a>
</div>
<!-- END: this line ends content from: inc/topnav.first.html -->
<!-- START: this line starts content from: inc/begin-row.default.html -->
<div class="row">
<!-- END: this line ends content from: inc/begin-row.default.html -->
<!-- START: this line starts content from: inc/begin-leftcolumn.default.html -->
<div class="leftcolumn">
<!-- END: this line ends content from: inc/begin-leftcolumn.default.html -->
<!-- START: this line starts content from: inc/sidenav.default.html -->
<div class="sidenav">
<a href="#content">Jump to contents</a>
</div>
<hr>
<div class="sidenav">
<a href="/temp-test-ioccc/index.html">IOCCC Home</a>
<a href="/temp-test-ioccc/years.html">Winning Entries</a>
<a href="/temp-test-ioccc/winners.html">People who have won</a>
</div>
<hr>
<div class="sidenav">
<a href="/temp-test-ioccc/news.html">IOCCC News</a>
<a href="/temp-test-ioccc/faq.html#submit">How to enter the IOCCC</a>
<a href="/temp-test-ioccc/faq.html">FAQ</a>
</div>
<hr>
<div class="sidenav">
<a href="/temp-test-ioccc/bugs.html">Bugs &amp; (mis)features</a>
<a href="/temp-test-ioccc/faq.html#fix_a_winner">Fixing IOCCC winners</a>
<a href="/temp-test-ioccc/faq.html#fix_web_site">Fixing the web site</a>
<a href="/temp-test-ioccc/faq.html#fix_author">Fixing winner info</a>
<a href="/temp-test-ioccc/thanks-for-help.html">Thanks for the help</a>
</div>
<hr>
<div class="sidenav">
<a href="/temp-test-ioccc/judges.html">The IOCCC Judges</a>
<a href="/temp-test-ioccc/contact.html">Contacting the IOCCC</a>
</div>
<hr>
<div class="sidenav">
<a href="#top">Jump to top</a>
</div>
<!-- END: this line ends content from: inc/sidenav.default.html -->
<!-- START: this line starts content from: inc/end-leftcolumn.default.html -->
</div>
<!-- END: this line ends content from: inc/end-leftcolumn.default.html -->
<!-- START: this line starts content from: inc/begin-rightcolumn.default.html -->
<div class="rightcolumn">
<!-- END: this line ends content from: inc/begin-rightcolumn.default.html -->
<!-- START: this line starts content from: inc/before-content.default.html -->
<a name="content"></a>
<!-- END: this line ends content from: inc/before-content.default.html -->
<!-- START: this line starts content generated by: bin/gen-author.sh -->
<p><a name="author"><strong>Author:</strong></a> <br><br>Name: <a
href="/temp-test-ioccc/winners.html#Edward_Giles">Edward Giles</a><br>
Location: <a href="/temp-test-ioccc/location.html#AU">AU</a></p>
<!-- END: next line ends content generated by: bin/gen-author.sh -->
<h2 id="to-build">To build:</h2>
<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span></span></code></pre></div>
<h2 id="to-use">To use:</h2>
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span> infile.wav outfile.wav</span></code></pre></div>
<h2 id="try">Try:</h2>
<div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="ex">play</span> MonodyVocals.wav</span>
<span id="cb3-2"><a href="#cb3-2" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span> MonodyVocals.wav</span>
<span id="cb3-3"><a href="#cb3-3" aria-hidden="true" tabindex="-1"></a><span class="ex">play</span> out.wav</span></code></pre></div>
<p>NOTE: <code>play</code> comes from SoX, the Swiss Army Knife of sound
processing programs. If you don’t have this installed, see <a
href="/faq.md#faq3_10">FAQ 3.10: How do I compile and use an IOCCC
winner that requires sound</a>.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>Do you need to pretend enjoying a more spacious living environment
than you actually are in, or the great outdoors with mountains and
canyons, when recording your outgoing voicemail message? Then don’t
waste another minute! Record yourself, send the audio file through this
entry, and let your callers be surprised.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="description">Description:</h3>
<p>This program takes a WAV audio file as input, and applies an
artificial reverberation effect to it. It works by feeding the audio
through a number of delay lines of various lengths, with various amounts
of feedback, to create a smooth echo that fades away over time. A number
of parameters of the effect can be altered, to change its sonic
characteristics.</p>
<p><a href="BlockDiagram.png">BlockDiagram.png</a> is a block-diagram of
the internal structure of the reverb algorithm, which is most likely
easier to understand than the source code.</p>
<p><a href="MonodyVocals.wav">MonodyVocals.wav</a> is for testing the
program: It is an extract of the unprocessed vocals from <a
href="https://www.youtube.com/watch?v=B7xai5u_tnk">Monody by TheFatRat,
featuring Laura Brehm</a>. The track was published under a free
license.</p>
<p>This program has also been successfully compiled on Windows, with
both the <a href="https://bellard.org/tcc/">Tiny C Compiler</a> and
Microsoft’s C/C++ compiler. However, the latter reports warnings about
loss of information when converting <code>float</code>s, and that
<code>void (*)()</code> and <code>void (*)(void)</code> are not the same
thing.</p>
<p>Interesting fact: The size of the program from
<code>./iocccsize -i</code> is 2019.</p>
<h4 id="how-to-use">How to use:</h4>
<div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span> input [output [size [dry [wet <span class="pp">[</span><span class="ss">damping</span><span class="pp">]</span>]]]]</span>
<span id="cb4-2"><a href="#cb4-2" aria-hidden="true" tabindex="-1"></a><span class="ex">prog.exe</span> input [output [size [dry [wet <span class="pp">[</span><span class="ss">damping</span><span class="pp">]</span>]]]]</span></code></pre></div>
<ul>
<li><code>input</code>: The path to the input file. Required.</li>
<li><code>output</code>: The path to the output file. Optional, defaults
to <code>out.wav</code>.</li>
<li><code>size</code>: The perceived size of the room, i.e. the
approximate amount of time taken for the echo to fade away. Optional,
default 1.6 seconds.</li>
<li><code>dry</code>: The amount of unprocessed signal (“dry” in audio
terminology) to add to the output. Optional, default 0.3 or 30%.</li>
<li><code>wet</code>: The amount of processed (“wet”) signal to add to
the output. Optional, default 0.5 or 50%.</li>
<li><code>damping</code>: The amount by which high frequencies are
damped out as the echo continues. This models the tendency for higher
frequencies to be absorbed more than lower ones. Increasing this value
causes the echo to be less “harsh” and more “muffled”. Optional, default
0.06 or 6%.</li>
</ul>
<p>The values <code>size</code>, <code>dry</code>, <code>wet</code>, and
<code>damping</code> can be specified either as decimal numbers
(e.g. 0.35) or as percentages (e.g. 35%).</p>
<p>The default settings are designed to make the effect obvious rather
than subtle, so it may be a good idea to adjust the ratio of “dry” to
“wet”, to give a more pleasant result:</p>
<div class="sourceCode" id="cb5"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span> in.wav out.wav 1.8 80% 15%</span></code></pre></div>
<p>The program only supports WAV files, and only mostly. Other audio
formats, such as MP3, are not supported because they are difficult to
decode, but there are free programs such as <code>ffmpeg</code> that can
perform the conversion. Some of the advanced features of the WAV file
format are also not supported, such as metadata, 3 or more channels, or
a bit depth other than 16 bits. Fortunately, WAV files that don’t use
these features are very common. The program validates the input file, so
passing it a file it can’t process will cause the program to print
<code>Bad input file</code> or
<code>Wave file must be 16 bits,1-2 channels.</code> depending on what
it thinks the problem is. If the output file cannot be opened, the
program will print <code>Can't open output file</code>.</p>
<h3 id="assumptions">Assumptions:</h3>
<ol type="1">
<li>The code is compiled using the C99 or C11 standard.</li>
<li>Values are stored in memory in little-endian order.</li>
<li><code>float</code> is a floating-point type of any size, such that
all zero bits represents the number zero.</li>
<li><code>int16_t</code> and <code>int32_t</code> are 2’s-complement,
<code>sizeof(int16_t) == 2</code> and
<code>sizeof(int32_t) == 4</code>.</li>
</ol>
<h3 id="obfuscations">Obfuscations</h3>
<p>The main obfuscation is that digital signal processing algorithms are
inherently opaque. They just consist of iterating through a list of
floating-point numbers and performing a series of arithmetic operations
on each value. Even if this entry were entirely cleaned of all other
obfuscation, it will appear to the average programmer to do the
following:</p>
<ul>
<li>Read and validate command-line arguments.</li>
<li>Read and validate the header portion of the input file, and print
some errors if that fails.</li>
<li>Write a modified form of that header into the output file.</li>
<li>Print the parameters read from the command-line arguments, in a
human-readable format.</li>
<li>Dynamically allocate some arrays of floating-point numbers, to be
used later, with lengths based on the <code>size</code> parameter.</li>
<li>Read 16-bit audio samples from the input file, converting them to
floating-point.</li>
<li>For each audio sample, do a weird combination of addition,
subtraction, and multiplication by constants, using the
previously-allocated arrays to store results between iterations. Write
the resulting audio samples to the output file, converting them back to
16-bit integers.</li>
<li>Close all of the file handles and free the memory.</li>
</ul>
<p>Note that no part of the above description of the code’s function had
anything to do with echoes in a room. The purpose of the code is
therefore hidden.</p>
<p>The source code, on cursory inspection, appears to be a jumbled
series of characters arranged into three arcs, representing sound waves.
The overall layout distracts people from the fact that it is source code
rather than only ASCII art, and the random appearance of the code
discourages people from trying to decipher it.</p>
<p><code>#define</code>s are used to abbreviate the code, which has a
side effect of making it very slightly harder to read.</p>
<ul>
<li><code>k</code> is just a general-purpose replacement for
<code>16</code>.</li>
<li><code>i</code> is the number of delay-lines to allocate and use
(currently <code>24</code>).</li>
<li><code>q</code> is an abbreviation for multiplying two elements of
<code>w[]</code> together.</li>
<li><code>u()</code> is used to display percentages with proper
rounding.</li>
<li><code>j()</code> imposes an upper limit on a floating-point value,
and then negates it. This operation is used eight times.</li>
<li><code>D()</code> abbreviates a call to <code>setvbuf</code>, used to
speed up file I/O.</li>
<li><code>l()</code> is used to clip audio samples to the acceptable
range, and convert them to 16-bit integers for output.</li>
<li><code>g()</code> handles errors.</li>
<li><code>C()</code> contains the bulk of the signal-processing code, as
well as a preprocessor obfuscation trick: If you were to read the body
of the macro out of context, it will appear to have multiple mismatched
square brackets, since <code>[</code> occurs more than <code>]</code>.
However, this macro is always invoked with arguments such as
<code>C(v],+10)</code> which contain an unmatched <code>]</code>
character. When the macro is used in this manner, the extra
<code>[</code>s in the macro’s body are matched with the <code>]</code>s
added through the first argument.</li>
</ul>
<p>Every variable name is one letter long. This allows the code to fit
into the IOCCC size limit, and it also makes the purpose of a given
variable much less clear. For example, it is not evident from the name
of the variable <code>t</code> that it contains pointers to the
delay-line arrays.</p>
<p>As many values as possible have been crammed into arrays.
<code>float w[]</code> contains:</p>
<ul>
<li>the input parameters (<code>w[0]</code> to <code>w[3]</code>)</li>
<li>various constants needed for the reverb algorithm (<code>w[4]</code>
to <code>w[9]</code>)</li>
<li>temporary storage of floating-point audio samples
(<code>w[10]</code> to <code>w[20]</code>)</li>
</ul>
<p><code>int32_t f[]</code> is even more multi-purpose. It contains:</p>
<ul>
<li>the header of the input file (<code>f[0]</code> to
<code>f[11]</code>)</li>
<li>the number of channels in the input file (<code>f[12]</code>)</li>
<li>the number of samples of output to generate
(<code>f[13]</code>)</li>
<li>an end-of-file flag (<code>f[14]</code>)</li>
<li>a variable that I forgot the exact purpose of
(<code>f[15]</code>)</li>
<li>indices into the circular buffers where audio samples should be
inserted (<code>f[16]</code> to <code>f[39]</code>)</li>
<li>indices where audio samples should be read out (<code>f[40]</code>
to <code>f[63]</code>)</li>
<li>lengths of the buffers (<code>f[64]</code> to
<code>f[87]</code>)</li>
</ul>
<p>All of the strings are concatenated together and “encrypted” by
breaking the string into 4-byte chunks (by casting it to an
<code>int32_t*</code>), and then XORing the sequence of
<code>int</code>s with a known numeric sequence. The “decryption” is not
done in-place, to avoid writing over the string constant.</p>
<p><code>int32_t *c</code> is a pointer that points into
<code>f[]</code>, except that it is often incremented or decremented
when it is accessed. In order to determine which indices of
<code>f[]</code> are being accessed through <code>c</code> at any given
point in the code, you would have to locate the places where
<code>c</code> is modified.</p>
<p>In order for this program to read and write WAV files, it needs to
parse the header. The necessary information, such as the sample rate and
channel count, is defined by the standard to be in somewhat arbitrary
locations within the file. Therefore, even if you know which indices of
<code>f[]</code> are being accessed, it takes extra effort to look up
the WAV file format and determine which field that corresponds to.</p>
<p>Some array accesses (which make up most of the program) have been
replaced with harder-to-interpret equivalents, for example:</p>
<ul>
<li><code>X[1]</code> -&gt; <code>1[X]</code></li>
<li><code>f[14]</code> -&gt; <code>10[f+4]</code></li>
<li><code>X[0]</code> -&gt; <code>*X</code></li>
</ul>
<p>Assignments return the assigned value, allowing them to be included
into later expressions:
<code>10[f]=f[13]&lt;&lt;2; f[1]=20+10[f]+k;</code> is replaced with
<code>f[1]=20+(10[f]=f[13]&lt;&lt;2)+k;</code>.</p>
<p>This technique is used in conjunction with the comma operator to
further obscure where the data ends up. For example:</p>
<ul>
<li><code>12[f]=4[++c]&gt;&gt;k;</code> was incorporated into
<code>w[0]*=6[f];</code> to yield
<code>w[0]*=(12[f]=4[++c]&gt;&gt;k,6[f]);</code></li>
<li><code>w[15]=w[k]=e[12[f]]; w[11]=w[10]=e[1];</code> becomes
<code>w[11]=(w[15]=w[k]=e[12[f]],w[10]=e[1]);</code></li>
</ul>
<p>A few other miscellaneous obfuscations have also been done:</p>
<ul>
<li><code>while(++f[15]&lt;12);</code> is used instead of
<code>f[15]=12;</code></li>
<li><code>for(s=14[f]=0;s&lt;f[13];s++)</code> is used instead of
<code>f[14]=0; for(s=0;s&lt;f[13];s++)</code></li>
<li>The line that contains <code>printf("Hello, world!");</code> is
mostly commented out.</li>
</ul>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0
License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights
Reserved. You are free to share and adapt this file under the terms of
this license:</p>
<pre><code>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</code></pre>
<p>For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/</p>
<!-- START: this line starts content generated by: bin/gen-inventory.sh -->
<h1 id="inventory-for-2019giles"><a name="inventory"></a>Inventory for
2019/giles</h1>
<h2 id="primary-files">Primary files</h2>
<ul>
<li><a href="index.html">index.html</a> - winner home page</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/giles/prog.c">prog.c</a>
- winning source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/giles/Makefile">Makefile</a>
- winner Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/giles/prog.orig.c">prog.orig.c</a>
- original source</li>
<li><a href="BlockDiagram.png">BlockDiagram.png</a> - reverb algorithm
block-diagram of internal structure</li>
<li><a href="MonodyVocals.wav">MonodyVocals.wav</a> - Monody by
TheFatRat featuring Laura Brehm</li>
<li><a href="2019_giles.tar.bz2">2019_giles.tar.bz2</a> - download
winning source</li>
</ul>
<h2 id="secondary-files">Secondary files</h2>
<ul>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/giles/.gitignore">.gitignore</a>
- list of files that should not be committed under git</li>
<li><a href=".path">.path</a> - directory path from top directory</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/giles/.winner.json">.winner.json</a>
- description of winner in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/giles/README.md">README.md</a>
- markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/gen-inventory.sh -->
<!-- START: this line starts content from: inc/after-content.default.html -->
<!-- END: this line ends content from: inc/after-content.default.html -->
<!-- START: this line starts content from: inc/end-rightcolumn.default.html -->
</div>
<!-- END: this line ends content from: inc/end-rightcolumn.default.html -->
<!-- START: this line starts content from: inc/end-row.default.html -->
</div>
<!-- END: this line ends content from: inc/end-row.default.html -->
<!-- START: this line starts content from: inc/footer.default.html -->
<div class="footer">
<hr>
<h2>Coda</h2>
<p><a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2F2019%2Fgiles%2Findex.html">Nu HTML check this web page</a></p>
<p><a href="#top">Jump to top</a> <a href="#content">Jump to Content</a> <a href="#inventory">Jump to Inventory</a></p>
</div>
<!-- END: this line ends content from: inc/footer.default.html -->
<!-- START: this line starts content from: inc/bottom.default.html -->
</body>
</html>
<!-- END: this line ends content from: inc/bottom.default.html -->