improve how markdown code language is commented

We added a space between the markdown triple code mark
and language that was enclosed in HTML comments.

So a line of the form:

````
```<!---c--->
````

became:

````
``` <!---c--->
````

This was done to **help** some code see that the HTML comment
string was not a markdown code specifier.   Not all code
understands this after this changed.  For example, `pandoc(1)`
still forms HTML classes of the form "&lt;!---c--&gt;"
when it encounters the above mentioned change.

We also fixed a problem with `2019/dogon/README.md` regarding
a markdown code block.

We also fixed a problem with `2020/yang/README.md` regarding
a markdown code block.
This commit is contained in:
Landon Curt Noll committed 2024-04-12 11:45:50 -07:00
1 parent c549f6585e
commit 3ddbac9e6b
357 files changed
+2432 -2399

No files matched your search

+9 -9
View File
@@ -1,6 +1,6 @@
## To build:
```<!---sh-->
``` <!---sh-->
make all
```
@@ -13,13 +13,13 @@ code](#alternate-code) below for details.
First, you must make sure that `first` is made first (even though `make all`
should make first first :-) ):
```<!---sh-->
``` <!---sh-->
make first
```
Second:
```<!---sh-->
``` <!---sh-->
# get help:
echo help | cat third help.th - | ./first
@@ -29,7 +29,7 @@ Second:
Third:
```<!---sh-->
``` <!---sh-->
cat third help.th - | ./first
```
@@ -50,7 +50,7 @@ Fourth:
## Try:
```<!---sh-->
``` <!---sh-->
./try.sh
```
@@ -63,7 +63,7 @@ fix that the author notes in their remarks.
### Alternate build:
```<!---sh-->
``` <!---sh-->
make alt
```
@@ -75,7 +75,7 @@ Use `buzzard.2.alt` as you would `buzzard.2` above.
### Alternate try:
```<!---sh-->
``` <!---sh-->
./try.alt.sh
```
@@ -125,7 +125,7 @@ Do not expect to be able to do anything interesting with `first`.
To do something interesting, you need to feed `first` the file
[third](third) first. In unix, you can do
```<!---sh-->
``` <!---sh-->
cat third help.th - | ./first
```
@@ -226,7 +226,7 @@ When you get the `Ok.` message from `third`, try out some sample
you in a normal way. It only prints `'Ok.'` after you define a word).
```<!---sh-->
``` <!---sh-->
2 3 + . cr
```