mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

changed web site to website

Browse Source
This commit is contained in:
Landon Curt Noll committed 2024-06-07 02:10:24 -07:00
1 parent 19725c1350
commit 6e698b238a
470 files changed
+1100 -1100
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

faq.html
+39 -39
View File
@@ -138,7 +138,7 @@
<div class="outfit-font">
<a href="./faq.html#fix_web_site" class="sub-item-link">
Fixing the web site
Fixing the website
</a>
</div>
@@ -283,7 +283,7 @@
</a>
<a class="mobile-submenu-item" href="./faq.html#fix_web_site">
Fixing the web site
Fixing the website
</a>
<a class="mobile-submenu-item" href="./faq.html#fix_author">
@@ -397,7 +397,7 @@
<ul>
<li><a href="#faq1_0">1.0 - How did the IOCCC get started?</a></li>
<li><a href="#faq1_1">1.1 - Why are some years missing IOCCC entries?</a></li>
<li><a href="#faq1_2">1.2 - What is the history of the IOCCC web site?</a></li>
<li><a href="#faq1_2">1.2 - What is the history of the IOCCC website?</a></li>
<li><a href="#faq1_3">1.3 - How has the IOCCC size limit rule changed over the years?</a></li>
</ul>
<h2 id="section-2---ioccc-judging-process">Section 2 - <a href="#faq2">IOCCC Judging process</a></h2>
@@ -451,8 +451,8 @@ other inconsistencies with the original entry?</a></li>
<li><a href="#faq5_0">5.0 - How may I help the IOCCC?</a></li>
<li><a href="#faq5_1">5.1 - How do I report a bug in an IOCCC entry?</a></li>
<li><a href="#faq5_2">5.2 - How may I submit a fix to an IOCCC entry?</a></li>
<li><a href="#faq5_3">5.3 - How may I report an IOCCC web site problem?</a></li>
<li><a href="#faq5_4">5.4 - How may I submit a fix to the IOCCC web site?</a></li>
<li><a href="#faq5_3">5.3 - How may I report an IOCCC website problem?</a></li>
<li><a href="#faq5_4">5.4 - How may I submit a fix to the IOCCC website?</a></li>
<li><a href="#faq5_5">5.5 - How may I correct or update IOCCC author information?</a></li>
<li><a href="#faq5_6">5.6 - What should I do if I find a broken or wrong web link?</a></li>
</ul>
@@ -460,7 +460,7 @@ other inconsistencies with the original entry?</a></li>
<ul>
<li><a href="#faq6_0">6.0 - How did an entry that breaks the size rule 2 win the IOCCC?</a></li>
<li><a href="#faq6_1">6.1 - Is there a list of known bugs and (mis)features of IOCCC entries?</a></li>
<li><a href="#faq6_2">6.2 - May I mirror the IOCCC web site?</a></li>
<li><a href="#faq6_2">6.2 - May I mirror the IOCCC website?</a></li>
<li><a href="#faq6_3">6.3 - May I use parts of the IOCCC in an article, book, newsletter, or instructional material?</a></li>
<li><a href="#faq6_4">6.4 - Why do you sometimes use the first person plural?</a></li>
<li><a href="#faq6_5">6.5 - What is an author handle?</a></li>
@@ -735,7 +735,7 @@ For example, we <a href="faq.html#submit">submitting to the IOCCC</a>, we have p
to submit remarks about entry in markdown format. Every
<a href="years.html">winning IOCCC entry</a> uses a <code>README.md</code> markdown file
as the basis for forming the <code>index.html</code> web page for that entry.
All generated HTML pages on the <a href="https://www.ioccc.org/index.html">Official IOCCC web site</a>
All generated HTML pages on the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>
start with some markdown content.</p>
<p><strong>IMPORTANT</strong>: Please read the <a href="markdown.html">IOCCC markdown best practices</a> guide
as it lists things you <strong>should not use</strong> in markdown files.</p>
@@ -812,12 +812,12 @@ do not permit us to hold a new IOCCC.</p>
<p>The pause during the 2021-2023 period was due to the IOCCC judges developing tools to
make is much more likely for the IOCCC to be held in a yearly basis later on.</p>
<div id="faq1_2">
<h3 id="faq-1.2-what-is-the-history-of-the-ioccc-web-site">FAQ 1.2: What is the history of the IOCCC web site?</h3>
<h3 id="faq-1.2-what-is-the-history-of-the-ioccc-website">FAQ 1.2: What is the history of the IOCCC website?</h3>
</div>
<h4 id="in-the-beginning-of-www.ioccc.org">In the beginning of www.ioccc.org</h4>
<p>The long history of the <a href="https://www.ioccc.org">official IOCCC web site</a> can be
<p>The long history of the <a href="https://www.ioccc.org">official IOCCC website</a> can be
viewed at the <a href="https://web.archive.org">Internet Wayback Machine Wayback Machine</a>.</p>
<p>One can <a href="https://web.archive.org/web/20230000000000*/www.ioccc.org">view several thousand snapshots showing how the IOCCC web site has
<p>One can <a href="https://web.archive.org/web/20230000000000*/www.ioccc.org">view several thousand snapshots showing how the IOCCC website has
evolved</a> going back
as far as <a href="https://web.archive.org/web/19981212030016/https://www.ioccc.org/">1998 Dec 12
www.ioccc.org</a>.</p>
@@ -825,7 +825,7 @@ www.ioccc.org</a>.</p>
repo</a> on
<a href="https://github.com">GitHub</a>. From this point on, the <a href="https://www.ioccc.org">official IOCCC web
site</a> became a <a href="https://pages.github.com">GitHub Pages</a>
web site.</p>
website.</p>
<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
IOCCC entry source code may be found under the
@@ -853,7 +853,7 @@ and then on <strong>Wed Dec 30 16:57:03 2020 -0800</strong> added a preview of
c0663537cb88d39b74285a930ff1a668c6d5968b</a>.</p>
<p>On 2020 Dec 30, with <a href="https://github.com/ioccc-src/winner/commit/c0663537cb88d39b74285a930ff1a668c6d5968b">commit
c0663537cb88d39b74285a930ff1a668c6d5968b</a>,
the <a href="https://web.archive.org/web/20221231001721/https://www.ioccc.org/">official IOCCC web site of 2022 Dec
the <a href="https://web.archive.org/web/20221231001721/https://www.ioccc.org/">official IOCCC website of 2022 Dec
29</a> was
uploaded into the <a href="https://github.com/ioccc-src/winner">Official IOCCC winner
repo</a>.</p>
@@ -897,11 +897,11 @@ and <a href="https://github.com/ioccc-src/winner/commit/098a3e7e04d43e480ecc4b54
an <a href="https://www.ioccc.org/judges.html">IOCCC judge</a> made edits to
their local repository with occasional pushes to the <a href="https://github.com/ioccc-src/winner">Official IOCCC winner
repo</a> and the <a href="https://www.ioccc.org/index.html">Official
www.ioccc.org web site</a>. After
www.ioccc.org website</a>. After
that time and until the <strong>Great Fork Merge</strong>, very few changes
were made to the <a href="https://github.com/ioccc-src/winner">Official IOCCC winner
repo</a> and the <a href="https://www.ioccc.org/index.html">Official
www.ioccc.org web site</a> most of
www.ioccc.org website</a> most of
which were news updates.</p>
<p>While the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
repo</a> has history
@@ -911,11 +911,11 @@ the repo was forked on <strong>Sun Sep 18 17:30:00 2022 -0700</strong>. The
first <a href="https://github.com/ioccc-src/temp-test-ioccc/commit/edbc3089e1b755d85a020af7975bbc7df3737a5f">push into the temp-test-ioccc
repo</a>
occurred on Sun Sep 18 11:15:49 2022 -0700.</p>
<p>At this same time, the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a> went live.</p>
<p>At this same time, the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a> went live.</p>
<p>Edits were made by an <a href="https://www.ioccc.org/judges.html">IOCCC judge</a>
to their local <a href="https://git-scm.com">git</a> repository and <a href="https://github.com/ioccc-src/temp-test-ioccc/commit/2f20ae8451ada03f4601ac727d10e1d8630861a8">were pushed into the temp-test-ioccc
repo</a>
and to the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a>.</p>
and to the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>.</p>
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/pull/15">first accepted pull request</a>
made directly to the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
repo</a> on
@@ -955,7 +955,7 @@ request</a>.</li>
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/bin/gen-years.sh">gen-years.sh</a> tool.</li>
<li>Setting up to generate the top level <a href="authors.html">authors.html file</a>, renamed
from <code>winners.html</code>, via the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/bin/gen-authors.sh">gen-authors.sh</a> tool.</li>
<li>Making use of a new and improved <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/ioccc.css">IOCCC CSS</a> for web site consistency</li>
<li>Making use of a new and improved <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/ioccc.css">IOCCC CSS</a> for website consistency</li>
<li>Etc.</li>
</ul>
<h4 id="y-mm-dd-the-great-fork-merge">202y mm dd The Great Fork Merge <!-- XXX - Fill in the date when Great Fork Merge happens --></h4>
@@ -965,7 +965,7 @@ there were <a href="https://github.com/ioccc-src/winner/compare/master...ioccc-s
of the <a href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>.</p>
<p>On 202y mm dd, the temporary repo was merged back into the <a href="https://github.com/ioccc-src/winner">IOCCC winner
repo</a> resulting in many, many substantial improvements
to the <a href="https://www.ioccc.org">official IOCCC web site</a>.</p>
to the <a href="https://www.ioccc.org">official IOCCC website</a>.</p>
<div id="faq1_3">
<div id="size_rule">
<h3 id="faq-1.3-how-has-the-ioccc-size-limit-rule-changed-over-the-years">FAQ 1.3: How has the IOCCC size limit rule changed over the years?</h3>
@@ -1139,7 +1139,7 @@ registered email address.</p></li>
<li><p>Announce who are authors of this year’s winning IOCCC entries via the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span> mastodon
feed</a>.</p></li>
<li><p>Upload the winning code to the <a href="https://github.com/ioccc-src/winner">Official IOCCC winner repo</a></p></li>
<li><p>Update the <a href="index.html">Official IOCCC web site</a>, and in particular
<li><p>Update the <a href="index.html">Official IOCCC website</a>, and in particular
display this year’s winning IOCCC entries at the top of the <a href="years.html">IOCCC
winning entries page</a>.</p></li>
<li><p>Update the <a href="news.html">IOCCC news</a> page.</p></li>
@@ -1333,7 +1333,7 @@ sharing might not work sometime, but it is the future. Fedora, also developed by
RHEL, has switched to a Wayland session as it’s default windowing system (And it
works flawlessly on my Laptop).</p>
</blockquote>
<p>See the <a href="https://wayland.freedesktop.org">Wayland</a> web site for more details.</p>
<p>See the <a href="https://wayland.freedesktop.org">Wayland</a> website for more details.</p>
<p><strong>IMPORTANT NOTE</strong>: We do <strong>NOT</strong> know if IOCCC entries will run under
<strong>Wayland</strong>. Some IOCCC entries that use X11 might be OK while other IOCCC
entries that use X11 in an unusual way might fail under <strong>Wayland</strong>.</p>
@@ -1415,7 +1415,7 @@ may be helpful:</p>
See the above note for details.</p>
<h4 id="package-website">Package website</h4>
<p>First, see the above note on <a href="#X11_general">installing and starting Xorg</a>.</p>
<p>See the <a href="https://x.org/wiki/">X.org</a> foundation web site.</p>
<p>See the <a href="https://x.org/wiki/">X.org</a> foundation website.</p>
<p><strong>IMPORTANT NOTE</strong>: The <a href="#Xorg_deprecated">X.org server has been deprecated</a>.
See the above note for details.</p>
<div id="faq3_8">
@@ -1863,13 +1863,13 @@ it like:</p>
</div>
</div>
<p>Although one can clone the entire <a href="https://github.com/ioccc-src/winner">winner
repo</a> to get the entire web site and all
repo</a> to get the entire website and all
entries, we also provide, as a convenience, a way to download individual entries
as well as a way to download a year’s winning entries.</p>
<p>Please note that some of the links in the html files will not work! This is
because you are not downloading the full website. If you want to view the entry
with links intact you should clone the repo or view it on the <a href="https://www.ioccc.org">official IOCCC
web site</a> instead.</p>
website</a> instead.</p>
<h4 id="individual-winning-entry-tarballs">Individual winning entry tarballs</h4>
<p>The individual entry tarballs are named in the form of
<code>YYYY/winner/YYYY_winner.tar.bz2</code> (e.g.
@@ -2127,7 +2127,7 @@ could no longer be so: <code>main()</code> instead had to call another function
the body of the old <code>main()</code> and that function would call itself again. In some
cases, however, this had to be done even without <code>clang</code> objections.</p>
<div id="faq5">
<h2 id="section-5-updating-or-correcting-ioccc-web-site-content">Section 5: Updating or correcting IOCCC web site content</h2>
<h2 id="section-5-updating-or-correcting-ioccc-website-content">Section 5: Updating or correcting IOCCC website content</h2>
</div>
<div id="faq5_0">
<div id="how_to_help">
@@ -2145,7 +2145,7 @@ in question. Note that in several cases what you may have discovered,
while a (mis)feature is not considered a bug and should <strong>not be fixed</strong>.
In cases where the bug is known, the entry’s <a href="bugs.html">known bugs</a> file
section may offer you important fixing clues.</p>
<h3 id="we-welcome-your-help-on-fixing-the-ioccc-web-site">We welcome your help on fixing the IOCCC web site</h3>
<h3 id="we-welcome-your-help-on-fixing-the-ioccc-website">We welcome your help on fixing the IOCCC website</h3>
<div id="faq5_1">
<div id="report_bug">
<h3 id="faq-5.1-how-do-i-report-a-bug-in-an-ioccc-entry">FAQ 5.1: How do I report a bug in an IOCCC entry?</h3>
@@ -2206,20 +2206,20 @@ request</a> for more information about pull requests.</p>
have the final say in the matter.</p>
<div id="faq5_3">
<div id="report_web_problem">
<h3 id="faq-5.3-how-may-i-report-an-ioccc-web-site-problem">FAQ 5.3: How may I report an IOCCC web site problem?</h3>
<h3 id="faq-5.3-how-may-i-report-an-ioccc-website-problem">FAQ 5.3: How may I report an IOCCC website problem?</h3>
</div>
</div>
<p>If you discover a problem with the IOCCC web site that is related
<p>If you discover a problem with the IOCCC website that is related
to a particular IOCCC entry, please see <a href="#report_bug">FAQ 5.1</a> for
information about reporting a bug in an IOCCC entry, and see <a href="#fix_an_entry">FAQ
5.2</a> for information on how to submit a fix to an IOCCC entry.</p>
<p>If you discover a problem with the IOCCC web site (such as a broken link, which
<p>If you discover a problem with the IOCCC website (such as a broken link, which
may or may not be specific to a particular IOCCC entry) that is <strong>not related
to a particular IOCCC entry</strong>, the best way you can help is to submit a fix to
the IOCCC web site. See <a href="#fix_web_site">FAQ 5.4</a> for information on submitting fixes
to the IOCCC web site.</p>
<p>If you do not have a IOCCC web site fix, and just wish to report a
general IOCCC web site problem, we ask that you first look at the
the IOCCC website. See <a href="#fix_web_site">FAQ 5.4</a> for information on submitting fixes
to the IOCCC website.</p>
<p>If you do not have a IOCCC website fix, and just wish to report a
general IOCCC website problem, we ask that you first look at the
<a href="https://github.com/ioccc-src/winner/issues">IOCCC issues</a> to see
if the problem has already been reported. If it has been reported,
feel free to add a comment to the issue. If you do not find an it
@@ -2227,10 +2227,10 @@ has been reported, then fee free to open a <a href="https://github.com/ioccc-src
issue</a>.</p>
<div id="faq5_4">
<div id="fix_web_site">
<h3 id="faq-5.4-how-may-i-submit-a-fix-to-the-ioccc-web-site">FAQ 5.4: How may I submit a fix to the IOCCC web site?</h3>
<h3 id="faq-5.4-how-may-i-submit-a-fix-to-the-ioccc-website">FAQ 5.4: How may I submit a fix to the IOCCC website?</h3>
</div>
</div>
<p>For IOCCC web site problems that relate to a particular IOCCC entry, please
<p>For IOCCC website problems that relate to a particular IOCCC entry, please
see <a href="#fix_an_entry">FAQ 5.2</a> for information on how submit a fix to an IOCCC entry.</p>
<p>You may open a <a href="https://github.com/ioccc-src/winner/pulls">GitHub pull request</a>
against the master <a href="https://github.com/ioccc-src/winner/branches">branch</a>
@@ -2241,7 +2241,7 @@ entry</a>. See also the <a href="#ull_request">FAQ 6.10 How does someone
make a change to a file and submit that change as a GitHub pull
request</a> for more information about pull requests.</p>
<h4 id="some-html-files-should-not-be-directly-modified">Some HTML files should NOT be directly modified</h4>
<p>Nearly all HTML files on the <a href="https://www.ioccc.org">IOCCC web site</a>
<p>Nearly all HTML files on the <a href="https://www.ioccc.org">IOCCC website</a>
are built from <a href="https://daringfireball.net/projects/markdown/">markdown</a> files.
If you see lines containing:</p>
<pre><code> &lt;!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! --&gt;
@@ -2377,7 +2377,7 @@ variety of kinds.</p>
not an issue and note that some issues are simply missing files, dead URL(s) or
something like that.</p>
<div id="faq6_2">
<h3 id="faq-6.2-may-i-mirror-the-ioccc-web-site">FAQ 6.2: May I mirror the IOCCC web site?</h3>
<h3 id="faq-6.2-may-i-mirror-the-ioccc-website">FAQ 6.2: May I mirror the IOCCC website?</h3>
</div>
<p>We are not accepting mirror requests at this time, sorry. However you are free to fork the <a href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>. We do ask that your fork keep up to date with the latest changes when possible.</p>
<div id="faq6_3">
@@ -2476,7 +2476,7 @@ in the case of <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master
information about authors of IOCCC entries and is used to help form
HTML files as well to contact an author.</p>
<p>The content of these JSON files are used by tools from a <a href="bin/index.html">bin directory tool</a>
to help build HTML content for the <a href="https://www.ioccc.org">official IOCCC web site</a>.
to help build HTML content for the <a href="https://www.ioccc.org">official IOCCC website</a>.
For example, the <code>index.html</code> file for each IOCCC entry contains
selected information about the authors. Tools from the <a href="bin/index.html">bin directory</a>
use the content of these JSON files to generate the <code>index.html</code> files for each IOCCC
@@ -2551,7 +2551,7 @@ be the exact <em>JSON string</em> as shown above.</p>
As of <em>Thu Nov 30 23:51:12 UTC 2023</em>, the <em>JSON value</em> <strong>MUST</strong> be <em>“1.0 2023-06-10”</em>.</p>
<p>The <em>author_JSON_format_version</em> would only changed when the overall format
of the these files is modified: and then only those who maintain the
<a href="https://www.ioccc.org">official IOCCC web site</a> would be the one to do this
<a href="https://www.ioccc.org">official IOCCC website</a> would be the one to do this
in conjunction with changes to <a href="bin/index.html">bin directory tools</a>.</p>
<h5 id="author_handle">author_handle</h5>
<pre><code> &quot;author_handle&quot; : &quot;Yusuke_Endoh&quot;,</code></pre>
@@ -2702,7 +2702,7 @@ information on Mastodon.</p>
be a <em>JSON string</em> or it <strong>MUST</strong> be a <em>JSON null</em>. The <code>github</code> <em>JSON string</em> <strong>MUST</strong>
start with an at sign (_<span class="citation" data-cites="_">@_</span>) and <strong>MUST</strong> be a valid GitHub username.</p>
<p>The IOCCC uses GitHub to hold the <a href="https://github.com/ioccc-src/winner">official winner repo of the IOCCC</a>,
and hosts <a href="https://www.ioccc.org">official IOCCC web site</a> on GitHub pages.</p>
and hosts <a href="https://www.ioccc.org">official IOCCC website</a> on GitHub pages.</p>
<p>The IOCCC GitHub handle is:</p>
<pre><code> @ioccc-src</code></pre>
<p>If the author wishes to not specify an GitHub handle, or if the GitHub handle is