improve how markdown code language is commented

We added a space between the markdown triple code mark
and language that was enclosed in HTML comments.

So a line of the form:

````
```<!---c--->
````

became:

````
``` <!---c--->
````

This was done to **help** some code see that the HTML comment
string was not a markdown code specifier.   Not all code
understands this after this changed.  For example, `pandoc(1)`
still forms HTML classes of the form "&lt;!---c--&gt;"
when it encounters the above mentioned change.

We also fixed a problem with `2019/dogon/README.md` regarding
a markdown code block.

We also fixed a problem with `2020/yang/README.md` regarding
a markdown code block.

2019/dogon/README.md

@@ -247,13 +247,13 @@ of his vast knowledge regarding GOL programming and hashlife. As a free bonus,
 Tom has allowed me to show his code which is probably the most efficient yet
 most obfuscated way of calculating the GOL function on a 64 bits `8*8` leaf:
 
-```<!---`c-->
+``` <!---c-->
     unsigned long life8x8(long a) { unsigned long aw = a << 1, ae = a >> 1, s0 = aw
     ^ ae, s1 = aw & ae, hs0 = s0 ^ a, hs1 = (s0 & a) | s1, hs0w8 = hs0 >> 8, hs0e8 =
     hs0 << 8, hs1w8 = hs1 >> 8, hs1e8 = hs1 << 8, ts0 = hs0w8 ^ hs0e8, ts1 = (hs0w8
     & hs0e8) | (ts0 & s0); return (hs1w8 ^ hs1e8 ^ ts1 ^ s1) & ((hs1w8 | hs1e8) ^
     (ts1 | s1)) & ((ts0 ^ s0) | a); }
-```<!---`-->
+```
 
 This uses only 19 bitwise operations and six shifts to calculate the inner 6x6
 next generation bits of the input 8x8 !

2019/dogon/index.html

@@ -321,7 +321,11 @@ master, who reviewed some earlier versions of the entry and freely shared some
 of his vast knowledge regarding GOL programming and hashlife. As a free bonus,
 Tom has allowed me to show his code which is probably the most efficient yet
 most obfuscated way of calculating the GOL function on a 64 bits <code>8*8</code> leaf:</p>
-<p><code>&lt;!---`c--&gt;     unsigned long life8x8(long a) { unsigned long aw = a &lt;&lt; 1, ae = a &gt;&gt; 1, s0 = aw     ^ ae, s1 = aw &amp; ae, hs0 = s0 ^ a, hs1 = (s0 &amp; a) | s1, hs0w8 = hs0 &gt;&gt; 8, hs0e8 =     hs0 &lt;&lt; 8, hs1w8 = hs1 &gt;&gt; 8, hs1e8 = hs1 &lt;&lt; 8, ts0 = hs0w8 ^ hs0e8, ts1 = (hs0w8     &amp; hs0e8) | (ts0 &amp; s0); return (hs1w8 ^ hs1e8 ^ ts1 ^ s1) &amp; ((hs1w8 | hs1e8) ^     (ts1 | s1)) &amp; ((ts0 ^ s0) | a); }</code><!---`--></p>
+<pre class="&lt;!---c--&gt;"><code>    unsigned long life8x8(long a) { unsigned long aw = a &lt;&lt; 1, ae = a &gt;&gt; 1, s0 = aw
+    ^ ae, s1 = aw &amp; ae, hs0 = s0 ^ a, hs1 = (s0 &amp; a) | s1, hs0w8 = hs0 &gt;&gt; 8, hs0e8 =
+    hs0 &lt;&lt; 8, hs1w8 = hs1 &gt;&gt; 8, hs1e8 = hs1 &lt;&lt; 8, ts0 = hs0w8 ^ hs0e8, ts1 = (hs0w8
+    &amp; hs0e8) | (ts0 &amp; s0); return (hs1w8 ^ hs1e8 ^ ts1 ^ s1) &amp; ((hs1w8 | hs1e8) ^
+    (ts1 | s1)) &amp; ((ts0 ^ s0) | a); }</code></pre>
 <p>This uses only 19 bitwise operations and six shifts to calculate the inner 6x6
 next generation bits of the input 8x8 !</p>
 <!--

2020/yang/README.md

@@ -1,20 +1,20 @@
 ## To build:
 
-```<!---<!---sh-->-->
+``` <!---sh-->
     make
 ```
 
 
 ## To use:
 
-```<!---<!---sh-->-->
+``` <!---sh-->
     ./prog [PIN] < input.txt > output.c
 ```
 
 
 ## Try:
 
-```<!---<!---sh-->-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -22,7 +22,7 @@
 The author provided the file [cppp.cc](cppp.cc) which can preprocess the
 generated output to make them more acceptable to typical compilers. To build:
 
-```<!---<!---sh-->-->
+``` <!---sh-->
     make cppp
 ```
 
@@ -44,7 +44,7 @@ spoiler](spoiler.html) that shows how this entry was written.
 
 ### Synopsis
 
-```<!---<!---sh-->-->
+``` <!---sh-->
     echo "Hello world" | ./prog 12345 > encoded.c
 
     gcc -DPIN=12345 encoded.c -o ./decoded && ./decoded
@@ -63,14 +63,14 @@ Mile is a C code generator.  Run without arguments for the help message below:
 When run with an encoding PIN (first command line argument), Mile will
 read bytes from `stdin` and generate C code on `stdout`.  Example:
 
-```<!---<!---sh-->-->
+``` <!---sh-->
     echo "Hello, world!" | ./prog 56789 > encoded.c
 ```
 
 This generated code will reproduce the same input bytes on `stdout` when
 executed, if it was compiled with the same encoding PIN.
 
-```<!---<!---sh-->-->
+``` <!---sh-->
     gcc -DPIN=56789 encoded.c -o decoded
 ```
 

2020/yang/index.html

@@ -141,14 +141,14 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
 
 <h2 id="to-build">To build:</h2>
-<pre class="&lt;!---&lt;!---sh--&gt;--&gt;"><code>    make</code></pre>
+<pre class="&lt;!---sh--&gt;"><code>    make</code></pre>
 <h2 id="to-use">To use:</h2>
-<pre class="&lt;!---&lt;!---sh--&gt;--&gt;"><code>    ./prog [PIN] &lt; input.txt &gt; output.c</code></pre>
+<pre class="&lt;!---sh--&gt;"><code>    ./prog [PIN] &lt; input.txt &gt; output.c</code></pre>
 <h2 id="try">Try:</h2>
-<pre class="&lt;!---&lt;!---sh--&gt;--&gt;"><code>    ./try.sh</code></pre>
+<pre class="&lt;!---sh--&gt;"><code>    ./try.sh</code></pre>
 <p>The author provided the file <a href="cppp.cc">cppp.cc</a> which can preprocess the
 generated output to make them more acceptable to typical compilers. To build:</p>
-<pre class="&lt;!---&lt;!---sh--&gt;--&gt;"><code>    make cppp</code></pre>
+<pre class="&lt;!---sh--&gt;"><code>    make cppp</code></pre>
 <p>See the author’s remarks for more details.</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>You might think of this entry as code obfuscater with a code.
@@ -159,7 +159,7 @@ What is compiling this entry about?
 spoiler</a> that shows how this entry was written.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <h3 id="synopsis">Synopsis</h3>
-<pre class="&lt;!---&lt;!---sh--&gt;--&gt;"><code>    echo &quot;Hello world&quot; | ./prog 12345 &gt; encoded.c
+<pre class="&lt;!---sh--&gt;"><code>    echo &quot;Hello world&quot; | ./prog 12345 &gt; encoded.c
 
     gcc -DPIN=12345 encoded.c -o ./decoded &amp;&amp; ./decoded</code></pre>
 <h3 id="details">Details</h3>
@@ -169,10 +169,10 @@ spoiler</a> that shows how this entry was written.</p>
     where [PIN] is an integer in the range of 1..65535</code></pre>
 <p>When run with an encoding PIN (first command line argument), Mile will
 read bytes from <code>stdin</code> and generate C code on <code>stdout</code>. Example:</p>
-<pre class="&lt;!---&lt;!---sh--&gt;--&gt;"><code>    echo &quot;Hello, world!&quot; | ./prog 56789 &gt; encoded.c</code></pre>
+<pre class="&lt;!---sh--&gt;"><code>    echo &quot;Hello, world!&quot; | ./prog 56789 &gt; encoded.c</code></pre>
 <p>This generated code will reproduce the same input bytes on <code>stdout</code> when
 executed, if it was compiled with the same encoding PIN.</p>
-<pre class="&lt;!---&lt;!---sh--&gt;--&gt;"><code>    gcc -DPIN=56789 encoded.c -o decoded</code></pre>
+<pre class="&lt;!---sh--&gt;"><code>    gcc -DPIN=56789 encoded.c -o decoded</code></pre>
 <p>The generated code reconstructs all data at compile time by seeding a
 random number generator with the given PIN to reproduce the input bytes,
 and simply does one <code>fwrite(3)</code> call at run time to print those bytes. Not

contact.html

@@ -145,8 +145,16 @@ problem has already been reported. If it has been reported, feel
 free to add a comment to the issue. If you do not find an it has
 been reported, then fee free to open a <a href="https://github.com/ioccc-src/winner/issues">new IOCCC
 issue</a>.</p>
+<p>If you are trying to:</p>
+<ul>
+<li>Comment or make a suggestion on IOCCC rules - (see <a href="faq.html#feedback">FAQ 0.5</a>)</li>
+<li>Comment or make a suggestion on IOCCC guidelines - (see <a href="faq.html#feedback">FAQ 0.5</a>)</li>
+<li>Comment or make a suggestion on IOCCC tools - (see <a href="faq.html#feedback">FAQ 0.5</a>)</li>
+</ul>
+<p>Those FAQ entries will help guide you on how to make public comments
+and suggestion in the relevant places.</p>
 <p>See the above FAQ entries for more details.</p>
-<h1 id="try-mastodon">Try mastodon</h1>
+<h1 id="try-mastodon"><a name="mastodon"></a>Try mastodon</h1>
 <p>You may wish to follow us <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a>
 as we use that platform to announce things such as the opening of a new IOCCC
 as well as winning entries of the IOCCC.</p>

faq.html

@@ -130,6 +130,7 @@
 <li><a href="#faq0_2">0.2 - What should I put in my entry’s Makefile?</a></li>
 <li><a href="#faq0_3">0.3 - May I use a different source or compiled filename than prog.c or prog?</a></li>
 <li><a href="#faq0_4">0.4 - What platform should I assume for my entry?</a></li>
+<li><a href="#faq0_5">0.5 - How may I comment or make a suggestion on IOCCC rules, guidelines and tools?</a></li>
 </ul>
 <h2 id="section-1---history-of-the-ioccc">Section 1 - <a href="#faq1">History of the IOCCC</a></h2>
 <ul>
@@ -405,6 +406,26 @@ If it can compile and run on Windows and/or Mac (see
 <a href="years.html#2000_thadgavin">2000/thadgavin</a> for one example, amongst others),
 even better. Being able to compile with other compilers like clang is also a
 good thing.</p>
+<h3 id="faq-0.5-how-may-i-comment-or-make-a-suggestion-on-ioccc-rules-guidelines-and-tools"><a name="faq0_5"></a><a name="feedback"></a>FAQ 0.5: How may I comment or make a suggestion on IOCCC rules, guidelines and tools?</h3>
+<p>The <a href="judges.html">IOCCC judges</a> to welcome feedback on the <a href="next/rules.html">IOCCC
+rules</a>, <a href="next/guidelines.html">IOCCC guidelines</a>
+and on the <a href="https://github.com/ioccc-src/mkiocccentry">IOCCC mkiocccentry tools</a>.</p>
+<p>To comment on the <a href="next/rules.html">IOCCC rules</a> or the
+<a href="next/guidelines.html">IOCCC guidelines</a> please view the
+<a href="https://github.com/ioccc-src/temp-test-ioccc/discussions">GitHub discussions for this repo</a>.
+If there is an on-going discussion that seems relevant to what you
+have to say, consider adding comments to that particular discussion.
+Otherwise consider opening a <a href="https://github.com/ioccc-src/temp-test-ioccc/discussions/new/choose">new IOCCC repo
+discussion</a>.</p>
+<p>To comment on <a href="https://github.com/ioccc-src/mkiocccentry">IOCCC mkiocccentry tools</a>,
+please view the <a href="https://github.com/ioccc-src/mkiocccentry/discussions">mkiocccentry repo discussions</a>.
+If there is an on-going discussion that seems relevant to what you
+have to say, consider adding comments to that particular discussion.
+Otherwise consider opening a <a href="https://github.com/ioccc-src/mkiocccentry/discussions/new/choose">new mkiocccentry
+discussion</a>.</p>
+<p>As a very last resort and/or if you feel the need to engage in a private
+discussion with the <a href="judges.html">IOCCC judges</a>, then see
+<a href="contact.html">How to contact the IOCCC</a>.</p>
 <h2 id="section-1-history-of-the-ioccc"><a name="faq1"></a>Section 1: History of the IOCCC</h2>
 <h3 id="faq-1.0-how-did-the-ioccc-get-started"><a name="faq1_0"></a><a name="ioccc_start"></a>FAQ 1.0: How did the IOCCC get started?</h3>
 <p>One day (1984 March 23 to be exact), Larry Bassel and I (Landon Curt

status.html

@@ -132,7 +132,7 @@
 <span id="cb1-2"><a href="#cb1-2" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;no_comment&quot;</span> <span class="fu">:</span> <span class="st">&quot;mandatory comment: because comments were removed from the original JSON spec&quot;</span><span class="fu">,</span></span>
 <span id="cb1-3"><a href="#cb1-3" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;IOCCC_status_version&quot;</span> <span class="fu">:</span> <span class="st">&quot;1.0 2024-03-09&quot;</span><span class="fu">,</span></span>
 <span id="cb1-4"><a href="#cb1-4" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;contest_status&quot;</span> <span class="fu">:</span> <span class="st">&quot;closed&quot;</span><span class="fu">,</span></span>
-<span id="cb1-5"><a href="#cb1-5" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;news_update&quot;</span> <span class="fu">:</span> <span class="st">&quot;2024-04-04T21:27:31+00:00&quot;</span><span class="fu">,</span></span>
+<span id="cb1-5"><a href="#cb1-5" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;news_update&quot;</span> <span class="fu">:</span> <span class="st">&quot;2024-04-12T18:22:04+00:00&quot;</span><span class="fu">,</span></span>
 <span id="cb1-6"><a href="#cb1-6" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;status_update&quot;</span> <span class="fu">:</span> <span class="st">&quot;2024-03-31T05:02:06+00:00&quot;</span></span>
 <span id="cb1-7"><a href="#cb1-7" aria-hidden="true" tabindex="-1"></a><span class="fu">}</span></span></code></pre></div>
 

status.json

@@ -2,6 +2,6 @@
     "no_comment" : "mandatory comment: because comments were removed from the original JSON spec",
     "IOCCC_status_version" : "1.0 2024-03-09",
     "contest_status" : "closed",
-    "news_update" : "2024-04-04T21:27:31+00:00",
+    "news_update" : "2024-04-12T18:22:04+00:00",
     "status_update" : "2024-03-31T05:02:06+00:00"
 }