From 3011f327577e0dcf2adc08cd9c5bed6a424d708b Mon Sep 17 00:00:00 2001 From: Landon Curt Noll Date: Thu, 27 Nov 2025 08:01:25 -0800 Subject: [PATCH] render makrdown and rules, update sitemap --- markdown.html | 34 +++++++++++++++++----------------- next/rules.html | 12 ++++++------ sitemap.xml | 12 ++++++------ 3 files changed, 29 insertions(+), 29 deletions(-) diff --git a/markdown.html b/markdown.html index 4a4abf315..2dbc9961b 100644 --- a/markdown.html +++ b/markdown.html @@ -491,7 +491,9 @@ not apply to other markdown files), PLEASE start at level three

Replace <a name="anchor_name"></a> construct.

❌ <a name="old_way">...</a>
-✔️ <span id="new_way">...</span>
+✔️ <div id="new_way">...</div> +✔️ +✔️ ### Section title @@ -533,7 +535,7 @@ not apply to other markdown files), PLEASE start at level three 
❌ echo "This code block is NOT indented"

We request that you indent the code block by multiples of four (4) ASCII SPACES, never TAB (␉):

-
✔️     echo "This code block is indented by multiples of 4 spaces"
+
✔️      echo "This code block is indented by multiples of 4 spaces"
 
 ✔️     # The top level starts with a 4 ASCII space indent.
 ✔️     #
@@ -564,19 +566,19 @@ ASCII SPACES.

 ❌ ␉Please do **NOT**␉use ASCII tabs␉in markdown files.
 ❌ ␉␉Please do **NOT** indent markdown with ASCII tabs.
 
-❌ ␉We       don't␉mind␉tabs␉in␉general,
+❌ ␉We␉don't␉mind␉tabs␉in␉general,
 ❌ ␉We just ask that you NOT use them in markdown files.
 ```

 
And to clarify, we are only talking about markdown files, not C code or
 any other non-markdown content:

-
✔️       printf("It is fine␉to␉use tabs in Obfuscated C code.\n");
-✔️               /*␉if␉you␉wish    */
+
✔️ ␉printf("It is fine␉to␉use tabs in Obfuscated C code.\n");
+✔️ ␉␉/*␉if␉you␉wish    */
 
-✔️       // 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.

-
NOTE: Again, you are perfectly welcome to use ASCII tab characters
-in your C code and other non-markdown files. We simply ask that
-you do NOT use any ASCII TAB (␉) characters in markdown files.

+✔️ ␉// 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.

+
NOTE: Again, you are perfectly welcome to use ASCII TAB (␉) characters
+in your C code and other non-markdown files. We simply ask that you do
+NOT use any ASCII TAB (␉) characters in markdown files.

 

 
 

@@ -629,9 +631,8 @@ block as this makes it easier to detect when markdown code blocks are
 
 
 
Do not add trailing slash to void HTML tags.

-
Please do NOT use a trailing slash on
-void HTML elements.

-
See also this note on trailing slashes in void-element start tags.

+
Please do NOT use a trailing slash on void HTML elements. See also
+this note on trailing slashes in void-element start tags.

 
The trailing slash on void HTML elements has no effect and interacts
 badly with unquoted attribute values.

 
❌ <br/>
@@ -672,7 +673,7 @@ a markdown line with a trailing backslash (\). Instead use a traili
 
 ✔️ `This is OK\`

 
Doing it this way will prevent pandoc(1) from generating deprecated
-HTML elements such as <br />.

+HTML elements, such as <br />.

 

 
 

@@ -700,7 +701,6 @@ a line with 3 or more dashes (“-”s).

 
Such markdown causes pandoc(1) to generate <hr />. The <hr /> has
 no effect in standard HTML 5 and interacts badly with unquoted attribute
 values.

-
If a horizontal line is really needed, use:

 
❌ * * *
 ❌ - - -
 ❌ ---
@@ -744,8 +744,8 @@ go for when it is bold and italic.

 ❌ ***this text is bold italic***
 ✔️ **_this text is bold italic_**
 ✔️ _**this text is bold italic**_

-
BTW: the astute reader might notice that some cases of * for
-italic might have slipped through. We do ask you, however, to please
+
BTW: the astute reader might notice that some cases of * for italic
+might have slipped through. We do ask you, however, to please
 observe this rule, as best you can.
 

 
diff --git a/next/rules.html b/next/rules.html
index f53a4100e..d326d1fa0 100644
--- a/next/rules.html
+++ b/next/rules.html
@@ -476,7 +476,7 @@ app from time to time to view IOCCC mastodon updates.

 
29th International Obfuscated C Code Contest Official Rules

 
Copyright © 2025 Leonid A. Broukhis and Landon Curt Noll.

 
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 MUST receive prior permission in
 writing by contacting the judges.

 
Rules Version

@@ -638,13 +638,13 @@ and
 
Rule 9 - No hands

 
 
Entries requiring human interaction to be initially compiled are NOT
-permitted. However, see the guidelines. Each entry MUST automated the
-its build process using bash, gmake, gcc, clang, under a
+permitted. However, see the guidelines. Each entry MUST automate the
+build process using bash, gmake, gcc, clang, under a
 SUS environment.

 
Note references to gmake can be any GNU Make compatible tool.

 
See Rule 15 - Building.

 

-
Rule 10 - Privileges

+
Rule 10 - Privileges

 

 
Programs that require special privileges (setuid(2), setgid(2),
 super-user, special owner, special group, etc.) are HIGHLY DISCOURAGED.
@@ -712,7 +712,7 @@ didn’t previously win, then you are encouraged to mention this in your
 
Rule 15 - Building

 
 
The Makefile MUST adhere to GNU Makefile syntax. Its recommended
-that you copy and rename the Makefile.example as template. The primary
+that you copy and rename the Makefile.example as a template. The primary
 target of the Makefile MUST be prog and the source file is prog.c.
 The C compiler and preprocessor MUST be invoked using ${CC} and ${CPP}
 macros respectively.

@@ -796,7 +796,7 @@ for an overview of how to enter the contest.

 
See also the FAQ.

 
Consider joining the IOCCC Discord Server
 for discussions about The Rules, questions for the Judges, and C in general.

-
Leonid A. Broukhis
+
Leonid A. Broukhis

 chongo (Landon Curt Noll) /\cc/\
 

 
diff --git a/sitemap.xml b/sitemap.xml
index 7fbedb885..cc515e541 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -16810,11 +16810,11 @@
 
 
     https://www.ioccc.org/markdown.html
-    2025-11-27T07:21:50+00:00
+    2025-11-27T15:59:15+00:00
 
 
     https://www.ioccc.org/markdown.md
-    2025-11-27T07:21:43+00:00
+    2025-11-27T15:58:56+00:00
 
 
     https://www.ioccc.org/news.html
@@ -16826,11 +16826,11 @@
 
 
     https://www.ioccc.org/next/guidelines.html
-    2025-11-27T07:11:14+00:00
+    2025-11-27T15:58:32+00:00
 
 
     https://www.ioccc.org/next/guidelines.md
-    2025-11-27T07:11:14+00:00
+    2025-11-27T15:58:32+00:00
 
 
     https://www.ioccc.org/next/index.html
@@ -16870,11 +16870,11 @@
 
 
     https://www.ioccc.org/next/rules.html
-    2025-11-27T07:11:14+00:00
+    2025-11-27T15:59:14+00:00
 
 
     https://www.ioccc.org/next/rules.md
-    2025-11-27T07:11:14+00:00
+    2025-11-27T15:58:56+00:00
 
 
     https://www.ioccc.org/next/submit.html