add missing news about the contest status change

next/guidelines.html

@@ -1679,15 +1679,10 @@ their entries. In some cases tools have a “Save As” option that will
 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 @@ writing by <a href="../contact.html">contacting the judges</a>.</p>
 </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 @@ their rule abuse is legal, in the <code>remarks.md</code> file.</p>
 <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>