add missing news about the contest status change

Author: lcn2

news.html

@@ -432,7 +432,12 @@ <h3 id="please-follow-the-ioccc-on-mastodon">Please follow the <a href="https://
 FAQ on “<a href="faq.html#try_mastodon">Mastodon</a>”
 for more information on Mastodon.</p>
 <h1 id="news">News</h1>
-<h2 id="section">2024-12-28</h2>
+<h2 id="section">2024-12-30</h2>
+<p>The IOCCC <a href="next/rules.html#rule13">Rule 13</a> no longer discourages the
+use of UTF-8 in C source. Since the days of <code>-std=gnu17</code> compilers,
+UTF-8 characters do not impose a compiler problem. The related guideline
+states that “Rule 13 no longer discourages the use of UTF-8 +characters in C code”.</p>
+<h2 id="section-1">2024-12-28</h2>
 <h3 id="good-news-everyone--">Good News Everyone! :-)</h3>
 <p>After a 4 year effort by a <a href="thanks-for-help.html">number of people</a>,
 with over 6168+ commits, the <strong>Great Fork Merge</strong> has been completed
@@ -455,10 +460,12 @@ <h3 id="good-news-everyone--">Good News Everyone! :-)</h3>
 <h3 id="ioccc28-is-starting">IOCCC28 is starting!</h3>
 <p>The IOCCC28, the <a href="faq.html#ioccc_start">40th anniversary of the IOCCC</a> is now
 scheduled to run from <strong>2024-12-29 23:58:13.213455 UTC</strong> to <strong>2025-04-01 23:29:31.374143 UTC</strong>!!!.</p>
+<p>The <a href="status.html">contest status</a> as been changed to “<strong>pending</strong>”
+and <a href="status.json">status.json</a> has been updated to reflect this new status.</p>
 <p>Proposed and tentative <a href="next/rules.html">IOCCC rules</a> and <a href="next/guidelines.html">IOCCC guidelines</a>
 have been released.</p>
 <p>See <a href="faq.html#enter_questions">FAQ Section 0</a> for more information on how to enter.</p>
-<h2 id="section-1">2024-06-08</h2>
+<h2 id="section-2">2024-06-08</h2>
 <p>We continue to make good progress on the
 <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
@@ -488,7 +495,7 @@ <h2 id="section-1">2024-06-08</h2>
 entries that have to be added at the end, like the example below.</p>
 <p>Once the <em>submit server</em> server is ready another FAQ will be added and that
 entry can be looked at alone.</p>
-<h2 id="section-2">2024-05-30</h2>
+<h2 id="section-3">2024-05-30</h2>
 <p>A number of issues from minor fixes have been applied to the
 <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
@@ -523,7 +530,7 @@ <h2 id="section-2">2024-05-30</h2>
 This will speed up the start date of IOCCC28.</p>
 <p>It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the
 IOCCC.</p>
-<h2 id="section-3">2024-04-30</h2>
+<h2 id="section-4">2024-04-30</h2>
 <p>The website now is viewing by mobile devices such as cell phones
 and tablets. Devices with a screen resolution 1024 pixels and
 narrower are given a <em>hamburger-style</em> menu icon in place of
@@ -545,7 +552,7 @@ <h2 id="section-3">2024-04-30</h2>
 warnings, nor info** messages, changes involving fixing invalid
 links to local files have been corrected, and changes involving the
 <em>topbar</em> are now HTML 5 conforming.</p>
-<h2 id="section-4">2024-04-20</h2>
+<h2 id="section-5">2024-04-20</h2>
 <p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 website has undergone editorial review. Nearly all <a href="years.html">IOCCC winning entries</a>
 compile on modern systems and many have <code>try.sh</code> scripts to help you run them.
@@ -563,10 +570,10 @@ <h2 id="section-4">2024-04-20</h2>
 where the contents of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>.</p>
 <p>Stay tuned!</p>
-<h2 id="section-5">2024-02-29</h2>
+<h2 id="section-6">2024-02-29</h2>
 <p>We continue to make good progress on website. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 4600 changes to date!</p>
 <p>All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the <a href="bin/index.html">bin</a> directory.</p>
-<h2 id="section-6">2023-05-22</h2>
+<h2 id="section-7">2023-05-22</h2>
 <p>We have been busy preparing for an important / significant update to this website. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 2645 changes to date.</p>
 <p>While you are free to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>,
 please <strong>do not link to it</strong> as this repo and related website will disappear once the main
@@ -622,7 +629,7 @@ <h2 id="section-6">2023-05-22</h2>
 The <strong>IOCCCMOCK</strong> will us to beta-test the new IOCCC process without putting the hard work of those
 who submit real IOCCC entries at risk.</p>
 <p>Stay tuned!</p>
-<h2 id="section-7">2023-01-30</h2>
+<h2 id="section-8">2023-01-30</h2>
 <p>We added to the
 <a href="status.json">status.json</a> page,
 a <em>“status_date”</em> JSON member whose value is the date
@@ -634,7 +641,7 @@ <h2 id="section-7">2023-01-30</h2>
 of the most recent news item.</p>
 <pre><code>    &quot;status_date&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;,
     &quot;latest_news&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;</code></pre>
-<h2 id="section-8">2022-12-18</h2>
+<h2 id="section-9">2022-12-18</h2>
 <p>As per the suggestion of <a href="https://fosstodon.org/@Virtaava@home.social">Toni Mikkola
 (<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social&amp;rpar">@home.social&amp;rpar</span>;</a>
 we now maintain a <a href="status.json">status.json</a> page on this website.</p>
@@ -652,7 +659,7 @@ <h2 id="section-8">2022-12-18</h2>
 Instead you will have to rely on the additional JSON information
 and/or read the <a href="#news">IOCCC news</a>,
 and/or follow us on Mastodon via <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
-<h2 id="section-9">2022-11-29</h2>
+<h2 id="section-10">2022-11-29</h2>
 <p>We are planning to abandon our
 <a href="https://twitter.com/ioccc">IOCCC Twitter feed</a>
 in favor of our new <a href="https://fosstodon.org/@ioccc">IOCCC Mastodon</a> feed.</p>
@@ -687,7 +694,7 @@ <h2 id="section-9">2022-11-29</h2>
 and those who voluntarily
 <a href="https://hub.fosstodon.org/support/">support</a> the cost of their server.</p>
 <p>Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!</p>
-<h2 id="section-10">2022-11-19</h2>
+<h2 id="section-11">2022-11-19</h2>
 <p>Source code has been released for version <strong>0.8.1 2022-11-19</strong> of the
 <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>,
 a GitHub repo that includes the official iocccsize tool,
@@ -699,13 +706,13 @@ <h2 id="section-10">2022-11-19</h2>
 judges will go through the motions (without judging the content) of an IOCCC:
 testing the above mentioned tools and testing the submit server.</p>
 <p>We are working on complete rebuild of this website as well.</p>
-<h2 id="section-11">2022-01-15</h2>
+<h2 id="section-12">2022-01-15</h2>
 <p>Source code has been released for version <strong>0.24 2022-01-15</strong> of the
 <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>,
 a tool that is based on, and is containing, the official iocccsize tool,
 will form a compressed tarball that a registered IOCCC contestant
 will upload to the submit server (when the contest is open of course).</p>
-<h2 id="section-12">2021-12-27</h2>
+<h2 id="section-13">2021-12-27</h2>
 <p><a href="judges.html">The Judges</a>
 are continuing to work on re-tooling how we run the IOCCC.
 We are writing tools under various repositories our
@@ -714,7 +721,7 @@ <h2 id="section-12">2021-12-27</h2>
 Sorry for the delay, but we think you will appreciate the re-tooling
 when it is completed.
 Stay tuned!</p>
-<h2 id="section-13">2021-10-21</h2>
+<h2 id="section-14">2021-10-21</h2>
 <p><a href="judges.html">The Judges</a>
 are re-tooling how we run the IOCCC.
 Our goal is to build a smoother, more rapid process centered around

news.md

@@ -14,6 +14,14 @@ for more information on Mastodon.
 </div>
 
 
+## 2024-12-30
+
+The IOCCC [Rule 13](next/rules.html#rule13) no longer discourages the
+use of UTF-8 in C source.  Since the days of `-std=gnu17` compilers,
+UTF-8 characters do not impose a compiler problem.  The related guideline
+states that "Rule 13 no longer discourages the use of UTF-8 +characters in C code".
+
+
 ## 2024-12-28
 
 ### Good News Everyone! :-)
@@ -45,6 +53,9 @@ or fix [known bugs in IOCCC winning entries](bugs.html).
 The IOCCC28, the [40th anniversary of the IOCCC](faq.html#ioccc_start) is now
 scheduled to run from **2024-12-29 23:58:13.213455 UTC** to **2025-04-01 23:29:31.374143 UTC**!!!.
 
+The [contest status](status.html) as been changed to "**pending**"
+and [status.json](status.json) has been updated to reflect this new status.
+
 Proposed and tentative [IOCCC rules](next/rules.html) and [IOCCC guidelines](next/guidelines.html)
 have been released.
 

next/guidelines.html

@@ -1679,15 +1679,10 @@ <h1 id="our-likes-and-dislikes">OUR LIKES AND DISLIKES:</h1>
 prevent such trailing control-M’s being added.</p>
 <p>One should restrict libcurses to portable features found on BSD
 or Linux curses.</p>
-<p><a href="rules.html#rule13">Rule 13</a> states any C source that fails to compile because of unescaped
-octets with the high bit set (octet value &gt;= 128) <strong>might</strong> be rejected.
-Instead of unescaped octets, you should use or escapes:</p>
-<pre><code>
-              /* 123456789 123456789 123456789 123456 */
-    char *foo = &quot;This string is 36 octets in length \263&quot;;
-          /* This octet requires 4 octets of source ^^^^ */
-    if (strlen(foo) == 36) printf(&quot;foo is 36 octets plus a final NUL\n&quot;);
-    else printf(&quot;This code should not print this message\n&quot;);</code></pre>
+<p class="leftbar">
+<a href="rules.html#rule13">Rule 13</a> no longer discourages the use of UTF-8
+characters in C code.
+</p>
 <p class="leftbar">
 It is a very good idea to, in your <code>remarks.md</code> file, tell us why you
 think your submission is obfuscated. This is particularly true if

next/guidelines.md

@@ -1560,18 +1560,10 @@ prevent such trailing control-M's being added.
 One should restrict libcurses to portable features found on BSD
 or Linux curses.
 
-[Rule 13](rules.html#rule13)  states any C source that fails to compile because of unescaped
-octets with the high bit set (octet value >= 128) **might** be rejected.
-Instead of unescaped octets, you should use \octal or \hex escapes:
-
-``` <!---c-->
-
-              /* 123456789 123456789 123456789 123456 */
-    char *foo = "This string is 36 octets in length \263";
-          /* This octet requires 4 octets of source ^^^^ */
-    if (strlen(foo) == 36) printf("foo is 36 octets plus a final NUL\n");
-    else printf("This code should not print this message\n");
-```
+<p class="leftbar">
+[Rule 13](rules.html#rule13) no longer discourages the use of UTF-8
+characters in C code.
+</p>
 
 <p class="leftbar">
 It is a very good idea to, in your `remarks.md` file, tell us why you

next/rules.html

@@ -462,7 +462,7 @@ <h2 id="ioccc-rules-version">IOCCC Rules version</h2>
 </div>
 <p>Jump to: <a href="#">top</a></p>
 <p class="leftbar">
-These <a href="rules.html">IOCCC rules</a> are version <strong>28.15 2024-12-28</strong>.
+These <a href="rules.html">IOCCC rules</a> are version <strong>28.16 2024-12-29</strong>.
 </p>
 <p class="leftbar">
 The <a href="rules.md" download="rules.md">markdown form of these rules</a>
@@ -852,8 +852,7 @@ <h2 id="rule-12">Rule 12</h2>
 <h2 id="rule-13">Rule 13</h2>
 </div>
 <p class="leftbar">
-Any C source that fails to compile because of unescaped octets with
-the high bit set (octet value &gt;= 128) <strong><em>might</em></strong> be rejected.
+7 out of 13 UTF-8 characters in C code agree that this rule number is lucky enough to be a prime number.
 </p>
 <p>Jump to: <a href="#">top</a></p>
 <div id="rule14">

next/rules.md

@@ -55,7 +55,7 @@ Jump to: [top](#)
 
 
 <p class="leftbar">
-These [IOCCC rules](rules.html) are version **28.15 2024-12-28**.
+These [IOCCC rules](rules.html) are version **28.16 2024-12-29**.
 </p>
 
 <p class="leftbar">
@@ -604,8 +604,7 @@ Jump to: [top](#)
 </div>
 
 <p class="leftbar">
-Any C source that fails to compile because of unescaped octets with
-the high bit set (octet value >= 128) **_might_** be rejected.
+7 out of 13 UTF-8 characters in C code agree that this rule number is lucky enough to be a prime number.
 </p>