fix broken markdown local links in faq.md

Ran `make gen_top_html` to perform the above.
This commit is contained in:
Landon Curt Noll committed 2024-04-28 14:43:30 -07:00
1 parent 9ea6e73805
commit 57dca5525b
2 files changed
+14 -17

No files matched your search

+7 -8
View File
@@ -482,9 +482,9 @@ see of the IOCCC is open.</p>
<p>You may only register for the IOCCC <p>You may only register for the IOCCC
and you may only submit your entries to the IOCCC when the IOCCC is <strong>OPEN</strong>.</p></li> and you may only submit your entries to the IOCCC when the IOCCC is <strong>OPEN</strong>.</p></li>
<li><p>Read the latest IOCCC rules and review the IOCCC guidelines</p> <li><p>Read the latest IOCCC rules and review the IOCCC guidelines</p>
<p>Please pay close attention to the <a href="rules.html">official IOCCC rules</a>.</p> <p>Please pay close attention to the <a href="next/rules.html">official IOCCC rules</a>.</p>
<p>You are also <strong>highly encouraged</strong> to review the <p>You are also <strong>highly encouraged</strong> to review the
<a href="guidelines.html">official IOCCC guidelines</a> as they contain important <a href="next/guidelines.html">official IOCCC guidelines</a> as they contain important
suggestions, useful hints, and IOCCC humor. :-)</p></li> suggestions, useful hints, and IOCCC humor. :-)</p></li>
<li><p>Register for the IOCCC</p> <li><p>Register for the IOCCC</p>
<p>The <strong>IOCCC registration procedure</strong> is still being designed. <p>The <strong>IOCCC registration procedure</strong> is still being designed.
@@ -520,7 +520,7 @@ prog.c path to the C source for your entry</p>
<p>NOTE: It is <em>NOT</em> necessary to install the tools to use them as you can run <p>NOTE: It is <em>NOT</em> necessary to install the tools to use them as you can run
the tools from the top of the <em>mkiocccentry repo</em> directory just fine.</p> the tools from the top of the <em>mkiocccentry repo</em> directory just fine.</p>
<p>If <code>mkiocccentry</code> tool indicates that there is a problem with your entry, <p>If <code>mkiocccentry</code> tool indicates that there is a problem with your entry,
especially if it identifies a <a href="rules.html#2">rule 2</a> related problem, especially if it identifies a <a href="next/rules.html#2">rule 2</a> related problem,
you are <strong>strongly</strong> encouraged to revise and correct your entry and you are <strong>strongly</strong> encouraged to revise and correct your entry and
then re-run the <code>mkiocccentry</code> tool.</p> then re-run the <code>mkiocccentry</code> tool.</p>
<p>If you choose to risk violating rules, be sure an explain your reason <p>If you choose to risk violating rules, be sure an explain your reason
@@ -626,7 +626,7 @@ of the same theme.</p>
<p>While it is possible to win a new IOCCC with one of these <p>While it is possible to win a new IOCCC with one of these
<strong>frequently submitted</strong> types of entries, level of the competition from <strong>frequently submitted</strong> types of entries, level of the competition from
previous IOCCC entries make it more challenging to be successful.</p> previous IOCCC entries make it more challenging to be successful.</p>
<p>It is also important to note that the <a href="guidelines.html">guidelines</a> often <p>It is also important to note that the <a href="next/guidelines.html">guidelines</a> often
state something along the lines of:</p> state something along the lines of:</p>
<pre><code> We tend to dislike programs that: are similar to previous winning entries.</code></pre> <pre><code> We tend to dislike programs that: are similar to previous winning entries.</code></pre>
<p><strong>FAIR WARNING</strong>: Be sure to <strong>clearly explain</strong> near the beginning <p><strong>FAIR WARNING</strong>: Be sure to <strong>clearly explain</strong> near the beginning
@@ -759,7 +759,7 @@ Thus began the tradition of putting typos in the contest rules and guidelines
… to make them more obfuscated of course! :-)</p> … to make them more obfuscated of course! :-)</p>
<p>BTW: This posting was made back in the days when AT&amp;T was the evil giant. <p>BTW: This posting was made back in the days when AT&amp;T was the evil giant.
Now, Microsoft makes AT&amp;T look mild and kind in comparison. :-( (IMHO) ).</p> Now, Microsoft makes AT&amp;T look mild and kind in comparison. :-( (IMHO) ).</p>
<p>BTW: See the story about the ‘<a href="1993/mills/index.html">Bill Gates</a>’ award. :-)</p> <p>BTW: See the story about the ‘<a href="1993/cmills/index.html">Bill Gates</a>’ award. :-)</p>
<p>OK, back to the story.</p> <p>OK, back to the story.</p>
<p>We (Larry and I) received a number of entries by email. <p>We (Larry and I) received a number of entries by email.
When we began to receive messages from outside of the US, Larry and I When we began to receive messages from outside of the US, Larry and I
@@ -790,7 +790,6 @@ posting was <strong>I</strong>nternational <strong>O</strong>bfuscated <strong>C
and the tradition continues as the longest running contest on the Internet.</p> and the tradition continues as the longest running contest on the Internet.</p>
<p>P.S. Part of the inspiration for making the IOCCC a contest goes to the <p>P.S. Part of the inspiration for making the IOCCC a contest goes to the
<a href="http://www.bulwer-lytton.com/">Bulwer-Lytton fiction contest</a>.</p> <a href="http://www.bulwer-lytton.com/">Bulwer-Lytton fiction contest</a>.</p>
<p>P^2.S. See the <a href="all/index.html">overall README</a> for more details.</p>
<div id="faq1_1"> <div id="faq1_1">
<h3 id="faq-1.1-why-are-some-years-missing-ioccc-entries">FAQ 1.1: Why are some years missing IOCCC entries?</h3> <h3 id="faq-1.1-why-are-some-years-missing-ioccc-entries">FAQ 1.1: Why are some years missing IOCCC entries?</h3>
</div> </div>
@@ -817,7 +816,7 @@ web site.</p>
<h4 id="dec-28-bzip2-compressed-tarball-archive">2020 Dec 28 bzip2 compressed tarball archive</h4> <h4 id="dec-28-bzip2-compressed-tarball-archive">2020 Dec 28 bzip2 compressed tarball archive</h4>
<p>Furthermore, a bzip2 compressed tarball containing the released <p>Furthermore, a bzip2 compressed tarball containing the released
IOCCC entry source code may be found under the IOCCC entry source code may be found under the
<a href="archive/histroic">archive/historic</a> directory. The file <a href="archive/historic/index.html">archive/historic</a> directory. The file
<a href="archive/historic/archive-all.tar.bz2">archive-all.tar.bz2</a> contains <a href="archive/historic/archive-all.tar.bz2">archive-all.tar.bz2</a> contains
all years and the individual years are in the form all years and the individual years are in the form
<code>archive/historic/archive-YYYY.tar.bz2</code>.</p> <code>archive/historic/archive-YYYY.tar.bz2</code>.</p>
@@ -2616,7 +2615,7 @@ of 2020 is found under the following directory:</p>
<p>The <a href=".top">.top</a> file resides at the top directory. This file contains the complete list <p>The <a href=".top">.top</a> file resides at the top directory. This file contains the complete list
of IOCCC years.</p> of IOCCC years.</p>
<p>Under each IOCCC year. one will find a <code>.year</code> file. These files contain directory paths from the top directory, <p>Under each IOCCC year. one will find a <code>.year</code> file. These files contain directory paths from the top directory,
of the IOCCC entry directories for a given year. For example, see the <a href=".1984/.year">1984/.year</a> file.</p> of the IOCCC entry directories for a given year. For example, see the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/.year">1984/.year</a> file.</p>
<p>Under each IOCCC entry directory, you will find a <code>.path</code> file. <p>Under each IOCCC entry directory, you will find a <code>.path</code> file.
These files contain the directory path from the top directory. These files contain the directory path from the top directory.
For example see <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/anonymous/.path">1984/anonymous/.path</a>.</p> For example see <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/anonymous/.path">1984/anonymous/.path</a>.</p>
+7 -9
View File
@@ -113,10 +113,10 @@ To submit your code to the IOCCC, you **MUST** follow these steps:
1. Read the latest IOCCC rules and review the IOCCC guidelines 1. Read the latest IOCCC rules and review the IOCCC guidelines
Please pay close attention to the [official IOCCC rules](rules.html). Please pay close attention to the [official IOCCC rules](next/rules.html).
You are also **highly encouraged** to review the You are also **highly encouraged** to review the
[official IOCCC guidelines](guidelines.html) as they contain important [official IOCCC guidelines](next/guidelines.html) as they contain important
suggestions, useful hints, and IOCCC humor. :-) suggestions, useful hints, and IOCCC humor. :-)
2. Register for the IOCCC 2. Register for the IOCCC
@@ -173,7 +173,7 @@ To submit your code to the IOCCC, you **MUST** follow these steps:
the tools from the top of the _mkiocccentry repo_ directory just fine. the tools from the top of the _mkiocccentry repo_ directory just fine.
If `mkiocccentry` tool indicates that there is a problem with your entry, If `mkiocccentry` tool indicates that there is a problem with your entry,
especially if it identifies a [rule 2](rules.html#2) related problem, especially if it identifies a [rule 2](next/rules.html#2) related problem,
you are **strongly** encouraged to revise and correct your entry and you are **strongly** encouraged to revise and correct your entry and
then re-run the `mkiocccentry` tool. then re-run the `mkiocccentry` tool.
@@ -307,7 +307,7 @@ While it is possible to win a new IOCCC with one of these
**frequently submitted** types of entries, level of the competition from **frequently submitted** types of entries, level of the competition from
previous IOCCC entries make it more challenging to be successful. previous IOCCC entries make it more challenging to be successful.
It is also important to note that the [guidelines](guidelines.html) often It is also important to note that the [guidelines](next/guidelines.html) often
state something along the lines of: state something along the lines of:
``` ```
@@ -491,7 +491,7 @@ Thus began the tradition of putting typos in the contest rules and guidelines
BTW: This posting was made back in the days when AT&amp;T was the evil giant. BTW: This posting was made back in the days when AT&amp;T was the evil giant.
Now, Microsoft makes AT&amp;T look mild and kind in comparison. :-( (IMHO) ). Now, Microsoft makes AT&amp;T look mild and kind in comparison. :-( (IMHO) ).
BTW: See the story about the '[Bill Gates](1993/mills/index.html)' award. :-) BTW: See the story about the '[Bill Gates](1993/cmills/index.html)' award. :-)
OK, back to the story. OK, back to the story.
@@ -532,8 +532,6 @@ and the tradition continues as the longest running contest on the Internet.
P.S. Part of the inspiration for making the IOCCC a contest goes to the P.S. Part of the inspiration for making the IOCCC a contest goes to the
[Bulwer-Lytton fiction contest](http://www.bulwer-lytton.com/). [Bulwer-Lytton fiction contest](http://www.bulwer-lytton.com/).
P^2.S. See the [overall README](all/index.html) for more details.
<div id="faq1_1"> <div id="faq1_1">
### FAQ 1.1: Why are some years missing IOCCC entries? ### FAQ 1.1: Why are some years missing IOCCC entries?
@@ -572,7 +570,7 @@ web site.
Furthermore, a bzip2 compressed tarball containing the released Furthermore, a bzip2 compressed tarball containing the released
IOCCC entry source code may be found under the IOCCC entry source code may be found under the
[archive/historic](archive/histroic) directory. The file [archive/historic](archive/historic/index.html) directory. The file
[archive-all.tar.bz2](archive/historic/archive-all.tar.bz2) contains [archive-all.tar.bz2](archive/historic/archive-all.tar.bz2) contains
all years and the individual years are in the form all years and the individual years are in the form
`archive/historic/archive-YYYY.tar.bz2`. `archive/historic/archive-YYYY.tar.bz2`.
@@ -3348,7 +3346,7 @@ The [.top](.top) file resides at the top directory. This file contains the comp
of IOCCC years. of IOCCC years.
Under each IOCCC year. one will find a `.year` file. These files contain directory paths from the top directory, Under each IOCCC year. one will find a `.year` file. These files contain directory paths from the top directory,
of the IOCCC entry directories for a given year. For example, see the [1984/.year](.1984/.year) file. of the IOCCC entry directories for a given year. For example, see the [1984/.year](%%REPO_URL%%/1984/.year) file.
Under each IOCCC entry directory, you will find a `.path` file. Under each IOCCC entry directory, you will find a `.path` file.
These files contain the directory path from the top directory. These files contain the directory path from the top directory.