Various fixes and updates

The links to rules should all be good. This includes in news.html, quick-start.html, next/submit.html, 2024/index.html (it had been modified to refer to next/rules.html instead of 2024/rules.html) as well as the guidelines and rules themselves (under next/). Various typo fixes. I'm afraid there are likely others but I must let others deal with that as I am out of time. Removed FAQ about mastodon push notifications. When I added the FAQ about push notifications for mastodon I was incorrect. The web browser interface suggests it but I never got a push notification even before Apple broke them. There seems to be no way at this time to get them. I note that there was a screenshot in the FAQ but this file still is in the repo possibly. I regenerated the html files but it's possible I forgot to do one at the last minute.
2025-11-29 12:03:55 -08:00
1 parent 28349bfb95
commit 6c49bc8955
@@ -460,9 +460,9 @@ IOCCC in the past.</p>
 <p>These rules are a <strong>TENTATIVE proposal</strong> for the next IOCCC
 and are <strong>likely be to be updated</strong> before the next IOCCC.</p>
 <p>See our
-FAQ on “<a href="../faq.html#feedback">rules, guidelines and tools feedback</a>”
+FAQ on “<a href="../faq.html#feedback">rules, guidelines, tools feedback</a>”
 as well as our
-FAQ on “<a href="../faq.html#question">asking questions</a>”
+FAQ on “<a href="../faq.html#question">about asking questions</a>”
 about these rules. You might also find the FAQ in general useful, especially the
 FAQ on “<a href="../quick-start.html#enter">how to enter the IOCCC</a>”.</p>
 <p>Watch both <a href="../status.html">the IOCCC status page</a> and the
@@ -503,10 +503,12 @@ of the above <strong>dates and times may change <em>AT ANY TIME</em></strong>!</
 <div id="rule2">
 <div id="rule2-size-restrictions">
 <div id="rule2-size">
+<div id="rule-2---size">
 <h2 id="rule-2---size-restrictions">Rule 2 - Size restrictions</h2>
 </div>
 </div>
 </div>
+</div>
 <p><code>Rule 2</code> requires that your submission satisfy <strong>BOTH</strong>
 <a href="rules.html#rule2a">Rule 2a (Gross Size)</a>
 and
@@ -516,9 +518,11 @@ During development this can be checked using <code>iocccsize(1)</code>:</p>
 <p>See the <a href="guidelines.html#guideline-2---size">Guidelines for Rule 2 - Size restrictions</a>.</p>
 <div id="rule2a">
 <div id="rule2a-gross-size">
+<div id="rule-2a-gross-size">
 <h3 id="rule-2a---gross-size">Rule 2a - Gross Size</h3>
 </div>
 </div>
+</div>
 <p>The overall maximum size of your <code>prog.c</code> program source <strong>MUST NOT</strong>
 exceed <strong>4993</strong> bytes.</p>
 <p><strong>NOTE</strong>: by default <code>iocccsize</code> will only report the rule 2b size, unless the
@@ -526,9 +530,11 @@ code surpasses the limit.</p>
 <p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>.</p>
 <div id="rule2b">
 <div id="rule2b-net-size">
+<div id="rule-2b-net-size">
 <h3 id="rule-2b---net-size">Rule 2b - Net Size</h3>
 </div>
 </div>
+</div>
 <p>When the filename of your program source (i.e., <code>prog.c</code>) is given as a
 command line argument to the latest version of the official IOCCC size
 tool (hereby referred to as <code>iocccsize(1)</code>), the value printed <strong>MUST
@@ -615,7 +621,8 @@ a case insensitive filesystem.</p></li>
 <p>See the
 FAQ on “<a href="../faq.html#file_perms">What permissions may my files be and what if I need different permissions?</a>”.</p>
 <p>See the <a href="guidelines.html#mkiocccentry_toolkit">Guidelines on the mkiocccentry toolkit</a>.</p>
-<p>See the <a href="guidelines.html#makefile">Guidelines on the Makefile</a>.</p>
+<p>See the
+FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommendations for a submission Makefile?</a>”.</p>
 <div id="rule5">
 <div id="rule5-modifying-files">
 <h2 id="rule-5---do-not-modify-submitted-files-or-filenames-or-parent-directories">Rule 5 - Do NOT modify submitted files or filenames or parent directories</h2>
@@ -677,9 +684,9 @@ validate your submission.</p>
 <p>Do <strong>NOT</strong> register more than one account!</p>
 <p>See
 <a href="rules.html#rule3-register">Rule 3 - Registering for the IOCCC</a>,
-<a href="rules.html#rule15-gnu-makefile">Rule 15 - GNU Makefile compatibility</a>,
+<a href="rules.html#rule15-gnu-makefile">Rule 15 - GNU Makefile</a>,
 and
-<a href="rules.html#rule-17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p>
+<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p>
 <div id="rule9">
 <h2 id="rule-9---no-interactive-compiling-allowed">Rule 9 - No interactive compiling allowed</h2>
 </div>
@@ -693,7 +700,7 @@ environment</a>.</p>
 the make command.</p>
 <p><strong>NOTE</strong>: it is better and more portable to <strong>NOT</strong> modify the <code>${CC}</code> variable
 in the Makefile.</p>
-<p>See <a href="rules.html#rule-15---building">Rule 15 - GNU Makefile compatibility</a>.</p>
+<p>See <a href="rules.html#rule15-gnu-makefile">Rule 15 - GNU Makefile</a>.</p>
 <div id="rule10">
 <h2 id="rule-10---program-file-permissions">Rule 10 - Program file permissions</h2>
 </div>
@@ -750,8 +757,8 @@ be rejected. Please do <strong>NOT</strong> put trailing CTRL+M in <code>prog.c<
 or <code>remarks.md</code> files, but instead end lines with Unix newline (line-feed,
 CTRL+J, <code>\n</code>).</p>
 <p>You are permitted, in order to try and squeeze your <code>prog.c</code> under a
-<a href="rules.html#rule-2a-gross-size">Rule 2a Gross Size</a> and/or
-<a href="rules.html#rule-2b-net-size">Rule 2b Net Size</a>
+<a href="rules.html#rule2a-gross-size">Rule 2a Gross Size</a> and/or
+<a href="rules.html#rule2b-net-size">Rule 2b Net Size</a>
 limits, to <strong>NOT</strong> end source with a newline. If you
 need to do this, please document that in your <code>remarks.md</code> file and if
 your compiler complains about this, document this too and update your
@@ -793,8 +800,9 @@ GNU long name options (such as <code>--example</code>) or extensions like <code>
 <p>Do <strong>NOT</strong> assume that <code>.</code> (current directory) is in the <code>$PATH</code> environment
 variable.</p>
 <p>See <a href="rules.html#rule4-required-files">Rule 4 - Required files</a>.</p>
-<p>See FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommendations for a submission Makefile?</a>”.</p>
-<p>See <a href="guidelines.html#guideline-15---building">Guidelines for Rule 15 - GNU Makefile compatibility</a>.</p>
+<p>See
+FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommendations for a submission Makefile?</a>”.</p>
+<p>See <a href="guidelines.html#guideline-15---building">Guidelines for Rule 15 - GNU Makefile</a>.</p>
 <div id="rule16">
 <div id="rule16-anonymous-judging">
 <h2 id="rule-16---anonymous-judging">Rule 16 - Anonymous judging</h2>
@@ -842,7 +850,7 @@ the IOCCC judges only</strong>”, in their respective man pages.</p>
 toolkit</a> command lines that confirm
 to the command’s <code>-h</code> “<em>print help message</em>”, again notwithstanding the options
 for testing and the IOCCC judges.</p>
-<p>The <code>prog.c</code> file <strong>MUST</strong> pass the <a href="rules.html#rule-2---size">Rule 2 - Size</a>
+<p>The <code>prog.c</code> file <strong>MUST</strong> pass the <a href="rules.html#rule2-size">Rule 2 - Size</a>
 checks performed by <code>iocccsize(1)</code>.</p>
 <p>The <code>.auth.json</code> and <code>.info.json</code> files <strong>MUST</strong> be compatible with what
 <code>mkiocccentry(1)</code> generates.</p>
@@ -865,14 +873,14 @@ FAQ on “<a href="../faq.html#mkiocccentry">What is the mkiocccentry tool, how
 <p>This 19th rule, while prime, is reserved for future abuse 😁.
 Additional rules, both humorous and otherwise, may be added
 below this rule in future contests.</p>
-<p>See <a href="rules.html#rule6-free">Rule 6 - Free Rule</a>.</p>
+<p>See <a href="rules.html#rule6-free-rule">Rule 6 - Free Rule</a>.</p>
 <h2 id="further-reading">Further Reading</h2>
 <p>Please read the <a href="guidelines.html">Guidelines</a> next for further commentary on these rules.</p>
 <p>Read the
 <a href="https://www.ioccc.org/quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>
 for an overview of how to enter the contest.</p>
 <p>See also the <a href="../faq.html">FAQ</a>.</p>
-<p>And now <a href="guidelines.html#fun">for something completely different</a></p>
+<p>And now <a href="guidelines.html#fun">for something completely different</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
@@ -10,9 +10,9 @@ These rules are a **TENTATIVE proposal** for the next IOCCC
 and are **likely be to be updated** before the next IOCCC.

 See our
-FAQ on "[rules, guidelines and tools feedback](../faq.html#feedback)"
+FAQ on "[rules, guidelines, tools feedback](../faq.html#feedback)"
 as well as our
-FAQ on "[asking questions](../faq.html#question)"
+FAQ on "[about asking questions](../faq.html#question)"
 about these rules. You might also find the FAQ in general useful, especially the
 FAQ on "[how to enter the IOCCC](../quick-start.html#enter)".

@@ -78,10 +78,12 @@ Your submission **MUST** be a C program that does NOT `#include` data files.
 <div id="rule2">
 <div id="rule2-size-restrictions">
 <div id="rule2-size">
+<div id="rule-2---size">
 ## Rule 2 - Size restrictions
 </div>
 </div>
 </div>
+</div>

 `Rule 2` requires that your submission satisfy **BOTH**
 [Rule 2a &lpar;Gross Size&rpar;](rules.html#rule2a)
@@ -98,9 +100,11 @@ See the [Guidelines for Rule 2 - Size restrictions](guidelines.html#guideline-2-

 <div id="rule2a">
 <div id="rule2a-gross-size">
+<div id="rule-2a-gross-size">
 ### Rule 2a - Gross Size
 </div>
 </div>
+</div>

 The overall maximum size of your `prog.c` program source **MUST NOT**
 exceed **4993** bytes.
@@ -113,9 +117,11 @@ See [Entering the IOCCC: the bare minimum you need to know](../quick-start.html#

 <div id="rule2b">
 <div id="rule2b-net-size">
+<div id="rule-2b-net-size">
 ### Rule 2b - Net Size
 </div>
 </div>
+</div>

 When the filename of your program source (i.e., `prog.c`) is given as a
 command line argument to the latest version of the official IOCCC size
@@ -234,7 +240,8 @@ FAQ on "[What permissions may my files be and what if I need different permissio

 See the [Guidelines on the mkiocccentry toolkit](guidelines.html#mkiocccentry_toolkit).

-See the [Guidelines on the Makefile](guidelines.html#makefile).
+See the
+FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)".


 <div id="rule5">
@@ -321,9 +328,9 @@ Do **NOT** register more than one account!

 See
 [Rule 3 - Registering for the IOCCC](rules.html#rule3-register),
-[Rule 15 - GNU Makefile compatibility](rules.html#rule15-gnu-makefile),
+[Rule 15 - GNU Makefile](rules.html#rule15-gnu-makefile),
 and
-[Rule 17 - Use mkiocccentry](rules.html#rule-17-mkiocccentry).
+[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry).


 <div id="rule9">
@@ -344,7 +351,7 @@ the make command.
 **NOTE**: it is better and more portable to **NOT** modify the `${CC}` variable
 in the Makefile.

-See [Rule 15 - GNU Makefile compatibility](rules.html#rule-15---building).
+See [Rule 15 - GNU Makefile](rules.html#rule15-gnu-makefile).


 <div id="rule10">
@@ -420,8 +427,8 @@ or `remarks.md` files, but instead end lines with Unix newline (line-feed,
 CTRL+J, `\n`).

 You are permitted, in order to try and squeeze your `prog.c` under a
-[Rule 2a Gross Size](rules.html#rule-2a-gross-size) and/or
-[Rule 2b Net Size](rules.html#rule-2b-net-size)
+[Rule 2a Gross Size](rules.html#rule2a-gross-size) and/or
+[Rule 2b Net Size](rules.html#rule2b-net-size)
 limits, to **NOT** end source with a newline. If you
 need to do this, please document that in your `remarks.md` file and if
 your compiler complains about this, document this too and update your
@@ -480,9 +487,10 @@ variable.

 See [Rule 4 - Required files](rules.html#rule4-required-files).

-See FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)".
+See
+FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)".

-See [Guidelines for Rule 15 - GNU Makefile compatibility](guidelines.html#guideline-15---building).
+See [Guidelines for Rule 15 - GNU Makefile](guidelines.html#guideline-15---building).


 <div id="rule16">
@@ -549,7 +557,7 @@ toolkit](https://github.com/ioccc-src/mkiocccentry) command lines that confirm
 to the command's `-h` "_print help message_", again notwithstanding the options
 for testing and the IOCCC judges.

-The `prog.c` file **MUST** pass the [Rule 2 - Size](rules.html#rule-2---size)
+The `prog.c` file **MUST** pass the [Rule 2 - Size](rules.html#rule2-size)
 checks performed by `iocccsize(1)`.

 The `.auth.json` and `.info.json` files **MUST** be compatible with what
@@ -586,7 +594,7 @@ This 19th rule, while prime, is reserved for future abuse 😁.
 Additional rules, both humorous and otherwise, may be added
 below this rule in future contests.

-See [Rule 6 - Free Rule](rules.html#rule6-free).
+See [Rule 6 - Free Rule](rules.html#rule6-free-rule).


 ## Further Reading
@@ -599,7 +607,7 @@ for an overview of how to enter the contest.

 See also the [FAQ](../faq.html).

-And now [for something completely different](guidelines.html#fun)
+And now [for something completely different](guidelines.html#fun).

 Consider joining the [IOCCC Discord Server](https://discord.com/invite/Wa42Qujwnw)
 for discussions about The Rules, questions for the Judges, and `C` in general.
@@ -452,7 +452,7 @@
 <!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->

 <!-- BEFORE: 1st line of markdown file: next/submit.md -->
-<p>Use mkiocccentry to rebuild# How to upload your submission to the IOCCC</p>
+<h1 id="how-to-upload-your-submission-to-the-ioccc">How to upload your submission to the IOCCC</h1>
 <p><strong>IMPORTANT NOTE</strong>: The <a href="https://submit.ioccc.org">IOCCC submit server</a>
 is only ready for submissions
 <strong>ONLY WHEN THE CONTEST IS <a href="../faq.html#open">open</a></strong>.</p>
@@ -518,7 +518,7 @@ the file selection step.</p>
 <li>the status of the submission</li>
 <li>the filename, which will be in the correct format, assuming you used
 <code>mkiocccentry(1)</code> which is <strong>HIGHLY</strong> recommended so that you do not break
-<a href="rules.html#rule-17---packaging">Rule 17 - Packaging</a>!</li>
+<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>!</li>
 <li>the file length, which <code>txzchk(1)</code> will also verify (the file itself and the
 tarball listing).</li>
 <li>the upload date.</li>
@@ -576,7 +576,7 @@ To see any status updates, you should logout and log back in later.</p>
 <p>… or <strong>ANY</strong> other error then you <strong>MUST FIX</strong> your submission, repackage your
 tarball with <code>mkiocccentry</code> and upload to the same slot again! If you do not fix
 this your submission <strong>WILL BE REJECTED</strong> for violating
-<a href="rules.html#rule-17---packaging">Rule 17 - Packaging</a>!</p>
+<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>!</p>
 <p>If the format test went well, then you will see:</p>
 <blockquote>
 <p><strong>Status: submit file received by the IOCCC judges. Passed both txzchk and chksubmit tests.</strong></p>
@@ -586,7 +586,7 @@ rules or that everything is OK once the tarball is extracted; it simply means
 the tests performed by the tools passed. If you find a flaw in a tool and
 abuse it and the tests pass then you stand a significant chance of having your
 submission rejected for violating
-<a href="rules.html#rule-17---packaging">Rule 17 - Packaging</a>,
+<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>,
 even if the tests passed.</p>
 <p>For details on <code>txzchk</code>, see the
 FAQ on “<a href="../faq.html#txzchk">txzchk</a>”.</p>
@@ -1,4 +1,4 @@
-Use mkiocccentry to rebuild# How to upload your submission to the IOCCC
+# How to upload your submission to the IOCCC

 **IMPORTANT NOTE**: The [IOCCC submit server](https://submit.ioccc.org)
 is only ready for submissions
@@ -87,7 +87,7 @@ And in the slot it will give you important details like:
 - the status of the submission
 - the filename, which will be in the correct format, assuming you used
 `mkiocccentry(1)` which is **HIGHLY** recommended so that you do not break
-[Rule 17 - Packaging](rules.html#rule-17---packaging)!
+[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry)!
 - the file length, which `txzchk(1)` will also verify (the file itself and the
 tarball listing).
 - the upload date.
@@ -158,7 +158,7 @@ Or:
 ... or **ANY** other error then you **MUST FIX** your submission, repackage your
 tarball with `mkiocccentry` and upload to the same slot again! If you do not fix
 this your submission **WILL BE REJECTED** for violating
-[Rule 17 - Packaging](rules.html#rule-17---packaging)!
+[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry)!

 If the format test went well, then you will see:

@@ -169,7 +169,7 @@ rules or that everything is OK once the tarball is extracted; it simply means
 the tests performed by the tools passed. If you find a flaw in a tool and
 abuse it and the tests pass then you stand a significant chance of having your
 submission rejected for violating
-[Rule 17 - Packaging](rules.html#rule-17---packaging),
+[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry),
 even if the tests passed.

 For details on `txzchk`, see the