From 25ccb1446166da10d746605d6a88d299e5c31578 Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Sat, 16 Mar 2024 08:34:57 -0700 Subject: [PATCH] Fix regexp in faq.md --- faq.html | 11 ++++++----- faq.md | 9 +++++---- 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/faq.html b/faq.html index 0ced2d660..d927c170a 100644 --- a/faq.html +++ b/faq.html @@ -2319,10 +2319,11 @@ form:

See FAQ 6.6 for information about the contents of these JSON file and how they are used.

Because the author_handle is used to form a JSON -filename, the string must be POSIX safe string. Furthermore, the -author_handle must be an ASCII string that matches this -regexp:

-
^[0-9A-Za-z][0-9A-Za-z_]*$
+filename, the string must be POSIX safe string plus the use of ++ (for technical reasons beyond this answer). In +particular, the author_handle must be an ASCII string that +matches this regexp:

+
^[0-9A-Za-z][0-9A-Za-z._+-]*$"

Default author_handle’s do not have multiple consecutive _ (underscore) characters. Nevertheless, multiple consecutive _ (underscore) characters are allowed. Contest @@ -2814,7 +2815,7 @@ not see who wrote the code.

IOCCC becomes an entry. Only then do the IOCCC judges look into the special JSON file to discover who the author(s) are.

An apology for being inconsistent: In the past, the -IOCCC used the term entry to refer to what is now an +IOCCC used the term entry to refer to what is now a submission. In a number of historical cases, such as old rules and old guidelines, terms such as entry may still be found. Moreover, out of habit, the IOCCC judges sometimes use old names such as diff --git a/faq.md b/faq.md index 147711376..d30ec7b36 100644 --- a/faq.md +++ b/faq.md @@ -2504,11 +2504,12 @@ See [FAQ 6.6](#author_json) for information about the contents of these JSON fil how they are used. Because the `author_handle` is used to form a JSON filename, the string must be -POSIX safe string. Furthermore, the `author_handle` must be an ASCII -string that matches this regexp: +POSIX safe string plus the use of `+` (for technical reasons beyond this +answer). In particular, the `author_handle` must be an ASCII string that +matches this regexp: ```re -^[0-9A-Za-z][0-9A-Za-z_]*$ +^[0-9A-Za-z][0-9A-Za-z._+-]*$" ``` Default `author_handle`'s do not have multiple consecutive `_` (underscore) @@ -3125,7 +3126,7 @@ becomes an _entry_. Only then do the IOCCC judges look into the special JSON file to discover who the _author_(s) are. **An apology for being inconsistent**: In the past, the IOCCC used the term _entry_ to -refer to what is now an _submission_. In a number of historical cases, +refer to what is now a _submission_. In a number of historical cases, such as old rules and old guidelines, terms such as _entry_ may still be found. Moreover, out of habit, the IOCCC judges sometimes use old names such as _entry_ when they should use _submission_. Sorry (tm Canada)! :-)