force use of pandoc version >= 3.1.12.2

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

No files matched your search

+44 -69
View File
@@ -129,9 +129,9 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Peter_Klausler">Peter
Klausler</a><br> Location: <a href="../../location.html#US">US</a> -
<em>United States of America</em> (<em>United States</em>) <br><br></li>
<li>Name: <a href="../../authors.html#Peter_Klausler">Peter Klausler</a><br>
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -146,90 +146,65 @@ Klausler</a><br> Location: <a href="../../location.html#US">US</a> -
<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">./try.sh</span></span></code></pre></div>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>To reduce the size of the source, include other people’s data. That
is what Peter suggests when he describes how to generate a critical
header file.</p>
<p>To reduce the size of the source, include other people’s data.
That is what Peter suggests when he describes how to generate
a critical header file.</p>
<p>In other words: make use of other words! :-)</p>
<p>Rules might have to be changed!</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>A useful tool to help one appear extra smart and witty when <a
href="https://en.wikipedia.org/wiki/Internet_Relay_Chat">IRCing</a>, or
even to just be highly annoying.</p>
<p>Finds best anagrams for word or phrase given as program arguments.
Use only lower-case letters in these arguments. Output is sorted firstly
in ascending order of word count (fewer words are better) and secondly
in descending order of word length. Pipe the output into
<code>more(1)</code>/<code>less(1)</code>/<code>head(1)</code> and
you’re likely to find the most amusing possibilities in the first few
screenfuls of output. For example,
<code>./klausler fawlty towers | more</code> quickly prints “waterfowl
sty”. The fewer obscure short words in your system’s dictionary, the
better the quality of the output; indeed, all one-letter words apart
from <code>a</code>, <code>i</code>, and <code>s</code> (for plurals)
are ignored when the dictionary is constructed by
<code>make dict.h</code>.</p>
<p>Some history and explanation: When I noticed the call for entries in
this year’s IOCCC, I submitted two of them. I worked on the first one
very hard to obfuscate it beautifully, using a goofy algorithm,
wonderful two’s-complement arithmetic tricks, and cute formatting. It
was a glorious work so lovely as to make even strong men weep in
admiration… but it didn’t win anything. On the other hand, this crappy
little other program, which was only mildly obfuscated from its original
hacked form, took home an award!</p>
<p>I’m embarrassed to admit that I don’t even know which specific rule
this entry has abused. It’s just yet another anagram generator and it
was written very late one night. And now I honestly do not know how it
works, so please don’t ask. Upon reviewing the program after its
unexpected honor, I guess that it’s remarkable only for its complete
lack of macros, sneaky naming, <code>main()</code> recursion, or other
tricks. Enjoy!</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>A useful tool to help one appear extra smart and witty when
<a href="https://en.wikipedia.org/wiki/Internet_Relay_Chat">IRCing</a>, or even to
just be highly annoying.</p>
<p>Finds best anagrams for word or phrase given as program arguments. Use only
lower-case letters in these arguments. Output is sorted firstly in ascending
order of word count (fewer words are better) and secondly in descending order
of word length. Pipe the output into <code>more(1)</code>/<code>less(1)</code>/<code>head(1)</code> and you’re likely
to find the most amusing possibilities in the first few screenfuls of output.
For example, <code>./klausler fawlty towers | more</code> quickly prints “waterfowl sty”. The
fewer obscure short words in your system’s dictionary, the better the quality
of the output; indeed, all one-letter words apart from <code>a</code>, <code>i</code>, and <code>s</code> (for
plurals) are ignored when the dictionary is constructed by <code>make dict.h</code>.</p>
<p>Some history and explanation: When I noticed the call for entries in this
year’s IOCCC, I submitted two of them. I worked on the first one very hard to
obfuscate it beautifully, using a goofy algorithm, wonderful two’s-complement
arithmetic tricks, and cute formatting. It was a glorious work so lovely as to
make even strong men weep in admiration… but it didn’t win anything. On the
other hand, this crappy little other program, which was only mildly obfuscated
from its original hacked form, took home an award!</p>
<p>I’m embarrassed to admit that I don’t even know which specific rule this entry
has abused. It’s just yet another anagram generator and it was written very
late one night. And now I honestly do not know how it works, so please don’t
ask. Upon reviewing the program after its unexpected honor, I guess that it’s
remarkable only for its complete lack of macros, sneaky naming, <code>main()</code>
recursion, or other tricks. Enjoy!</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-2005klausler"><a name="inventory"></a>Inventory
for 2005/klausler</h1>
<h1 id="inventory-for-2005klausler"><a name="inventory"></a>Inventory for 2005/klausler</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/2005/klausler/klausler.c">klausler.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/klausler.orig.c">klausler.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/try.sh">try.sh</a>
- how to run</li>
<li><a href="2005_klausler.tar.bz2">2005_klausler.tar.bz2</a> - download
entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/klausler.c">klausler.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/klausler.orig.c">klausler.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/try.sh">try.sh</a> - how to run</li>
<li><a href="2005_klausler.tar.bz2">2005_klausler.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/2005/klausler/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/.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/2005/klausler/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/.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/2005/klausler/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/klausler/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->