mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

force use of pandoc version >= 3.1.12.2

Browse Source 
The `bin/pandoc-wrapper.sh` tool will verify that the ssytem
has a recent enough version of `pandoc(1)`.

We explain why we insist on `pandoc(1)`. version >= 3.1.12.2
in comments where the $PANDOC_MIN_VERSION is set.

Added `--wrap=preserve` as a default argument to `pandoc(1)`.
While this change will impact every HTML file generated,
we believe this will improve the ability of someone to look
at the generated HTML and correlate with the original markdown.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.4.2 2024-03-17"
to "1.4.3 2024-03-18".

Performed `make www` to achieve all of the above and to generate
HTML using the new  `--wrap=preserve` `pandoc(1)` mode.
This commit is contained in:
Landon Curt Noll committed 2024-03-18 01:26:39 -07:00
1 parent 9eb7a54e9f
commit b0b212acb1
402 files changed
+37061 -55132
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2018/algmyr/index.html
+97 -134
View File
@@ -130,8 +130,8 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Anton_Algmyr">Anton Älgmyr</a><br>
Location: <a href="../../location.html#SE">SE</a> - <em>Kingdom of
Sweden</em> (<em>Sweden</em>) <br><br></li>
Location: <a href="../../location.html#SE">SE</a> - <em>Kingdom of Sweden</em> (<em>Sweden</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -141,15 +141,13 @@ Sweden</em> (<em>Sweden</em>) <br><br></li>
<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>
<p>To use this entry requires, in some invocations, a sound processing
program. This can be ALSA or SoX but we recommend the latter. See <a
href="../../faq.html#sox">FAQ 3.10 - How do I compile and use an IOCCC
entry that requires sound?</a>.</p>
<p>To use this entry requires, in some invocations, a sound processing program.
This can be ALSA or SoX but we recommend the latter. See <a href="../../faq.html#sox">FAQ 3.10 - How do I
compile and use an IOCCC entry that requires sound?</a>.</p>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
<pre><code>STATUS: INABIAF - please **DO NOT** fix</code></pre>
<p>For more detailed information see <a
href="../../bugs.html#2018_algmyr">2018 algmyr bugs</a>.</p>
<p>For more detailed information see <a href="../../bugs.html#2018_algmyr">2018 algmyr bugs</a>.</p>
<h2 id="to-use">To use:</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">./prog</span> <span class="op">&lt;</span> prog.c <span class="co"># Print garbage: might mess up your terminal</span></span>
<span id="cb3-2"><a href="#cb3-2" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span> <span class="op">&lt;</span>file1<span class="op">&gt;</span> <span class="op">&lt;</span>file2<span class="op">&gt;</span> <span class="op">&gt;</span> out.raw</span>
@@ -157,169 +155,134 @@ href="../../bugs.html#2018_algmyr">2018 algmyr bugs</a>.</p>
<h2 id="try">Try:</h2>
<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">./try.sh</span></span></code></pre></div>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>Be warned, this is not your garden variety text-to-speech program!
Earplugs are advised, or at least a handy and well-tested volume
knob.</p>
<p>Be warned, this is not your garden variety text-to-speech program! Earplugs are advised,
or at least a handy and well-tested volume knob.</p>
<p>Pixels are numbered, amplitudes are weighed, frequencies are divided,
and the message can be displayed in fiery letters, but don’t be
alarmed.</p>
<p>How does decoding of the waveform work? Can you encode an arbitrary
text in a sound sample?</p>
and the message can be displayed in fiery letters, but don’t be alarmed.</p>
<p>How does decoding of the waveform work? Can you encode an arbitrary text in a
sound sample?</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="what-is-this">What is this?</h3>
<p>To put it brief, this entry is akin to a sound based cat. It takes
characters as input and outputs them into frequency space as audio. The
entry also supports decoding the produced waveforms using the
<code>-d</code> flag. Usage instructions is output if run with the
<code>-h</code> flag, albeit not in an immediately legible format.</p>
<p>To put it brief, this entry is akin to a sound based cat. It takes characters as
input and outputs them into frequency space as audio. The entry also supports
decoding the produced waveforms using the <code>-d</code> flag. Usage instructions is
output if run with the <code>-h</code> flag, albeit not in an immediately legible format.</p>
<h3 id="details">Details</h3>
<p>In normal operation, the entry reads characters from one or more
sources. If the <code>-h</code> flag is given, usage instructions is
used as a source. Else if file paths are present as arguments those will
be used. Else <code>stdin</code> is used.</p>
<p>If a character is part of the supported subset of ASCII
<code>{10, 32-126}</code> then that character is output into frequency
space of an audio signal (44.1 kHz single precision float, endianness
should depend on system endianness) through <code>stdout</code>. Any
other character will be interpreted and outputted as a space.</p>
<p>Characters are printed using a (slightly modified) pixel font based
on <a href="https://github.com/hchargois/gohufont">gohufont</a>. Pixels
are drawn using crosses in frequency space, achieved by simultaneous up
<p>In normal operation, the entry reads characters from one or more sources. If the
<code>-h</code> flag is given, usage instructions is used as a source. Else if file paths
are present as arguments those will be used. Else <code>stdin</code> is used.</p>
<p>If a character is part of the supported subset of ASCII <code>{10, 32-126}</code> then that
character is output into frequency space of an audio signal (44.1 kHz single
precision float, endianness should depend on system endianness) through <code>stdout</code>.
Any other character will be interpreted and outputted as a space.</p>
<p>Characters are printed using a (slightly modified) pixel font based on
<a href="https://github.com/hchargois/gohufont">gohufont</a>.
Pixels are drawn using crosses in frequency space, achieved by simultaneous up
and down chirps.</p>
<p>Each input source is designated its own channel in the output (one
float per channel per time step in the output) so if you have a surround
sound system you could listen to a cacophony of chirpy characters.</p>
<p>Interestingly, with training you might actually be able to tell
characters just from hearing. But even without training you can easily
read along with the printed characters and have the sound make sense
with the look of the characters.</p>
<p>See image <a href="spoilers.png">spoiler.png</a> for an example
spectrogram.</p>
<p>Each input source is designated its own channel in the output (one float per
channel per time step in the output) so if you have a surround sound system you
could listen to a cacophony of chirpy characters.</p>
<p>Interestingly, with training you might actually be able to tell characters just
from hearing. But even without training you can easily read along with the
printed characters and have the sound make sense with the look of the
characters.</p>
<p>See image <a href="spoilers.png">spoiler.png</a> for an example spectrogram.</p>
<h3 id="limitations">Limitations</h3>
<p>There is no error checking done when opening files, so expect
segfaults if you provide the wrong path to a file.</p>
<p>This program is bound to misbehave if <code>int</code> is less than
32 bits.</p>
<p>Flags will only be interpreted correctly if they are the first
argument. Reading a file named <code>-d</code> or <code>-h</code> is
fully possible if it is not the first file provided, even though I am
not sure why you would want to do that.</p>
<p>Providing invalid/unexpected arguments to the decode flag will result
in odd behavior. Some erroneous arguments cause segfaults (negative
number of channels, channel id outside valid range). One argument in
particular causes an infinite loop printing whitespace.</p>
<p>There is no error checking done when opening files, so expect segfaults if you
provide the wrong path to a file.</p>
<p>This program is bound to misbehave if <code>int</code> is less than 32 bits.</p>
<p>Flags will only be interpreted correctly if they are the first argument. Reading
a file named <code>-d</code> or <code>-h</code> is fully possible if it is not the first file
provided, even though I am not sure why you would want to do that.</p>
<p>Providing invalid/unexpected arguments to the decode flag will result in odd
behavior. Some erroneous arguments cause segfaults (negative number of channels,
channel id outside valid range). One argument in particular causes an infinite
loop printing whitespace.</p>
<h3 id="obfuscation">Obfuscation:</h3>
<p>A lot of the obfuscations done came naturally from trying to appease
the size tool. To name some:</p>
<p>A lot of the obfuscations done came naturally from trying to appease the size
tool. To name some:</p>
<ul>
<li>One character names.</li>
<li>Merging of related (and not so related) arithmetic operations.</li>
<li>Short circuiting for flow control to replace some
<code>if</code>s.</li>
<li>Short circuiting for flow control to replace some <code>if</code>s.</li>
<li>Some <code>#defines</code>, sadly.</li>
</ul>
<p>On the intersection of size and obfuscation is the data encoding,
which was quite fun to design.</p>
<p>Some additional obfuscation was done to mathematical formulas.
Somewhat known expressions were transformed into equivalent but less
recognizable counterparts.</p>
<p>I have tried to avoid intentional red herrings in the code, although
fishy statements are plentiful.</p>
<p>On the intersection of size and obfuscation is the data encoding, which was
quite fun to design.</p>
<p>Some additional obfuscation was done to mathematical formulas. Somewhat known
expressions were transformed into equivalent but less recognizable counterparts.</p>
<p>I have tried to avoid intentional red herrings in the code, although fishy
statements are plentiful.</p>
<h3 id="data-encoding">Data encoding:</h3>
<p>The large string in the beginning of the source file contains font
data, encoded in base64 using characters in the range <code>' '</code>
to <code>'_'</code>. The space was chosen as zero because the data
contains a lot of zeroes, and quite helpfully the size tool ignores
whitespace even in strings. Without this fact the program would have
been too large and the decoding feature would have had to go.
Fortunately this hole in the size spec was readily available. :)</p>
<p>Characters in the font (5x8 pixels, 40 bits) are packed into 7 base64
digits (which was a pain to decode in minimal code).</p>
<p>The large string in the beginning of the source file contains font data, encoded
in base64 using characters in the range <code>' '</code> to <code>'_'</code>. The space was chosen as
zero because the data contains a lot of zeroes, and quite helpfully the size
tool ignores whitespace even in strings. Without this fact the program would
have been too large and the decoding feature would have had to go. Fortunately
this hole in the size spec was readily available. :)</p>
<p>Characters in the font (5x8 pixels, 40 bits) are packed into 7 base64 digits
(which was a pain to decode in minimal code).</p>
<h3 id="math">Math:</h3>
<p>Note that even though <code>float</code>s are used for the waveforms,
the standard math library is not used at all! Most arithmetic is done
purely on integers. The only major exception is generating a table of
sine values which are interpolated to give high resolution waveforms.
Can you see when the generation is triggered, and how it is done?</p>
<p>A critical issue encountered was that having abrupt starts and ends
of signals cause a lot of problems with spectral leakage which makes
spectrograms hard to read and audio painful to listen to. To reduce
spectral leakage a windowing function was used. Although the one used is
quite well known, it is not in a form that should be familiar to anyone.
What looks like a polynomial and quacks like a polynomial might not
actually be a polynomial, at least not deep inside.</p>
<p>Note that even though <code>float</code>s are used for the waveforms, the standard math
library is not used at all! Most arithmetic is done purely on integers. The only
major exception is generating a table of sine values which are interpolated to
give high resolution waveforms. Can you see when the generation is triggered,
and how it is done?</p>
<p>A critical issue encountered was that having abrupt starts and ends of signals
cause a lot of problems with spectral leakage which makes spectrograms hard to
read and audio painful to listen to. To reduce spectral leakage a windowing
function was used. Although the one used is quite well known, it is not in a
form that should be familiar to anyone. What looks like a polynomial and quacks
like a polynomial might not actually be a polynomial, at least not deep inside.</p>
<h3 id="printing-a-string">Printing a string:</h3>
<p>The program was written to deal exclusively with file descriptors, so
how would one go about printing a <code>char</code> array not from a
file descriptor without adding additional logic? Answer:
<code>ungetc(3)</code> into <code>stdin</code>, one <code>char</code> at
a time (to be standards compliant). This is used to print the usage
instructions.</p>
<p>The program was written to deal exclusively with file descriptors, so how would
one go about printing a <code>char</code> array not from a file descriptor without adding
additional logic? Answer: <code>ungetc(3)</code> into <code>stdin</code>, one <code>char</code> at a time (to be
standards compliant). This is used to print the usage instructions.</p>
<h3 id="compilation-warnings">Compilation warnings</h3>
<p>Compiling using</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="fu">gcc</span> <span class="at">-Wall</span> <span class="at">-Wextra</span> <span class="at">-pedantic</span></span></code></pre></div>
<p>gives only <code>-Wmisleading-indentation</code> which is sensible
considering the source code. While</p>
<p>gives only <code>-Wmisleading-indentation</code> which is sensible considering the source code. While</p>
<div class="sourceCode" id="cb6"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="fu">clang</span> <span class="at">-Wall</span> <span class="at">-Wextra</span> <span class="at">-pedantic</span></span></code></pre></div>
<p>is a bit more pessimistic and gives <code>-Wempty-body</code> (I like
loops without bodies), <code>-Wstring-plus-int</code> (since apparently
some people think string+<code>int</code> is a concatenation) and one of
the weirder warnings I have seen from me splitting a negative constant
with whitespace. Compiling using</p>
<p>is a bit more pessimistic and gives <code>-Wempty-body</code> (I like loops without
bodies), <code>-Wstring-plus-int</code> (since apparently some people think string+<code>int</code> is a
concatenation) and one of the weirder warnings I have seen from me splitting a
negative constant with whitespace. Compiling using</p>
<div class="sourceCode" id="cb7"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="fu">clang</span> <span class="at">-Wall</span> <span class="at">-Wextra</span> <span class="at">-pedantic</span> <span class="at">-Weverything</span></span></code></pre></div>
<p>produces a few page faults of warnings and makes me feel generally
bad about myself. :(</p>
<p>produces a few page faults of warnings and makes me feel generally bad about
myself. :(</p>
<h3 id="misc">Misc</h3>
<p>The reported size of the source code using the size tool is very
intentionally 2018.</p>
<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>
<p>The reported size of the source code using the size tool is very intentionally
2018.</p>
<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>
<p>For more information, see: https://creativecommons.org/licenses/by-sa/4.0/</p>
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- START: this line starts content for HTML phase 22 by: bin/output-index-inventory.sh via bin/md2html.sh -->
<!-- START: this line starts content generated by: bin/output-index-inventory.sh -->
<h1 id="inventory-for-2018algmyr"><a name="inventory"></a>Inventory for
2018/algmyr</h1>
<h1 id="inventory-for-2018algmyr"><a name="inventory"></a>Inventory for 2018/algmyr</h1>
<p><a href="#top">Jump to top</a></p>
<h2 id="primary-files">Primary files</h2>
<ul>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/prog.c">prog.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/prog.orig.c">prog.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/try.sh">try.sh</a>
- how to run</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/prog.c">prog.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/prog.orig.c">prog.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/try.sh">try.sh</a> - how to run</li>
<li><a href="spoiler.png">spoiler.png</a> - SPOILER WARNING</li>
<li><a href="2018_algmyr.tar.bz2">2018_algmyr.tar.bz2</a> - download
entry source</li>
<li><a href="2018_algmyr.tar.bz2">2018_algmyr.tar.bz2</a> - download entry source</li>
</ul>
<h2 id="secondary-files">Secondary files</h2>
<ul>
<li><a href="index.html">index.html</a> - entry home page</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/.gitignore">.gitignore</a>
- list of files that should not be committed under git</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/.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/2018/algmyr/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->