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

+48 -72
View File
@@ -129,9 +129,9 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Bas_de_Bakker">Bas de
Bakker</a><br> Location: <a href="../../location.html#NL">NL</a> -
<em>Kingdom of the Netherlands</em> (<em>Netherlands</em>) <br><br></li>
<li>Name: <a href="../../authors.html#Bas_de_Bakker">Bas de Bakker</a><br>
Location: <a href="../../location.html#NL">NL</a> - <em>Kingdom of the Netherlands</em> (<em>Netherlands</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -144,96 +144,72 @@ Bakker</a><br> Location: <a href="../../location.html#NL">NL</a> -
<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">./bas1.sh</span></span></code></pre></div>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>The output is supposed to be a 3D maze, but it is somewhat more than
that. If you’ve seen any of the <a
href="https://en.wikipedia.org/wiki/M._C._Escher">Maurits Escher’s</a>
<a href="https://mcescher.com/gallery/">works</a>, you’ll know what
we’re talking about.</p>
<p>When trying to run the program with command line arguments, be
generous.</p>
<p>The output is supposed to be a 3D maze, but it is somewhat more
than that. If you’ve seen any of the <a href="https://en.wikipedia.org/wiki/M._C._Escher">Maurits
Escher’s</a>
<a href="https://mcescher.com/gallery/">works</a>, you’ll know what we’re talking about.</p>
<p>When trying to run the program with command line arguments, be generous.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="bemazing">BEMAZING</h3>
<p>“You’re in a twisty little maze of beams, all different.”</p>
<p><code>Bemazing</code> is “amazing” taken one step (letter) further.
<code>Bemazing</code> creates a 3D maze of beams. Try to go from the
entrance (the unfinished beam in one corner) to the exit (the unfinished
beam in the opposite corner) or vice versa.</p>
<p>For maximum portability, <code>Bemazing</code> is not tied to any
window system, but creates postscript output. The picture it makes will
fit on either A4 or letter size paper.</p>
<p>In addition, because postscript is rather verbose,
<code>Bemazing</code> creates the postscript in <code>gzip(1)</code>
format, in order to save precious bits on your hard disk for the latest
version of <a href="https://www.gnu.org/software/emacs/">GNU Emacs</a>
(after all, you wouldn’t want to use an editor without a
psychoanalyze-pinhead function, now would you). Again for maximum
portability, <code>Bemazing</code> will take special care that the
binary output will not contain any newline or return characters that may
get weird treatment on systems that do not use the One True Line
Separator.</p>
<p><code>Bemazing</code> is “amazing” taken one step (letter) further. <code>Bemazing</code>
creates a 3D maze of beams. Try to go from the entrance (the
unfinished beam in one corner) to the exit (the unfinished beam in the
opposite corner) or vice versa.</p>
<p>For maximum portability, <code>Bemazing</code> is not tied to any window system, but
creates postscript output. The picture it makes will fit on either A4 or letter
size paper.</p>
<p>In addition, because postscript is rather verbose, <code>Bemazing</code> creates
the postscript in <code>gzip(1)</code> format, in order to save precious bits on your
hard disk for the latest version of <a href="https://www.gnu.org/software/emacs/">GNU
Emacs</a> (after all, you wouldn’t
want to use an editor without a psychoanalyze-pinhead function, now
would you). Again for maximum portability, <code>Bemazing</code> will take special
care that the binary output will not contain any newline or return
characters that may get weird treatment on systems that do not use the
One True Line Separator.</p>
<h3 id="notes">NOTES</h3>
<p>Be sure to view the source with something that can display characters
<code>\240-\377</code>. Use <code>LESSCHARSET=latin1</code>,
<code>M-x</code> <code>standard-display-european</code> in GNU Emacs
etc. The source does not use characters in the range
<code>\200-\237</code> (we are not an unnamed word processor that tends
to create HTML containing these control characters).</p>
<code>\240-\377</code>. Use <code>LESSCHARSET=latin1</code>, <code>M-x</code> <code>standard-display-european</code> in
GNU Emacs etc. The source does not use characters in the range
<code>\200-\237</code> (we are not an unnamed word processor that tends to create
HTML containing these control characters).</p>
<p>Because this is not the obfuscated postscript contest, the postscript
does not contain any <code>for</code>, <code>if</code> or other control
structures. All the logic is in the C code. There are only a few
straightforward <code>def</code>s, because otherwise the output would
become much larger.</p>
<p>Try running <code>Bemazing</code> with command line arguments and see
what happens. (But note that the program only guarantees that there
actually is a route from entrance to exit if you run it without command
line arguments.)</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>
does not contain any <code>for</code>, <code>if</code> or other control structures. All the
logic is in the C code. There are only a few straightforward <code>def</code>s,
because otherwise the output would become much larger.</p>
<p>Try running <code>Bemazing</code> with command line arguments and see what
happens. (But note that the program only guarantees that there
actually is a route from entrance to exit if you run it without
command line arguments.)</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-1998bas1"><a name="inventory"></a>Inventory for
1998/bas1</h1>
<h1 id="inventory-for-1998bas1"><a name="inventory"></a>Inventory for 1998/bas1</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/1998/bas1/bas1.c">bas1.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/bas1.orig.c">bas1.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/bas1.sh">bas1.sh</a>
- how to run bas1</li>
<li><a href="1998_bas1.tar.bz2">1998_bas1.tar.bz2</a> - download entry
source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/bas1.c">bas1.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/bas1.orig.c">bas1.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/bas1.sh">bas1.sh</a> - how to run bas1</li>
<li><a href="1998_bas1.tar.bz2">1998_bas1.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/1998/bas1/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/.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/1998/bas1/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/.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/1998/bas1/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->