improved indentation and whitespace for markdown code blocks
All code blocks in markdown have been intended by at least 4 spaces. We add `--tab-stop=8` to all `pandoc(1)` executions in order to set a better tab stop indentation, especially for tab intended code blocks. Changed `bin/pandoc-wrapper.sh` VERSION from "1.5.3 2024-03-26" to "1.6 2024-03-31". Fixed `1991/brnstnd/sorta.README.md` so that the sorta code is code blocks. Removed unneeded paragraph group in copyright in `inc/footer.default.html`. Fixed excess whitespace after list Author on entry `index.html` page. Changed `bin/output-index-author.sh` VERSION from "1.5.2 2024-03-26" to "1.6 2024-03-31". Performed `make www` to perform the above and test under macOS. TODO: Fix the problem of the initial line of code being extra intended. TODO: Fix excess whitespace around code that is inline.
This commit is contained in:
Landon Curt Noll committed
1 parent
b84c27ce02
commit
a996f8d2b8
734 files changed
+16723
-16963
No files matched your search
+13
-14
@@ -1,21 +1,21 @@
|
||||
## To build:
|
||||
|
||||
```sh
|
||||
make
|
||||
make
|
||||
```
|
||||
|
||||
|
||||
## To use:
|
||||
|
||||
```sh
|
||||
./omoikane infile layout outfile
|
||||
./omoikane infile layout outfile
|
||||
```
|
||||
|
||||
|
||||
## Try:
|
||||
|
||||
```
|
||||
./try.sh
|
||||
./try.sh
|
||||
```
|
||||
|
||||
|
||||
@@ -44,7 +44,7 @@ insert a human-readable checksum string in the text itself! `^_^`
|
||||
### Usage
|
||||
|
||||
```sh
|
||||
./omoikane <infile> <layout> <outfile>
|
||||
./omoikane <infile> <layout> <outfile>
|
||||
```
|
||||
|
||||
All three arguments may reference the same file. All files is
|
||||
@@ -82,18 +82,18 @@ layout.
|
||||
Example file/layout:
|
||||
|
||||
```
|
||||
file: layout:
|
||||
crc = ######## ... . XXXXXXXX
|
||||
patch = ###### ..... . XXXXXX
|
||||
other text here ..... .... ....
|
||||
file: layout:
|
||||
crc = ######## ... . XXXXXXXX
|
||||
patch = ###### ..... . XXXXXX
|
||||
other text here ..... .... ....
|
||||
```
|
||||
|
||||
And `Rinia` may generate a file similar to this:
|
||||
|
||||
```
|
||||
crc = 1bad73cf
|
||||
patch = #FR-QQ
|
||||
other text here
|
||||
crc = 1bad73cf
|
||||
patch = #FR-QQ
|
||||
other text here
|
||||
```
|
||||
|
||||
Note that the original file by itself is a valid layout file, since
|
||||
@@ -116,9 +116,8 @@ runs faster if the checksum is placed before the other marker
|
||||
characters rather than after, e.g.:
|
||||
|
||||
```
|
||||
a: X X XXX b: XXXXXXXX c: XXXXXXXX
|
||||
XXXXXXXX X X XXX XXXXX
|
||||
|
||||
a: X X XXX b: XXXXXXXX c: XXXXXXXX
|
||||
XXXXXXXX X X XXX XXXXX
|
||||
```
|
||||
|
||||
`a` usually takes the longest time, while `c` usually is the
|
||||
|
||||
+14
-16
@@ -132,8 +132,7 @@
|
||||
<h2 id="author"><a name="author"></a>Author:</h2>
|
||||
<ul>
|
||||
<li>Name: <a href="../../authors.html#Don_Yang">Don Yang</a><br>
|
||||
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)
|
||||
<br><br></li>
|
||||
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)</li>
|
||||
</ul>
|
||||
|
||||
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
|
||||
@@ -142,11 +141,11 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
|
||||
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span></span></code></pre></div>
|
||||
<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a> <span class="fu">make</span></span></code></pre></div>
|
||||
<h2 id="to-use">To use:</h2>
|
||||
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./omoikane</span> infile layout outfile</span></code></pre></div>
|
||||
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a> <span class="ex">./omoikane</span> infile layout outfile</span></code></pre></div>
|
||||
<h2 id="try">Try:</h2>
|
||||
<pre><code>./try.sh</code></pre>
|
||||
<pre><code> ./try.sh</code></pre>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>For extra credit, spot the checksum in the source file itself.
|
||||
What makes this one particularly interesting is that the checksum,
|
||||
@@ -162,7 +161,7 @@ Comments refer to it as such.</p>
|
||||
strange file names or package .SFVs with your files! <code>Rinia</code> will
|
||||
insert a human-readable checksum string in the text itself! <code>^_^</code></p>
|
||||
<h3 id="usage">Usage</h3>
|
||||
<div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./omoikane</span> <span class="op"><</span>infile<span class="op">></span> <span class="op"><</span>layout<span class="op">></span> <span class="op"><</span>outfile<span class="op">></span></span></code></pre></div>
|
||||
<div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a> <span class="ex">./omoikane</span> <span class="op"><</span>infile<span class="op">></span> <span class="op"><</span>layout<span class="op">></span> <span class="op"><</span>outfile<span class="op">></span></span></code></pre></div>
|
||||
<p>All three arguments may reference the same file. All files is
|
||||
assumed to be of ASCII character set.</p>
|
||||
<h3 id="input">Input</h3>
|
||||
@@ -188,14 +187,14 @@ then replace the remaining ones with space. Often it’s possible to
|
||||
write the original file in such a way that it can be used as a
|
||||
layout.</p>
|
||||
<p>Example file/layout:</p>
|
||||
<pre><code>file: layout:
|
||||
crc = ######## ... . XXXXXXXX
|
||||
patch = ###### ..... . XXXXXX
|
||||
other text here ..... .... ....</code></pre>
|
||||
<pre><code> file: layout:
|
||||
crc = ######## ... . XXXXXXXX
|
||||
patch = ###### ..... . XXXXXX
|
||||
other text here ..... .... ....</code></pre>
|
||||
<p>And <code>Rinia</code> may generate a file similar to this:</p>
|
||||
<pre><code>crc = 1bad73cf
|
||||
patch = #FR-QQ
|
||||
other text here</code></pre>
|
||||
<pre><code> crc = 1bad73cf
|
||||
patch = #FR-QQ
|
||||
other text here</code></pre>
|
||||
<p>Note that the original file by itself is a valid layout file, since
|
||||
<code>Rinia</code> will recognize that only <code>#</code> marks enough space to hold the
|
||||
checksum, and has the lowest frequency.</p>
|
||||
@@ -209,9 +208,8 @@ and nothing is written.</p>
|
||||
completely dominated by the layout file design. In general, <code>Rinia</code>
|
||||
runs faster if the checksum is placed before the other marker
|
||||
characters rather than after, e.g.:</p>
|
||||
<pre><code> a: X X XXX b: XXXXXXXX c: XXXXXXXX
|
||||
XXXXXXXX X X XXX XXXXX
|
||||
</code></pre>
|
||||
<pre><code> a: X X XXX b: XXXXXXXX c: XXXXXXXX
|
||||
XXXXXXXX X X XXX XXXXX</code></pre>
|
||||
<p><code>a</code> usually takes the longest time, while <code>c</code> usually is the
|
||||
fastest.</p>
|
||||
<p>That said, each run is randomized with respect to system time, so
|
||||
|
||||
Reference in new issue
Block a user