Fix html lint (W3C Nu) errors
In the case of two which had an abstract (.entry.json file) that includes one (in one case) '<' or two (in another case) '<'s a markdown code block had to be used as otherwise the abstract would have to have a < which looks even worse. This is not ideal but if we want it to pass lint this is what has to be done. Use of json \uxxxx won't work as that encodes it to < literally. In the case of 2018/burton[12] the author had a section called Coda. This conflicted with the problem that all generated html files have such a section. To fix this problem I renamed it 'Final remarks'. Not ideal but at least it now passes as valid. There were a number of different kinds of problems and in one case the symbols < and > could be fixed by changing it to a code block (which it should have been anyway) - that was 2020/ferguson1 I think.
This commit is contained in:
1 parent
b4da848429
commit
c50835517f
14 files changed
+20
-22
No files matched your search
@@ -117,7 +117,7 @@ If you find yourself in an evolutionary dead end, try:
|
||||
0. Preface
|
||||
1. What it is
|
||||
2. How it works
|
||||
3. Hints (Keyboards, Options, Obfuscation, Example Invocations)
|
||||
3. Hints (Keyboards, Options, Easter egg, Example Invocations)
|
||||
4. Obfuscation (Techniques, Beauty)
|
||||
5. How to build (S and N Constants, Compilation, Portability, Installing)
|
||||
6. Final thoughts
|
||||
@@ -558,13 +558,13 @@ are only parsed if the first character is `-` and if the parser hasn't seen
|
||||
the `-` - *in an earlier element of `argv`. This is not a bug!*
|
||||
|
||||
|
||||
<div id="obfuscation">
|
||||
### Obfuscation
|
||||
<div id="easter-egg">
|
||||
### Easter egg
|
||||
</div>
|
||||
|
||||
Skip to [Example Invocations](#invocations).
|
||||
|
||||
The Easter egg: Since Dawkins references the [Infinite Monkey Theorem][] it
|
||||
The Easter egg: since Dawkins references the [Infinite Monkey Theorem][] it
|
||||
simulates a monkey using a typewriter! This mode has the following changes:
|
||||
|
||||
Selection is omitted; this means no sorting by fitness score (*each offspring
|
||||
|
||||
@@ -513,7 +513,7 @@ while using more Cenozoic minded code migration, read <a href="rpm.html">rpm.htm
|
||||
<li>Preface</li>
|
||||
<li>What it is</li>
|
||||
<li>How it works</li>
|
||||
<li>Hints (Keyboards, Options, Obfuscation, Example Invocations)</li>
|
||||
<li>Hints (Keyboards, Options, Easter egg, Example Invocations)</li>
|
||||
<li>Obfuscation (Techniques, Beauty)</li>
|
||||
<li>How to build (S and N Constants, Compilation, Portability, Installing)</li>
|
||||
<li>Final thoughts</li>
|
||||
@@ -825,9 +825,9 @@ itself) and then the target string would <em>literally</em> be set to <code>-r</
|
||||
it no longer cares about the <code>-</code> for option parsing. In other words options
|
||||
are only parsed if the first character is <code>-</code> and if the parser hasn’t seen
|
||||
the <code>-</code> - <em>in an earlier element of <code>argv</code>. This is not a bug!</em></p>
|
||||
<h3 id="obfuscation">Obfuscation</h3>
|
||||
<h3 id="easter-egg">Easter egg</h3>
|
||||
<p>Skip to <a href="#invocations">Example Invocations</a>.</p>
|
||||
<p>The Easter egg: Since Dawkins references the <a href="https://en.wikipedia.org/wiki/Infinite_monkey_theorem">Infinite Monkey Theorem</a> it
|
||||
<p>The Easter egg: since Dawkins references the <a href="https://en.wikipedia.org/wiki/Infinite_monkey_theorem">Infinite Monkey Theorem</a> it
|
||||
simulates a monkey using a typewriter! This mode has the following changes:</p>
|
||||
<p>Selection is omitted; this means no sorting by fitness score (<em>each offspring
|
||||
is initially set to be the first two in the list</em>) but do pseudo-randomly
|
||||
@@ -1048,9 +1048,7 @@ invalid character (<code>'\n'</code> itself which means another line break) and
|
||||
finally the closing <code>'</code>. Specifically <code>isspace()</code> characters aren’t
|
||||
distinctly seen like a letter, digit or symbol is: <code>isprint('\n') == 0 && isspace('\n') == 1</code>. You can add these characters but the output will be
|
||||
rather confusing and hard to read.</p>
|
||||
<div id="obfuscation">
|
||||
<h2 id="obfuscation-1"><strong>4. Obfuscation</strong></h2>
|
||||
</div>
|
||||
<h2 id="obfuscation"><strong>4. Obfuscation</strong></h2>
|
||||
<h3 id="techniques">Techniques</h3>
|
||||
<p>Skip to <a href="#beauty">Beauty</a>.</p>
|
||||
<p>The following might be some of the techniques used in this entry:</p>
|
||||
|
||||
Reference in new issue
Block a user