From c26ad143867167afa9f6969691eab35909285d18 Mon Sep 17 00:00:00 2001
From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com>
Date: Mon, 24 Jun 2024 05:52:21 -0700
Subject: [PATCH] Slight format improvement to rule 2 in guidelines

The '{', '}' and other chars that are referred to are now in code blocks
(surrounded by single quotes) to help make them stand out better. The
single quotes are there as depending on the person's perception (or if
they're tired or ...) the colour difference might not be enough (in fact
it's barely enough for me at this point and others are more colour blind
than I am). The block quote colour is being experimented with still,
too, so that is another reason to have the 's.

Added make gen_next rule to Makefile which builds next/index.html from
next/README.md, next/rules.html from next/rules.md and
next/guidelines.html from next/guidelines.md. The make help rule was
updated for this.
---
 Makefile             | 6 ++++++
 next/guidelines.html | 6 +++---
 next/guidelines.md   | 6 +++---
 3 files changed, 12 insertions(+), 6 deletions(-)

diff --git a/Makefile b/Makefile
index dec2f6c08..e258ec2f3 100644
--- a/Makefile
+++ b/Makefile
@@ -287,6 +287,7 @@ help:
 	@echo 'make gen_other_html	 - build entry HTML files from markdown other than README.md'
 	@echo 'make gen_year_index	 - generate year level index.html files using from README.md files'
 	@echo 'make gen_top_html	 - generate a number of the top level HTML files from markdown'
+	@echo 'make gen_next		 - generate the HTML files in next/'
 	@echo 'make quick_entry_index	 - build winner index.html files that might be out of date'
 	@echo 'make find_missing_links	 - find markdown links to missing local files'
 	@echo
@@ -437,6 +438,11 @@ bugs: ${GEN_TOP_HTML} bugs.md
 	@${GEN_TOP_HTML} bugs
 	@echo "Eh, what's up, doc?"
 
+gen_next: ${GEN_TOP_HTML} next/README.md next/guidelines.md next/rules.md
+	${GEN_TOP_HTML} -v 1 next/README
+	${GEN_TOP_HTML} -v 1 next/guidelines
+	${GEN_TOP_HTML} -v 1 next/rules
+
 # build entry HTML files from markdown other than README.md to index.html
 #
 gen_other_html: ${GEN_OTHER_HTML}
diff --git a/next/guidelines.html b/next/guidelines.html
index 98adba26b..e4281b207 100644
--- a/next/guidelines.html
+++ b/next/guidelines.html
@@ -518,12 +518,12 @@ For example:</p>
 <p>The size tool counts most C reserved words (keyword, secondary,<br>
 and selected preprocessor keywords) as 1. The size tool counts all<br>
 other octets as 1 excluding ASCII whitespace, and excluding any<br>
-‘;’, ‘{’ or ‘}’ followed by ASCII whitespace, and excluding any<br>
-‘;’, ‘{’ or ‘}’ octet immediately before the end of file.</p>
+‘<code>;</code>’, ‘<code>{</code>’ or ‘<code>}</code>’ followed by ASCII whitespace, and excluding any<br>
+‘<code>;</code>’, ‘<code>{</code>’ or ‘<code>}</code>’ octet immediately before the end of file.</p>
 </blockquote>
 <p>ASCII whitespace includes ASCII tab, ASCII space, ASCII newline,
 ASCII formfeed, and ASCII carriage return.</p>
-<p><strong><code>|</code></strong> When ‘;’, ‘{’ or ‘}’ are within a C string, they may still not be
+<p><strong><code>|</code></strong> When ‘<code>;</code>’, ‘<code>{</code>’ or ‘<code>}</code>’ are within a C string, they may still not be
 <strong><code>|</code></strong> counted by the IOCCC size tool. This is a feature, not a bug!</p>
 <p>In cases where the above summary and the algorithm implemented by
 the IOCCC size tool source code conflict, the algorithm implemented
diff --git a/next/guidelines.md b/next/guidelines.md
index ecd4999b6..a062d1291 100644
--- a/next/guidelines.md
+++ b/next/guidelines.md
@@ -190,13 +190,13 @@ The IOCCC size tool, when using the -i option, may be summarized as:
 >   The size tool counts most C reserved words (keyword, secondary,<br>
 >   and selected preprocessor keywords) as 1.  The size tool counts all<br>
 >   other octets as 1 excluding ASCII whitespace, and excluding any<br>
->   ';', '{' or '}' followed by ASCII whitespace, and excluding any<br>
->   ';', '{' or '}' octet immediately before the end of file.
+>   '`;`', '`{`' or '`}`' followed by ASCII whitespace, and excluding any<br>
+>   '`;`', '`{`' or '`}`' octet immediately before the end of file.
 
 ASCII whitespace includes ASCII tab, ASCII space, ASCII newline,
 ASCII formfeed, and ASCII carriage return.
 
-**`|`**   When ';', '{' or '}' are within a C string, they may still not be
+**`|`**   When '`;`', '`{`' or '`}`' are within a C string, they may still not be
 **`|`**   counted by the IOCCC size tool.  This is a feature, not a bug!
 
 In cases where the above summary and the algorithm implemented by