From 6c49bc8955311934ea3559f32041884c73bbe1cf Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Sat, 29 Nov 2025 12:03:55 -0800 Subject: [PATCH] Various fixes and updates The links to rules should all be good. This includes in news.html, quick-start.html, next/submit.html, 2024/index.html (it had been modified to refer to next/rules.html instead of 2024/rules.html) as well as the guidelines and rules themselves (under next/). Various typo fixes. I'm afraid there are likely others but I must let others deal with that as I am out of time. Removed FAQ about mastodon push notifications. When I added the FAQ about push notifications for mastodon I was incorrect. The web browser interface suggests it but I never got a push notification even before Apple broke them. There seems to be no way at this time to get them. I note that there was a screenshot in the FAQ but this file still is in the repo possibly. I regenerated the html files but it's possible I forgot to do one at the last minute. --- 2024/README.md | 6 +- 2024/index.html | 8 +- faq.html | 85 +-- faq.md | 85 +-- news.html | 4 +- news.md | 4 +- next/guidelines.html | 1321 +-------------------------------- next/guidelines.md | 1692 +----------------------------------------- next/rules.html | 34 +- next/rules.md | 34 +- next/submit.html | 8 +- next/submit.md | 8 +- quick-start.html | 6 +- quick-start.md | 6 +- 14 files changed, 161 insertions(+), 3140 deletions(-) diff --git a/2024/README.md b/2024/README.md index 6a128c458..da448866c 100644 --- a/2024/README.md +++ b/2024/README.md @@ -77,7 +77,7 @@ become more skilled in the programming in the C language. We were pleased to observe that while the [IOCCC size limit](../faq.html#size_rule_history) increased by about 21%, we received many submissions that were well under the new -[Rule 2 Size](../next/rules.html#rule-2-size) including a fair number of quality +[Rule 2](rules.html#rule2) including a fair number of quality small and medium sized submissions. Half of the **IOCCC28 winners** were less than _2/3 of the size limit_, and 10 of the **IOCCC28 winners** were less than _1/2 of the size limit_! @@ -85,10 +85,10 @@ _1/2 of the size limit_! **IMPORTANT NOTE**: The [IOCCC size limit](../faq.html#size_rule_history) increase for **IOCCC28** was the first size increase in over 10 years. Given the quality of submissions we received that were well under the limit, we do **NOT** expect to change the -[Rule 2 Size](../next/rules.html#rule-2-size) for **at least another 10 years** (and likely longer). +[Rule 2](rules.html#rule2) for **at least another 10 years** (and likely longer). **IMPORTANT HINT**: Only 3 of the 23 **IOCCC28 winners** came close to the [Rule -2 Size](../next/rules.html#rule-2-size). Large code size isn't everything. :-) +2](rules.html#rule2). Large code size isn't everything. :-) Those submitting to future contents should **take a careful note** of that fact. diff --git a/2024/index.html b/2024/index.html index b41981ca2..131505802 100644 --- a/2024/index.html +++ b/2024/index.html @@ -513,16 +513,16 @@ become more skilled in the programming in the C language.

Code size and Rule 2

We were pleased to observe that while the IOCCC size limit increased by about 21%, we received many submissions that were well under the new -Rule 2 Size including a fair number of quality +Rule 2 including a fair number of quality small and medium sized submissions. Half of the IOCCC28 winners were less than 2/3 of the size limit, and 10 of the IOCCC28 winners were less than 1/2 of the size limit!

IMPORTANT NOTE: The IOCCC size limit increase for IOCCC28 was the first size increase in over 10 years. Given the quality of submissions we received that were well under the limit, we do NOT expect to change the -Rule 2 Size for at least another 10 years (and likely longer).

-

IMPORTANT HINT: Only 3 of the 23 IOCCC28 winners came close to the Rule -2 Size. Large code size isn’t everything. :-) +Rule 2 for at least another 10 years (and likely longer).

+

IMPORTANT HINT: Only 3 of the 23 IOCCC28 winners came close to the Rule +2. Large code size isn’t everything. :-) Those submitting to future contents should take a careful note of that fact.

Rules and Guidelines for this contest

Here are the final versions of the IOCCC rules and guidelines that were in diff --git a/faq.html b/faq.html index 1f9fc8ef2..9342f0d78 100644 --- a/faq.html +++ b/faq.html @@ -493,7 +493,7 @@

  • Q 2.1: How can I comment or make a suggestion on IOCCC rules, guidelines and tools?
  • Q 2.2: Are there any compiler warnings that I should not worry about in my submissions?
  • Q 2.3: What types of entries have been frequently submitted to the IOCCC?
    • -
  • Q 2.4: How did an entry win the IOCCC that breaks Rule 2 - Size?
    • +
  • Q 2.4: How did an entry win the IOCCC that breaks Rule 2 - Size Limit?
  • Q 2.5: How many submissions do the judges receive for a given IOCCC?
  • Q 2.6: How much time does it take to judge the contest?
  • Q 2.7: How many judging rounds do you have?
    • @@ -590,10 +590,7 @@
  • Q 10.3: What is the purpose of the .top, .allyear, .year and .path files?
  • Q 10.4: What is the current meaning of the IOCCC terms Author, Entry, and Submission?
  • Q 10.5: Am I allowed to use IOCCC content?
    • -
  • Q 10.6: What is Mastodon and why does the IOCCC use it? -
    • +
  • Q 10.6: What is Mastodon and why does the IOCCC use it?
  • Q 10.7: How do I set certain tabstops for viewing source code in vi(m)?
  • Q 10.8: How do the menus on the website work and what can I do if they don’t work?
  • Q 10.9: How do I find more information about a winning author of an entry?
    • @@ -986,7 +983,8 @@ and itself.

    Do remember that if your submission requires different filenames, then you MUST make a COPY of them in your Makefile. See also -Rule 5 - Integrity.

    +Rule 5 - Do NOT modify submitted files or filenames or parent +directories.

    Jump to: top

    @@ -1328,10 +1326,11 @@ modes, it also verifies them after the fact and if they are not correct it is an error.

    If you do need different permissions, then see the FAQ on “file permissions”. Also keep in mind -Rule 4 - Files, -Rule 5 - Integrity, +Rule 4 - Required files, +Rule 5 - Do NOT modify submitted files or filenames or parent +directories, and -Rule 16 - Anonymous.

    +Rule 16 - Anonymous judging.

    The txzchk(1) tool will also verify file/directory permissions (and many other things) for you, and so will chksubmit(1) (along with other checks on files and directories in your submission directory, including the two required JSON files, @@ -1344,7 +1343,7 @@ page.

    will run fnamchk(1) as part of its algorithm. If you use mkiocccentry(1) there should be no problem but if you were to package things manually it is possible there could be a problem and this poses a big risk of violating -Rule 4 - Files +Rule 4 - Required files or Rule 17 - Use mkiocccentry.

    The fnamchk(1), which txzchk(1) executes, will verify that the @@ -1353,7 +1352,7 @@ mismatch in what is in the tarball and the name, txzchk(1) will fla discrepancy as an error and exit with non-zero.

    These checks MUST PASS. If they do not you stand a significant chance of having your submission rejected for violating -Rule 4 - Files +Rule 4 - Required files or Rule 17 - Use mkiocccentry.

    @@ -1385,9 +1384,9 @@ The mkiocccentry(1) tool uses the v7 format. For instance you might 
        tar --format=v7 -cJf foo.txz directory

    IMPORTANT: where -Rule 4 - Files, +Rule 4 - Required files, and -Rule 17 - Use mkiocccentry. +Rule 17 - Use mkiocccentry and the tools from the latest release of the mkiocccentry repo conflict, the IOCCC judges will use their best judgment which @@ -1422,7 +1421,7 @@ page, for help here and also read our FAQ on “mkiocccentry repo bugs”.

    At the risk of stating the obvious: submissions that violate -Rule 4 - Files, +Rule 4 - Required files, or Rule 17 - Use mkiocccentry WILL BE REJECTED, so BE SURE to use the latest release of the @@ -1903,7 +1902,7 @@ of the same theme.

    Jump to: top

    -

    Q 2.4: How did an entry win the IOCCC that breaks Rule 2 - Size?

    +

    Q 2.4: How did an entry win the IOCCC that breaks Rule 2 - Size restrictions?

    As entries have been fixed it is entirely possible that some of the entries no @@ -2120,7 +2119,7 @@ two JSON files, .auth.json and .info.json as well as t .info.json manifest. (Okay there is an option to skip files but this is for the judges ONLY; use of this option to validate your submission puts you at a great risk of violating -Rule 4 - Files, +Rule 4 - Required files, or Rule 17 - Use mkiocccentry!).

    As an example, if your submission directory is @@ -2142,7 +2141,7 @@ FAQ on “.auth.json” and the FAQ on “.info.json” as well as -Rule 4 - Files, +Rule 4 - Required files, and Rule 17 - Use mkiocccentry for more information.

    @@ -2424,7 +2423,7 @@ will use it on the submission directory as part of the judging process.

    is reported invalid by chksubmit(1), or if your submission directory is reported invalid by chksubmit(1), your submission will almost certainly be rejected for violating the Rules and in particular -Rule 4 - Files, +Rule 4 - Required files, and Rule 17 - Use mkiocccentry.

    An obvious example where chksubmit(1) would fail to validate .auth.json is if @@ -2435,7 +2434,7 @@ out of range (see above for list). Two more examples would be if a field is missing or if an unknown filed is in the file. In these cases (and any others that must be established as valid by chksubmit(1)) your submission would be rejected for violating -Rule 4 - Files, +Rule 4 - Required files, and Rule 17 - Use mkiocccentry and in particular @@ -2608,17 +2607,17 @@ validate your filename, or if you have the wrong directory name in the tarball, this will be flaggd.

  • rule_2a_size (number)

    IMPORTANT: if this violates Rule 2a you stand a great chance of having your submission rejected for violating the Rules!

  • rule_2b_size (number)

    IMPORTANT: if this violates -Rule 2b Next Size +Rule 2b Net Size you stand a great chance of having your submission rejected for violating the Rules!

    • @@ -2629,11 +2628,11 @@ chance of having your submission rejected for violating the

  • rule_2a_override (boolean)

    IMPORTANT: if the -Rule 2a Gross Size +Rule 2a - Gross Size calculated size is NOT violated but this is true then you stand a good chance of having your submission rejected for violating @@ -2641,43 +2640,27 @@ submission rejected for violating

  • rule_2a_mismatch (boolean)

  • rule_2b_override (boolean)

    IMPORTANT: if the -Rule 2b Next Size +Rule 2b - Net Size calculated size is NOT violated but this is true then you stand a good chance of having your submission rejected for violating Rule 17 - Use mkiocccentry.

    • -

  • highbit_warning (boolean)

    -
    • -

  • nul_warning (boolean)

    -

  • trigraph_warning (boolean)

    • -

  • wordbuf_warning (boolean)

    -

  • ungetc_warning (boolean)

    • Rule 2 requires that your submission satisfy BOTH Rule 2a (Gross Size) and @@ -516,9 +518,11 @@ During development this can be checked using iocccsize(1):

    See the Guidelines for Rule 2 - Size restrictions.

    +

    Rule 2a - Gross Size

    +

    The overall maximum size of your prog.c program source MUST NOT exceed 4993 bytes.

    NOTE: by default iocccsize will only report the rule 2b size, unless the @@ -526,9 +530,11 @@ code surpasses the limit.

    See Entering the IOCCC: the bare minimum you need to know.

    +

    Rule 2b - Net Size

    +

    When the filename of your program source (i.e., prog.c) is given as a command line argument to the latest version of the official IOCCC size tool (hereby referred to as iocccsize(1)), the value printed MUST @@ -615,7 +621,8 @@ a case insensitive filesystem.

    See the FAQ on “What permissions may my files be and what if I need different permissions?”.

    See the Guidelines on the mkiocccentry toolkit.

    -

    See the Guidelines on the Makefile.

    +

    See the +FAQ on “What are the detailed recommendations for a submission Makefile?”.

    Rule 5 - Do NOT modify submitted files or filenames or parent directories

    @@ -677,9 +684,9 @@ validate your submission.

    Do NOT register more than one account!

    See Rule 3 - Registering for the IOCCC, -Rule 15 - GNU Makefile compatibility, +Rule 15 - GNU Makefile, and -Rule 17 - Use mkiocccentry.

    +Rule 17 - Use mkiocccentry.

    Rule 9 - No interactive compiling allowed

    @@ -693,7 +700,7 @@ environment.

    the make command.

    NOTE: it is better and more portable to NOT modify the ${CC} variable in the Makefile.

    -

    See Rule 15 - GNU Makefile compatibility.

    +

    See Rule 15 - GNU Makefile.

    Rule 10 - Program file permissions

    @@ -750,8 +757,8 @@ be rejected. Please do NOT put trailing CTRL+M in prog.c< or remarks.md files, but instead end lines with Unix newline (line-feed, CTRL+J, \n).

    You are permitted, in order to try and squeeze your prog.c under a -Rule 2a Gross Size and/or -Rule 2b Net Size +Rule 2a Gross Size and/or +Rule 2b Net Size limits, to NOT end source with a newline. If you need to do this, please document that in your remarks.md file and if your compiler complains about this, document this too and update your @@ -793,8 +800,9 @@ GNU long name options (such as --example) or extensions like

    Do NOT assume that . (current directory) is in the $PATH environment variable.

    See Rule 4 - Required files.

    -

    See FAQ on “What are the detailed recommendations for a submission Makefile?”.

    -

    See Guidelines for Rule 15 - GNU Makefile compatibility.

    +

    See +FAQ on “What are the detailed recommendations for a submission Makefile?”.

    +

    See Guidelines for Rule 15 - GNU Makefile.

    Rule 16 - Anonymous judging

    @@ -842,7 +850,7 @@ the IOCCC judges only    ”, in their respective man pages.

    toolkit command lines that confirm to the command’s -h “print help message”, again notwithstanding the options for testing and the IOCCC judges.

    -

    The prog.c file MUST pass the Rule 2 - Size +

    The prog.c file MUST pass the Rule 2 - Size checks performed by iocccsize(1).

    The .auth.json and .info.json files MUST be compatible with what mkiocccentry(1) generates.

    @@ -865,14 +873,14 @@ FAQ on “What is the mkiocccentry tool, how

    This 19th rule, while prime, is reserved for future abuse 😁. Additional rules, both humorous and otherwise, may be added below this rule in future contests.

    -

    See Rule 6 - Free Rule.

    +

    See Rule 6 - Free Rule.

    Further Reading

    Please read the Guidelines next for further commentary on these rules.

    Read the Entering the IOCCC: the bare minimum you need to know for an overview of how to enter the contest.

    See also the FAQ.

    -

    And now for something completely different

    +

    And now for something completely different.

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

    Leonid A. Broukhis diff --git a/next/rules.md b/next/rules.md index 68c519031..f87d14393 100644 --- a/next/rules.md +++ b/next/rules.md @@ -10,9 +10,9 @@ These rules are a **TENTATIVE proposal** for the next IOCCC and are **likely be to be updated** before the next IOCCC. See our -FAQ on "[rules, guidelines and tools feedback](../faq.html#feedback)" +FAQ on "[rules, guidelines, tools feedback](../faq.html#feedback)" as well as our -FAQ on "[asking questions](../faq.html#question)" +FAQ on "[about asking questions](../faq.html#question)" about these rules. You might also find the FAQ in general useful, especially the FAQ on "[how to enter the IOCCC](../quick-start.html#enter)". @@ -78,10 +78,12 @@ Your submission **MUST** be a C program that does NOT `#include` data files.

    +
    ## Rule 2 - Size restrictions
    +
    `Rule 2` requires that your submission satisfy **BOTH** [Rule 2a (Gross Size)](rules.html#rule2a) @@ -98,9 +100,11 @@ See the [Guidelines for Rule 2 - Size restrictions](guidelines.html#guideline-2-
    +
    ### Rule 2a - Gross Size
    +
    The overall maximum size of your `prog.c` program source **MUST NOT** exceed **4993** bytes. @@ -113,9 +117,11 @@ See [Entering the IOCCC: the bare minimum you need to know](../quick-start.html#
    +
    ### Rule 2b - Net Size
    +
    When the filename of your program source (i.e., `prog.c`) is given as a command line argument to the latest version of the official IOCCC size @@ -234,7 +240,8 @@ FAQ on "[What permissions may my files be and what if I need different permissio See the [Guidelines on the mkiocccentry toolkit](guidelines.html#mkiocccentry_toolkit). -See the [Guidelines on the Makefile](guidelines.html#makefile). +See the +FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)".
    @@ -321,9 +328,9 @@ Do **NOT** register more than one account! See [Rule 3 - Registering for the IOCCC](rules.html#rule3-register), -[Rule 15 - GNU Makefile compatibility](rules.html#rule15-gnu-makefile), +[Rule 15 - GNU Makefile](rules.html#rule15-gnu-makefile), and -[Rule 17 - Use mkiocccentry](rules.html#rule-17-mkiocccentry). +[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry).
    @@ -344,7 +351,7 @@ the make command. **NOTE**: it is better and more portable to **NOT** modify the `${CC}` variable in the Makefile. -See [Rule 15 - GNU Makefile compatibility](rules.html#rule-15---building). +See [Rule 15 - GNU Makefile](rules.html#rule15-gnu-makefile).
    @@ -420,8 +427,8 @@ or `remarks.md` files, but instead end lines with Unix newline (line-feed, CTRL+J, `\n`). You are permitted, in order to try and squeeze your `prog.c` under a -[Rule 2a Gross Size](rules.html#rule-2a-gross-size) and/or -[Rule 2b Net Size](rules.html#rule-2b-net-size) +[Rule 2a Gross Size](rules.html#rule2a-gross-size) and/or +[Rule 2b Net Size](rules.html#rule2b-net-size) limits, to **NOT** end source with a newline. If you need to do this, please document that in your `remarks.md` file and if your compiler complains about this, document this too and update your @@ -480,9 +487,10 @@ variable. See [Rule 4 - Required files](rules.html#rule4-required-files). -See FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)". +See +FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)". -See [Guidelines for Rule 15 - GNU Makefile compatibility](guidelines.html#guideline-15---building). +See [Guidelines for Rule 15 - GNU Makefile](guidelines.html#guideline-15---building).
    @@ -549,7 +557,7 @@ toolkit](https://github.com/ioccc-src/mkiocccentry) command lines that confirm to the command's `-h` "_print help message_", again notwithstanding the options for testing and the IOCCC judges. -The `prog.c` file **MUST** pass the [Rule 2 - Size](rules.html#rule-2---size) +The `prog.c` file **MUST** pass the [Rule 2 - Size](rules.html#rule2-size) checks performed by `iocccsize(1)`. The `.auth.json` and `.info.json` files **MUST** be compatible with what @@ -586,7 +594,7 @@ This 19th rule, while prime, is reserved for future abuse 😁. Additional rules, both humorous and otherwise, may be added below this rule in future contests. -See [Rule 6 - Free Rule](rules.html#rule6-free). +See [Rule 6 - Free Rule](rules.html#rule6-free-rule). ## Further Reading @@ -599,7 +607,7 @@ for an overview of how to enter the contest. See also the [FAQ](../faq.html). -And now [for something completely different](guidelines.html#fun) +And now [for something completely different](guidelines.html#fun). Consider joining the [IOCCC Discord Server](https://discord.com/invite/Wa42Qujwnw) for discussions about The Rules, questions for the Judges, and `C` in general. diff --git a/next/submit.html b/next/submit.html index df14ca71e..b9df6cacf 100644 --- a/next/submit.html +++ b/next/submit.html @@ -452,7 +452,7 @@ -

    Use mkiocccentry to rebuild# How to upload your submission to the IOCCC

    +

    How to upload your submission to the IOCCC

    IMPORTANT NOTE: The IOCCC submit server is only ready for submissions ONLY WHEN THE CONTEST IS open.

    @@ -518,7 +518,7 @@ the file selection step.

  • the status of the submission
  • the filename, which will be in the correct format, assuming you used mkiocccentry(1) which is HIGHLY recommended so that you do not break -Rule 17 - Packaging!
    • +Rule 17 - Use mkiocccentry!
  • the file length, which txzchk(1) will also verify (the file itself and the tarball listing).
  • the upload date.
    • @@ -576,7 +576,7 @@ To see any status updates, you should logout and log back in later.

    … or ANY other error then you MUST FIX your submission, repackage your tarball with mkiocccentry and upload to the same slot again! If you do not fix this your submission WILL BE REJECTED for violating -Rule 17 - Packaging!

    +Rule 17 - Use mkiocccentry!

    If the format test went well, then you will see:

    Status: submit file received by the IOCCC judges. Passed both txzchk and chksubmit tests.

    @@ -586,7 +586,7 @@ rules or that everything is OK once the tarball is extracted; it simply means the tests performed by the tools passed. If you find a flaw in a tool and abuse it and the tests pass then you stand a significant chance of having your submission rejected for violating -Rule 17 - Packaging, +Rule 17 - Use mkiocccentry, even if the tests passed.

    For details on txzchk, see the FAQ on “txzchk”.

    diff --git a/next/submit.md b/next/submit.md index 60a5cb6b5..59fee0320 100644 --- a/next/submit.md +++ b/next/submit.md @@ -1,4 +1,4 @@ -Use mkiocccentry to rebuild# How to upload your submission to the IOCCC +# How to upload your submission to the IOCCC **IMPORTANT NOTE**: The [IOCCC submit server](https://submit.ioccc.org) is only ready for submissions @@ -87,7 +87,7 @@ And in the slot it will give you important details like: - the status of the submission - the filename, which will be in the correct format, assuming you used `mkiocccentry(1)` which is **HIGHLY** recommended so that you do not break -[Rule 17 - Packaging](rules.html#rule-17---packaging)! +[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry)! - the file length, which `txzchk(1)` will also verify (the file itself and the tarball listing). - the upload date. @@ -158,7 +158,7 @@ Or: ... or **ANY** other error then you **MUST FIX** your submission, repackage your tarball with `mkiocccentry` and upload to the same slot again! If you do not fix this your submission **WILL BE REJECTED** for violating -[Rule 17 - Packaging](rules.html#rule-17---packaging)! +[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry)! If the format test went well, then you will see: @@ -169,7 +169,7 @@ rules or that everything is OK once the tarball is extracted; it simply means the tests performed by the tools passed. If you find a flaw in a tool and abuse it and the tests pass then you stand a significant chance of having your submission rejected for violating -[Rule 17 - Packaging](rules.html#rule-17---packaging), +[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry), even if the tests passed. For details on `txzchk`, see the diff --git a/quick-start.html b/quick-start.html index 2d58ee0e1..d53f3f306 100644 --- a/quick-start.html +++ b/quick-start.html @@ -566,13 +566,13 @@ for more info.

    NOTE: Please see our IOCCC markdown guide for important information on using markdown in the IOCCC.

    If the mkiocccentry tool indicates that there is a problem with your submission, especially if it identifies a -Rule 2 - Size, +Rule 2 - Size restrictions, or any other rule, related problem, you are strongly encouraged to revise and correct your entry and then re-run the mkiocccentry tool.

    If you choose to risk violating Rules, be sure and explain your reason for doing so in your remarks.md file.

    See also -Rule 17 - Packaging!

    +Rule 17 - Use mkiocccentry!

    IMPORTANT NOTE: the tools that require other tools, mkiocccentry(1) and txzchk(1), will, as of version 2.0.2 2025-03-11, search under $PATH. If you have an earlier version and you have not installed the tools and run the @@ -581,7 +581,7 @@ tools to set the path to the required tools.

    Do remember to make sure you have the latest vers chksubmit(1), txzchk(1) and fnamchk(1). And remember to make sure you have the latest version so you do not violate -Rule 17 - Packaging. +Rule 17 - Use mkiocccentry. See the FAQ on “obtaining the latest mkiocccentry tools”, the diff --git a/quick-start.md b/quick-start.md index 192fdf4bb..e975c697e 100644 --- a/quick-start.md +++ b/quick-start.md @@ -162,7 +162,7 @@ Three files are required to exist in `topdir`: If the `mkiocccentry` tool indicates that there is a problem with your submission, especially if it identifies a -[Rule 2 - Size](next/rules.html#rule-2---size), +[Rule 2 - Size restrictions](next/rules.html#rule2-size), or any other [rule](next/rules.html), related problem, you are **strongly** encouraged to revise and correct your entry and then re-run the `mkiocccentry` tool. @@ -170,7 +170,7 @@ If you choose to risk violating [Rules](next/rules.html), be sure and explain yo for doing so in your `remarks.md` file. See also -[Rule 17 - Packaging](next/rules.html#rule-17---packaging)! +[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry)! **IMPORTANT NOTE**: the tools that require other tools, `mkiocccentry(1)` and `txzchk(1)`, will, as of version `2.0.2 2025-03-11`, search under `$PATH`. If @@ -181,7 +181,7 @@ tools to set the path to the required tools. Do remember to make sure you have the latest vers `chksubmit(1)`, `txzchk(1)` and `fnamchk(1)`. And remember to make sure you have the latest version so you do not violate -[Rule 17 - Packaging](next/rules.html#rule-17---packaging). +[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry). See the FAQ on "[obtaining the latest mkiocccentry tools](faq.html#obtaining_mkiocccentry)", the