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:
1 parent
9eb7a54e9f
commit
b0b212acb1
402 files changed
+37061
-55132
No files matched your search
+76
-112
@@ -130,8 +130,8 @@
|
||||
<h2 id="author"><a name="author"></a>Author:</h2>
|
||||
<ul>
|
||||
<li>Name: <a href="../../authors.html#Daniel_Vik">Daniel Vik</a><br>
|
||||
Location: <a href="../../location.html#US">US</a> - <em>United States of
|
||||
America</em> (<em>United States</em>) <br><br></li>
|
||||
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 -->
|
||||
@@ -142,13 +142,12 @@ America</em> (<em>United States</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>This entry requires <a href="https://www.zlib.net">Zlib</a>.</p>
|
||||
<p>There is an alternate version which might work for Windows. See <a
|
||||
href="#alternate-code">Alternate code</a> section below.</p>
|
||||
<p>There is an alternate version which might work for Windows. See <a href="#alternate-code">Alternate
|
||||
code</a> section below.</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#2012_vik">2012 vik bugs</a>.</p>
|
||||
<p>For more detailed information see <a href="../../bugs.html#2012_vik">2012 vik bugs</a>.</p>
|
||||
<h2 id="to-use">To use:</h2>
|
||||
<p>To embed text (from file or command line):</p>
|
||||
<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">./vik</span> e base.png filename <span class="op">></span> encodedimg.png</span></code></pre></div>
|
||||
@@ -163,8 +162,7 @@ href="../../bugs.html#2012_vik">2012 vik bugs</a>.</p>
|
||||
<h2 id="try">Try:</h2>
|
||||
<div class="sourceCode" id="cb8"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.sh</span></span></code></pre></div>
|
||||
<h2 id="alternate-code">Alternate code:</h2>
|
||||
<p>For those few who might use Windows this alternate code might
|
||||
work.</p>
|
||||
<p>For those few who might use Windows this alternate code might work.</p>
|
||||
<h3 id="alternate-build">Alternate build:</h3>
|
||||
<div class="sourceCode" id="cb9"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span> alt</span></code></pre></div>
|
||||
<h3 id="alternate-use">Alternate use:</h3>
|
||||
@@ -172,145 +170,111 @@ work.</p>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>References to chocolate had no effect on judging this entry. We
|
||||
guarantee it.</p>
|
||||
<p>Can you discern hidden pieces of chocolate in <a
|
||||
href="chocolate-in-ioccc.png">chocolate-in-ioccc.png</a>?</p>
|
||||
<p>Can you discern hidden pieces of chocolate in
|
||||
<a href="chocolate-in-ioccc.png">chocolate-in-ioccc.png</a>?</p>
|
||||
<figure>
|
||||
<img src="chocolate-in-ioccc.png" title="Chocolate in IOCCC"
|
||||
alt="chocolate in ioccc" />
|
||||
<img src="chocolate-in-ioccc.png" title="Chocolate in IOCCC" alt="chocolate in ioccc" />
|
||||
<figcaption aria-hidden="true">chocolate in ioccc</figcaption>
|
||||
</figure>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<h3 id="introduction">Introduction</h3>
|
||||
<p>This program is a <a
|
||||
href="https://en.wikipedia.org/wiki/Steganography">steganography</a>
|
||||
<p>This program is a <a href="https://en.wikipedia.org/wiki/Steganography">steganography</a>
|
||||
application for embedding an image or text into another image as well as
|
||||
extracting the embedded image or text back. The program stores the
|
||||
embedded image or text in the low bits of the RGB values.</p>
|
||||
<p>The program supports any 8 bit true color PNG images (RGB, RGBA,
|
||||
greyscale, and greyscale+alpha). The output image is always 8 bit RGB.
|
||||
When embedding one image into another, the width and height needs to be
|
||||
the same.</p>
|
||||
<p>The program only updates the <code>IDAT</code> and <code>IHDR</code>
|
||||
chunks of the source image. Any additional chunks are copied into the
|
||||
resulting image.</p>
|
||||
extracting the embedded image or text back. The program stores the embedded
|
||||
image or text in the low bits of the RGB values.</p>
|
||||
<p>The program supports any 8 bit true color PNG images (RGB, RGBA, greyscale,
|
||||
and greyscale+alpha). The output image is always 8 bit RGB. When embedding
|
||||
one image into another, the width and height needs to be the same.</p>
|
||||
<p>The program only updates the <code>IDAT</code> and <code>IHDR</code> chunks of the source image. Any
|
||||
additional chunks are copied into the resulting image.</p>
|
||||
<h3 id="bonus-extractor">Bonus Extractor:</h3>
|
||||
<p>For some reason the chocolate image seems to have some special
|
||||
properties. Apart from being quite big and a little bit noisy, it
|
||||
appears that when embedded into another image and extracted, the bitmap
|
||||
data is also a valid <a
|
||||
href="https://en.wikipedia.org/wiki/Brainfuck">brainfuck</a> program. It
|
||||
is of course possible to get the bitmap data from the extracted image,
|
||||
and run it through any of the previous winning brainfuck interpreters,
|
||||
but I thought it would be easier to include an interpreter in the
|
||||
program to avoid the hassle:</p>
|
||||
<div class="sourceCode" id="cb10"><pre
|
||||
class="sourceCode sh"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./vik</span> e ioccc.png chocolate.png <span class="op">></span> encodedimg.png</span>
|
||||
<p>For some reason the chocolate image seems to have some special properties.
|
||||
Apart from being quite big and a little bit noisy, it appears that when embedded
|
||||
into another image and extracted, the bitmap data is also a valid
|
||||
<a href="https://en.wikipedia.org/wiki/Brainfuck">brainfuck</a> program. It is of course
|
||||
possible to get the bitmap data from the extracted image, and run it through any
|
||||
of the previous winning brainfuck interpreters, but I thought it would be easier
|
||||
to include an interpreter in the program to avoid the hassle:</p>
|
||||
<div class="sourceCode" id="cb10"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./vik</span> e ioccc.png chocolate.png <span class="op">></span> encodedimg.png</span>
|
||||
<span id="cb10-2"><a href="#cb10-2" aria-hidden="true" tabindex="-1"></a><span class="ex">./vik</span> b encodedimg.png</span></code></pre></div>
|
||||
<p>It is of course also possible to embed a <a
|
||||
href="https://en.wikipedia.org/wiki/Brainfuck">brainfuck</a> program as
|
||||
a text file (as explained above) and decode it, e.g.:</p>
|
||||
<div class="sourceCode" id="cb11"><pre
|
||||
class="sourceCode sh"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./vik</span> e ioccc.png .+<span class="pp">[</span><span class="ss">.+</span><span class="pp">]</span> <span class="op">></span> encodedimg.png</span>
|
||||
<p>It is of course also possible to embed a
|
||||
<a href="https://en.wikipedia.org/wiki/Brainfuck">brainfuck</a> program as a text file
|
||||
(as explained above) and decode it, e.g.:</p>
|
||||
<div class="sourceCode" id="cb11"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./vik</span> e ioccc.png .+<span class="pp">[</span><span class="ss">.+</span><span class="pp">]</span> <span class="op">></span> encodedimg.png</span>
|
||||
<span id="cb11-2"><a href="#cb11-2" aria-hidden="true" tabindex="-1"></a><span class="ex">./vik</span> b encodedimg.png</span></code></pre></div>
|
||||
<h3 id="obfuscation">Obfuscation</h3>
|
||||
<p>I really wanted to keep the program simple, so instead of adding
|
||||
multiple macros or helper methods that can be confusing, I placed all
|
||||
functionality in the <code>main()</code> function. <code>main()</code>
|
||||
is called recursively and quite extensively, but it gives the benefit
|
||||
that all invocations of the function have the same parameters,
|
||||
<code>argv</code> and <code>argc</code>. This really helps readability,
|
||||
as a programmer doesn’t need to remember several variable or function
|
||||
names. I also tried to reduce the number of keywords, and the program
|
||||
only has four <code>for</code> loops followed by a single
|
||||
<code>return</code> statement. There is a little bit of use of the
|
||||
ternary (<code>?:</code>) operator, but this is really there to keep the
|
||||
program as simple as possible.</p>
|
||||
<p>I really wanted to keep the program simple, so instead of adding multiple macros
|
||||
or helper methods that can be confusing, I placed all functionality in the
|
||||
<code>main()</code> function. <code>main()</code> is called recursively and quite extensively, but it
|
||||
gives the benefit that all invocations of the function have the same parameters,
|
||||
<code>argv</code> and <code>argc</code>. This really helps readability, as a programmer doesn’t need
|
||||
to remember several variable or function names. I also tried to reduce the
|
||||
number of keywords, and the program only has four <code>for</code> loops followed by a single
|
||||
<code>return</code> statement. There is a little bit of use of the ternary (<code>?:</code>) operator,
|
||||
but this is really there to keep the program as simple as possible.</p>
|
||||
<h3 id="portability">Portability</h3>
|
||||
<p>The program is portable to most platforms that have <a
|
||||
href="https://www.zlib.net">zlib</a> available. The only system
|
||||
dependency is that the program relies on writing binary data to
|
||||
<code>stdout</code>.</p>
|
||||
<p>By default, Microsoft compilers adds carriage returns to new lines,
|
||||
and to compile the program on this platform, the following line can be
|
||||
added after the variable declarations in the main declaration in order
|
||||
to run correctly:</p>
|
||||
<p>The program is portable to most platforms that have <a href="https://www.zlib.net">zlib</a>
|
||||
available. The only system dependency is that the program relies on writing
|
||||
binary data to <code>stdout</code>.</p>
|
||||
<p>By default, Microsoft compilers adds carriage returns to new lines, and to
|
||||
compile the program on this platform, the following line can be added after
|
||||
the variable declarations in the main declaration in order to run
|
||||
correctly:</p>
|
||||
<div class="sourceCode" id="cb12"><pre class="sourceCode c"><code class="sourceCode c"><span id="cb12-1"><a href="#cb12-1" aria-hidden="true" tabindex="-1"></a>_setmode<span class="op">(</span>_fileno<span class="op">(</span>stdout<span class="op">),</span> <span class="bn">0x8000</span><span class="op">);</span></span></code></pre></div>
|
||||
<p>NOTE: this is what the <a href="#alternate-code">Alternate code</a>
|
||||
does.</p>
|
||||
<p>NOTE: this is what the <a href="#alternate-code">Alternate code</a> does.</p>
|
||||
<h3 id="limitations">Limitations</h3>
|
||||
<p>The program doesn’t have many error checks so passing in invalid
|
||||
arguments or images of mismatching sizes, or unsupported pixel formats
|
||||
will cause the program to crash.</p>
|
||||
<p>The program doesn’t have many error checks so passing in invalid arguments
|
||||
or images of mismatching sizes, or unsupported pixel formats will cause the
|
||||
program to crash.</p>
|
||||
<h3 id="extendability">Extendability</h3>
|
||||
<p>Since a lot of care was taken to keep the code simple, it turned out
|
||||
to be quite easy to extend functionality. I did include a small <a
|
||||
href="https://en.wikipedia.org/wiki/Brainfuck">brainfuck</a> after I
|
||||
<p>Since a lot of care was taken to keep the code simple, it turned out to be
|
||||
quite easy to extend functionality. I did include a small
|
||||
<a href="https://en.wikipedia.org/wiki/Brainfuck">brainfuck</a> after I
|
||||
realized that the chocolate image had some interesting properties.</p>
|
||||
<p>But there is more functionality I added that didn’t fit within the
|
||||
size limits and could not remain included. For example, I added a method
|
||||
to format source code based on a PNG image. So the format of the program
|
||||
is actually done by the program itself.</p>
|
||||
<p>And to be honest, the chocolate image did not have a <a
|
||||
href="https://en.wikipedia.org/wiki/Brainfuck">brainfuck</a> program
|
||||
<p>But there is more functionality I added that didn’t fit within the size
|
||||
limits and could not remain included. For example, I added a method to
|
||||
format source code based on a PNG image. So the format of the program is
|
||||
actually done by the program itself.</p>
|
||||
<p>And to be honest, the chocolate image did not have a
|
||||
<a href="https://en.wikipedia.org/wiki/Brainfuck">brainfuck</a> program
|
||||
embedded to begin with. I added functionality to the program to embed a
|
||||
brainfuck into a PNG image and used it to create the image provided with
|
||||
the entry.</p>
|
||||
<p>I also added a method to analyze PNG images, to print the size and
|
||||
format, as well as the scan line filters.</p>
|
||||
<p>All these features were quite easy to add, much thanks to the
|
||||
(actually pretty good) design of the code.</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>I also added a method to analyze PNG images, to print the size and format,
|
||||
as well as the scan line filters.</p>
|
||||
<p>All these features were quite easy to add, much thanks to the (actually
|
||||
pretty good) design of the code.</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-2012vik"><a name="inventory"></a>Inventory for
|
||||
2012/vik</h1>
|
||||
<h1 id="inventory-for-2012vik"><a name="inventory"></a>Inventory for 2012/vik</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/2012/vik/vik.c">vik.c</a>
|
||||
- entry source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/Makefile">Makefile</a>
|
||||
- entry Makefile</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/vik.alt.c">vik.alt.c</a>
|
||||
- alternative source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/vik.orig.c">vik.orig.c</a>
|
||||
- original source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/vik.c">vik.c</a> - entry source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/Makefile">Makefile</a> - entry Makefile</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/vik.alt.c">vik.alt.c</a> - alternative source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/vik.orig.c">vik.orig.c</a> - original source</li>
|
||||
<li><a href="chocolate.png">chocolate.png</a> - encoding image</li>
|
||||
<li><a href="ioccc.png">ioccc.png</a> - encoding image</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/try.sh">try.sh</a>
|
||||
- how to run</li>
|
||||
<li><a href="2012_vik.tar.bz2">2012_vik.tar.bz2</a> - download entry
|
||||
source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/try.sh">try.sh</a> - how to run</li>
|
||||
<li><a href="2012_vik.tar.bz2">2012_vik.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/2012/vik/.entry.json">.entry.json</a>
|
||||
- description of entry in JSON</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/.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/2012/vik/.entry.json">.entry.json</a> - description of entry in JSON</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/.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/2012/vik/README.md">README.md</a>
|
||||
- markdown source for index.html</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/vik/README.md">README.md</a> - markdown source for index.html</li>
|
||||
</ul>
|
||||
|
||||
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->
|
||||
|
||||
Reference in new issue
Block a user