render makrdown and rules, update sitemap

markdown.html

@@ -491,7 +491,9 @@ not apply to other markdown files), <strong>PLEASE</strong> start at level three
 </div>
 <h2 id="replace-a-nameanchor_namea-construct.">Replace <code>&lt;a name="anchor_name"&gt;&lt;/a&gt;</code> construct.</h2>
 <pre class="&lt;!---html--&gt;"><code>❌ &lt;a name=&quot;old_way&quot;&gt;...&lt;/a&gt;
-✔️ &lt;span id=&quot;new_way&quot;&gt;...&lt;/span&gt;</code></pre>
+✔️ &lt;div id=&quot;new_way&quot;&gt;...&lt;/div&gt;
+✔️ 
+✔️ ### Section title</code></pre>
 <div id="links">
 
 </div>
@@ -533,7 +535,7 @@ not apply to other markdown files), <strong>PLEASE</strong> start at level three
 <pre class="&lt;!---sh--&gt;"><code>❌ echo &quot;This code block is NOT indented&quot;</code></pre>
 <p>We request that you indent the code block by multiples of four (4)
 ASCII SPACES, never TAB (␉):</p>
-<pre class="&lt;!---sh--&gt;"><code>✔️     echo &quot;This code block is indented by multiples of 4 spaces&quot;
+<pre class="&lt;!---sh--&gt;"><code>✔️      echo &quot;This code block is indented by multiples of 4 spaces&quot;
 
 ✔️     # The top level starts with a 4 ASCII space indent.
 ✔️     #
@@ -564,19 +566,19 @@ ASCII SPACES.</p>
 ❌ ␉Please do **NOT**␉use ASCII tabs␉in markdown files.
 ❌ ␉␉Please do **NOT** indent markdown with ASCII tabs.
 
-❌ ␉We       don&#39;t␉mind␉tabs␉in␉general,
+❌ ␉We␉don&#39;t␉mind␉tabs␉in␉general,
 ❌ ␉We just ask that you NOT use them in markdown files.
 ```</code></pre>
 <p>And to clarify, we are only talking about markdown files, not C code or
 any other non-markdown content:</p>
-<pre class="&lt;!---c--&gt;"><code>✔️       printf(&quot;It is fine␉to␉use tabs in Obfuscated C code.\n&quot;);
+<pre class="&lt;!---c--&gt;"><code>✔️ ␉printf(&quot;It is fine␉to␉use tabs in Obfuscated C code.\n&quot;);
-✔️               /*␉if␉you␉wish    */
+✔️ ␉␉/*␉if␉you␉wish    */
 
-✔️       // We ask that you to NOT use ASCII tab characters in your remarks.md writeup,
+✔️ ␉// We ask that you to NOT use ASCII tab characters in your remarks.md writeup,
-✔️       // or in any other markdown files within your entry, please.</code></pre>
+✔️ ␉// or in any other markdown files within your entry, please.</code></pre>
-<p><strong>NOTE</strong>: Again, you are <strong>perfectly welcome</strong> to use ASCII tab characters
+<p><strong>NOTE</strong>: Again, you are <strong>perfectly welcome</strong> to use ASCII TAB (␉) characters
-in your C code and other non-markdown files. We simply ask that
+in your C code and other non-markdown files. We simply ask that you do
-you do <strong>NOT</strong> use any ASCII TAB (␉) characters in markdown files.</p>
+<strong>NOT</strong> use any ASCII TAB (␉) characters in markdown files.</p>
 <div id="code">
 
 </div>
@@ -629,9 +631,8 @@ block as this makes it easier to detect when markdown code blocks are
 
 </div>
 <h2 id="do-not-add-trailing-slash-to-void-html-tags.">Do not add trailing slash to void HTML tags.</h2>
-<p>Please do <strong>NOT</strong> use a trailing slash on
+<p>Please do <strong>NOT</strong> use a trailing slash on <a href="https://github.com/validator/validator/wiki/Markup-»-Void-elements">void HTML elements</a>. See also
-<a href="https://github.com/validator/validator/wiki/Markup-»-Void-elements">void HTML elements</a>.</p>
+this note on <a href="https://github.com/validator/validator/wiki/Markup-»-Void-elements#trailing-slashes-in-void-element-start-tags-do-NOT-mark-the-start-tags-as-self-closing">trailing slashes in void-element start tags</a>.</p>
-<p>See also this note on <a href="https://github.com/validator/validator/wiki/Markup-»-Void-elements#trailing-slashes-in-void-element-start-tags-do-NOT-mark-the-start-tags-as-self-closing">trailing slashes in void-element start tags</a>.</p>
 <p>The trailing slash on void HTML elements has no effect and interacts
 badly with unquoted attribute values.</p>
 <pre class="&lt;!---html--&gt;"><code>❌ &lt;br/&gt;
@@ -672,7 +673,7 @@ a markdown line with a trailing backslash (<code>\</code>). Instead use a traili
 
 ✔️ `This is OK\`</code></pre>
 <p>Doing it this way will prevent <code>pandoc(1)</code> from generating deprecated
-HTML elements such as <code>&lt;br /&gt;</code>.</p>
+HTML elements, such as <code>&lt;br /&gt;</code>.</p>
 <div id="img">
 
 </div>
@@ -700,7 +701,6 @@ a line with 3 or more dashes (“<code>-</code>”s).</p>
 <p>Such markdown causes <code>pandoc(1)</code> to generate <code>&lt;hr /&gt;</code>. The <code>&lt;hr /&gt;</code> has
 no effect in standard HTML 5 and interacts badly with unquoted attribute
 values.</p>
-<p>If a horizontal line is really needed, use:</p>
 <pre class="&lt;!---html--&gt;"><code>❌ * * *
 ❌ - - -
 ❌ ---
@@ -744,8 +744,8 @@ go for when it is <strong><em>bold and italic</em></strong>.</p>
 ❌ ***this text is bold italic***
 ✔️ **_this text is bold italic_**
 ✔️ _**this text is bold italic**_</code></pre>
-<p><strong>BTW</strong>: the astute reader might notice that some cases of <code>*</code> for
+<p><strong>BTW</strong>: the astute reader might notice that some cases of <code>*</code> for italic
-italic might have slipped through. We do ask you, however, to please
+might have slipped through. We do ask you, however, to please
 observe this rule, as best you can.
 <!-- AFTER: last line of markdown file: markdown.md --></p>
 

next/rules.html

@@ -476,7 +476,7 @@ app from time to time to view IOCCC mastodon updates.</p>
 <h1 id="th-international-obfuscated-c-code-contest-official-rules">29th International Obfuscated C Code Contest Official Rules</h1>
 <p>Copyright © 2025 Leonid A. Broukhis and Landon Curt Noll.</p>
 <p>All Rights Reserved. Permission for personal, education or non-profit use is
-granted provided this this copyright and notice are included in its entirety
+granted provided this copyright and notice are included in its entirety
 and remains unaltered. All other uses <strong>MUST</strong> receive prior permission in
 writing by <a href="../contact.html">contacting the judges</a>.</p>
 <h2 id="rules-version">Rules Version</h2>
@@ -638,13 +638,13 @@ and
 <h2 id="rule-9---no-hands">Rule 9 - No hands</h2>
 </div>
 <p>Entries requiring human interaction to be initially compiled are <strong>NOT</strong>
-permitted. However, see the guidelines. Each entry <strong>MUST</strong> automated the
+permitted. However, see the guidelines. Each entry <strong>MUST</strong> automate the
-its build process using <code>bash</code>, <code>gmake</code>, <code>gcc</code>, <code>clang</code>, under a
+build process using <code>bash</code>, <code>gmake</code>, <code>gcc</code>, <code>clang</code>, under a
 <a href="https://pubs.opengroup.org/onlinepubs/9799919799/">SUS environment</a>.</p>
 <p>Note references to <code>gmake</code> can be any GNU Make compatible tool.</p>
 <p>See <a href="rules.html#rule-15---building">Rule 15 - Building</a>.</p>
 <div id="rule10">
-<p>Rule 10 - Privileges</p>
+<h2 id="rule-10---privileges">Rule 10 - Privileges</h2>
 </div>
 <p>Programs that require special privileges (setuid(2), setgid(2),
 super-user, special owner, special group, etc.) are <strong>HIGHLY DISCOURAGED</strong>.
@@ -712,7 +712,7 @@ didn’t previously win, then you are encouraged to mention this in your
 <h2 id="rule-15---building">Rule 15 - Building</h2>
 </div>
 <p>The <code>Makefile</code> <strong>MUST</strong> adhere to GNU Makefile syntax. Its recommended
-that you copy and rename the <code>Makefile.example</code> as template. The primary
+that you copy and rename the <code>Makefile.example</code> as a template. The primary
 target of the <code>Makefile</code> <strong>MUST</strong> be <code>prog</code> and the source file is <code>prog.c</code>.
 The C compiler and preprocessor <strong>MUST</strong> be invoked using <code>${CC}</code> and <code>${CPP}</code>
 macros respectively.</p>
@@ -796,7 +796,7 @@ for an overview of how to enter the contest.</p>
 <p>See also the <a href="../faq.html">FAQ</a>.</p>
 <p>Consider joining the <a href="https://discord.com/invite/Wa42Qujwnw">IOCCC Discord Server</a>
 for discussions about The Rules, questions for the Judges, and <code>C</code> in general.</p>
-<p>Leonid A. Broukhis
+<p>Leonid A. Broukhis<br />
 chongo (Landon Curt Noll) /\cc/\
 <!-- AFTER: last line of markdown file: next/rules.md --></p>
 

sitemap.xml

@@ -16810,11 +16810,11 @@
 </url>
 <url>
     <loc>https://www.ioccc.org/markdown.html</loc>
-    <lastmod>2025-11-27T07:21:50+00:00</lastmod>
+    <lastmod>2025-11-27T15:59:15+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/markdown.md</loc>
-    <lastmod>2025-11-27T07:21:43+00:00</lastmod>
+    <lastmod>2025-11-27T15:58:56+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/news.html</loc>
@@ -16826,11 +16826,11 @@
 </url>
 <url>
     <loc>https://www.ioccc.org/next/guidelines.html</loc>
-    <lastmod>2025-11-27T07:11:14+00:00</lastmod>
+    <lastmod>2025-11-27T15:58:32+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/next/guidelines.md</loc>
-    <lastmod>2025-11-27T07:11:14+00:00</lastmod>
+    <lastmod>2025-11-27T15:58:32+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/next/index.html</loc>
@@ -16870,11 +16870,11 @@
 </url>
 <url>
     <loc>https://www.ioccc.org/next/rules.html</loc>
-    <lastmod>2025-11-27T07:11:14+00:00</lastmod>
+    <lastmod>2025-11-27T15:59:14+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/next/rules.md</loc>
-    <lastmod>2025-11-27T07:11:14+00:00</lastmod>
+    <lastmod>2025-11-27T15:58:56+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/next/submit.html</loc>