Change references of 'alt code' to 'alternate code'

This was done by:

    sgit -e 's/alt code/alternate code/g' . ; git co tmp/OLD_manifest

as well as updating the tmp/manifest.numbers spreadsheet and exporting
to the CSV file (though that would not strictly be necessary).

The way this works means that the update manifest script does not need
to be run as it sgit(1) touched the .entry.json files (any that needed
to be updated) and so would any index.html files. An example for both
.entry.json and index.html files being modified due to manifest is
2012/kang.

Numerous Makefiles were updated, any try scripts that had 'alt code'
instead of 'alternate code' and README.md/index.html files (unrelated to
the manifest as 'alt code' was used in other places too) and obviously
the manifest.numbers spreadsheet.

However to be safe I will do a run of the manifest script in a bit even
though it should not be necessary. If no commits are made it means all
is good and if any commits are made for the manifest it means that I
did not think of something (or else I made another change after this).
This commit is contained in:
Cody Boone Ferguson committed 2024-05-30 08:02:32 -07:00
1 parent bb6c0d0bb6
commit ffdb219ceb
81 files changed
+4483 -4483

No files matched your search

+7 -7
View File
@@ -1918,23 +1918,23 @@ current source (that is <code>entry.orig.c</code> to <code>entry.c</code>).</li>
</ul></li>
<li><code>make make diff_alt_orig</code>:
<ul>
<li>This rule will show the diff of the alt code to the original
code (that is <code>entry.alt.c</code> to <code>entry.orig.c</code>). If no alt code exists
<li>This rule will show the diff of the alternate code to the original
code (that is <code>entry.alt.c</code> to <code>entry.orig.c</code>). If no alternate code exists
nothing will be shown.</li>
</ul></li>
<li><code>make diff_alt_prog</code>:
<ul>
<li>This rule will show the diff of the alt code to the entry as it
<li>This rule will show the diff of the alternate code to the entry as it
stands (that is <code>entry.alt.c</code> to <code>entry.c</code>).</li>
</ul></li>
<li><code>make diff_orig_alt</code>:
<ul>
<li>This rule will show the diff of the original code to the alt code
<li>This rule will show the diff of the original code to the alternate code
(that is <code>entry.orig.c</code> to <code>entry.alt.c</code>).</li>
</ul></li>
<li><code>make diff_prog_alt</code>:
<ul>
<li>This rule will show the diff of the entry to the alt code (that is
<li>This rule will show the diff of the entry to the alternate code (that is
<code>entry.c</code> to <code>entry.alt.c</code>).</li>
</ul></li>
<li><code>make diff_prog_orig</code>:
@@ -1950,7 +1950,7 @@ would be instead <code>prog.orig.c</code>, <code>prog.alt.c</code> and <code>pro
<p>Note that you might see something like:</p>
<pre><code> make: [Makefile:170: diff_orig_prog] Error 1 (ignored)</code></pre>
<p>at the end of the output but this is completely normal if there are differences.</p>
<p>If the alt code is the same as the original, say with
<p>If the alternate code is the same as the original, say with
<a href="1984/anonymous/index.html">1984/anonymous</a>, then naturally there is no point in
running the rule and the same applies for all the other rules but this system
allows for easily seeing the diffs.</p>
@@ -1981,7 +1981,7 @@ very easily. To do that <code>cd 1991/dds</code> and then do:</p>
just do:</p>
<pre><code> make DIFF=colordiff diff_orig_prog # for orig to prog diff
make DIFF=colordiff diff_alt_prog # for alt to prog diff</code></pre>
<p>Obviously if you want to view the alt code or the orig code you can just open
<p>Obviously if you want to view the alternate code or the orig code you can just open
the files as described above.</p>
<div id="faq4_3">
<h3 id="faq-4.3---why-do-author-remarks-sometimes-not-match-the-source-andor-why-are-there-other-inconsistencies-with-the-original-entry">FAQ 4.3 - Why do author remarks sometimes not match the source and/or why are there other inconsistencies with the original entry?</h3>