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

fix problematic HTML caused by certain trailing backslashes

Browse Source 
In cases that are **outside of a markdown code block**,
a markdown line with ending in a tailing "\" can generate
problematic HTML.

We certain trailing backslashes outside of a markdown code block
with "<br>" HTML elements, or in some cases eliminated the
need for a trailing backslash.

In a few cases some unnecessary trailing backslashes inside
of a markdown code block were removed.

The following markdown files were changed in this commit:

```
1990/dds/README.md
1990/jaw/README.md
1991/ant/README.md
1991/rince/README.md
1991/westley/README.md
1992/vern/README.md
1992/westley/README.md
1998/schweikh1/README.md
2004/anonymous/README.md
2005/sykes/README.md
2006/toledo2/README.md
2011/toledo/README.md
2012/endoh2/README.md
2012/tromp/README.md
2013/robison/README.md
2015/hou/README.md
2015/howe/README.md
2015/schweikhardt/README.md
2018/burton1/README.md
2018/burton2/README.md
2018/ferguson/README.md
2018/vokes/README.md
2020/ferguson1/README.md
```

Performed `make www` to test these changes.
This commit is contained in:
Landon Curt Noll committed 2024-04-17 00:25:09 -07:00
1 parent 1785da1728
commit 4c3649a3c1
47 files changed
+481 -502
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

1991/ant/README.md
+5 -5
View File
@@ -138,18 +138,18 @@ screen with long lines. Paging up and down should work correctly, however.
### References:
[Fin80] Craig A. Finseth, "Theory and Practice of Text Editors or\
A Cookbook For An EMACS", TM-165, MIT Lab. for Computer\
[Fin80] Craig A. Finseth, "Theory and Practice of Text Editors or<br>
A Cookbook For An EMACS", TM-165, MIT Lab. for Computer<br>
Science
[KeP81] Kernighan & Plauger, "Software Tools in Pascal",\
[KeP81] Kernighan & Plauger, "Software Tools in Pascal",<br>
Addison-Wesley, 81, chapter 6
[Mil86] Eugene W. Myers & Webb Miller, "Row-replacement Algorithms
for Screen Editors", TR 86-19, Dept. of Computer Science,\
for Screen Editors", TR 86-19, Dept. of Computer Science,<br>
U. of Arizona
[MyM86] Eugene W. Myers & Webb Miller, "A simple row-replacement\
[MyM86] Eugene W. Myers & Webb Miller, "A simple row-replacement<br>
method", TR 86-28, Dept. of Computer Science, U. of Arizona
[Mil87] Webb Miller, "A Software Tools Sampler", Prentice Hall, 87
1991/ant/index.html
+5 -5
View File
@@ -238,15 +238,15 @@ in the same group every so often.</p>
<p>This entry will display a file with long lines, but has trouble scrolling the
screen with long lines. Paging up and down should work correctly, however.</p>
<h3 id="references">References:</h3>
<p>[Fin80] Craig A. Finseth, “Theory and Practice of Text Editors or<br />
A Cookbook For An EMACS”, TM-165, MIT Lab. for Computer<br />
<p>[Fin80] Craig A. Finseth, “Theory and Practice of Text Editors or<br>
A Cookbook For An EMACS”, TM-165, MIT Lab. for Computer<br>
Science</p>
<p>[KeP81] Kernighan &amp; Plauger, “Software Tools in Pascal”,<br />
<p>[KeP81] Kernighan &amp; Plauger, “Software Tools in Pascal”,<br>
Addison-Wesley, 81, chapter 6</p>
<p>[Mil86] Eugene W. Myers &amp; Webb Miller, “Row-replacement Algorithms
for Screen Editors”, TR 86-19, Dept. of Computer Science,<br />
for Screen Editors”, TR 86-19, Dept. of Computer Science,<br>
U. of Arizona</p>
<p>[MyM86] Eugene W. Myers &amp; Webb Miller, “A simple row-replacement<br />
<p>[MyM86] Eugene W. Myers &amp; Webb Miller, “A simple row-replacement<br>
method”, TR 86-28, Dept. of Computer Science, U. of Arizona</p>
<p>[Mil87] Webb Miller, “A Software Tools Sampler”, Prentice Hall, 87
ISBN 0-13-822305-X, chapter 5</p>
1991/rince/README.md
+3 -3
View File
@@ -87,15 +87,15 @@ Key to map:
###### | | | /\ /--\ ==| /\ | | Directonal keys
###### Solid Wall | ----|| \/ /\ ||---- (unlock doors of
###### | \/ ==| \--/ \/ the same direction)
|\
|
| << >> Doors. Unlocked by
Blank space | << vvvvvv ^^^^^^ >> the above keys.
| << >>
|\
|
___ | o__O\ O__O ^__^ /O__o\
/ \ 'Crushable' | \___/ /----\ /----\ \___/ The four sprites for
\___/ boulder | _/_\ _/ \_ _/ \_ /_\_ your character :-)
|\
|
___ uncrushable | /\ Diamonds. They can either be found lying
/@@@\ boulder | < > around (if only!) or manufacture by pushing
\@@@/ | \/ two 'crushable' rocks together.
1991/rince/index.html
+3 -3
View File
@@ -195,15 +195,15 @@ enjoyment high.</p>
###### | | | /\ /--\ ==| /\ | | Directonal keys
###### Solid Wall | ----|| \/ /\ ||---- (unlock doors of
###### | \/ ==| \--/ \/ the same direction)
|\
|
| &lt;&lt; &gt;&gt; Doors. Unlocked by
Blank space | &lt;&lt; vvvvvv ^^^^^^ &gt;&gt; the above keys.
| &lt;&lt; &gt;&gt;
|\
|
___ | o__O\ O__O ^__^ /O__o\
/ \ &#39;Crushable&#39; | \___/ /----\ /----\ \___/ The four sprites for
\___/ boulder | _/_\ _/ \_ _/ \_ /_\_ your character :-)
|\
|
___ uncrushable | /\ Diamonds. They can either be found lying
/@@@\ boulder | &lt; &gt; around (if only!) or manufacture by pushing
\@@@/ | \/ two &#39;crushable&#39; rocks together.
1991/westley/README.md
+12 -10
View File
@@ -143,16 +143,18 @@ What happens if you make a move already made?
Now go try and draw or better yet win (without cheating which is very easy :-) )!
Why is win better than draw? Because everyone knows how to draw:
> Professor Falken: Did you ever play tic-tac-toe?\
> Jennifer Mack: Yeah. Of course.\
> Falken: But you don't any more.\
> Jennifer: No.\
> Falken: Why?\
> Jennifer: Because it's a boring game. It's always a tie.\
> Falken: Exactly. There's no way to win. The game itself is pointless. But back
at the [International Obfuscated C Code Contest judges'
room](../../judges.html) they believe that
you can win tic-tac-toe, that there can be acceptable draws.
```
Professor Falken: Did you ever play tic-tac-toe?
Jennifer Mack: Yeah. Of course.
Falken: But you don't any more.
Jennifer: No.
Falken: Why?
Jennifer: Because it's a boring game. It's always a tie.
Falken: Exactly. There's no way to win. The game itself is pointless.
But back at the International Obfuscated C Code Contest judges'
room they believe that you can win tic-tac-toe, that there can
be acceptable draws.
```
This is supposed to happen. As is written in the
[The Jargon File](http://catb.org/jargon/html/F/feature.html):
1991/westley/index.html
+10 -12
View File
@@ -231,18 +231,16 @@ can lose if you cheat. That’s supposed to happen. Can you win any other time?<
<p>What happens if you make a move already made?</p>
<p>Now go try and draw or better yet win (without cheating which is very easy :-) )!
Why is win better than draw? Because everyone knows how to draw:</p>
<blockquote>
<p>Professor Falken: Did you ever play tic-tac-toe?<br />
Jennifer Mack: Yeah. Of course.<br />
Falken: But you don’t any more.<br />
Jennifer: No.<br />
Falken: Why?<br />
Jennifer: Because it’s a boring game. It’s always a tie.<br />
Falken: Exactly. There’s no way to win. The game itself is pointless. But back
at the <a href="../../judges.html">International Obfuscated C Code Contest judges’
room</a> they believe that
you can win tic-tac-toe, that there can be acceptable draws.</p>
</blockquote>
<pre><code> Professor Falken: Did you ever play tic-tac-toe?
Jennifer Mack: Yeah. Of course.
Falken: But you don&#39;t any more.
Jennifer: No.
Falken: Why?
Jennifer: Because it&#39;s a boring game. It&#39;s always a tie.
Falken: Exactly. There&#39;s no way to win. The game itself is pointless.
But back at the International Obfuscated C Code Contest judges&#39;
room they believe that you can win tic-tac-toe, that there can
be acceptable draws.</code></pre>
<p>This is supposed to happen. As is written in the
<a href="http://catb.org/jargon/html/F/feature.html">The Jargon File</a>:</p>
<pre><code> That&#39;s not a bug, that&#39;s a feature.</code></pre>