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

+8 -8
View File
@@ -1,6 +1,6 @@
## To build:
```<!---sh-->
``` <!---sh-->
make
```
@@ -10,14 +10,14 @@ See [Alternate code](#alternate-code) below for the (fun) rationale here.
## To use:
```<!---sh-->
``` <!---sh-->
echo "full spelling of an English cardinal numeral less than a quadrillion" | ./kang
```
## Try:
```<!---sh-->
``` <!---sh-->
./try.sh # try various languages
./en.sh # English 0 through 13
@@ -43,14 +43,14 @@ subtlety of this entry even more.
### Alternate build:
```<!---sh-->
``` <!---sh-->
make alt
```
### Alternate use:
```<!---sh-->
``` <!---sh-->
echo "full spelling of an English cardinal numeral less than a quadrillion" | ./kang.alt
echo vier | ./kang.alt
@@ -61,7 +61,7 @@ subtlety of this entry even more.
### Alternate try:
```<!---sh-->
``` <!---sh-->
./try.alt.sh # try various languages
./en.alt.sh # English 0 through 13
@@ -88,13 +88,13 @@ We've added a linefeed to the print format for convenience.
Can you explain why:
```<!---sh-->
``` <!---sh-->
echo f hundr|./kang
```
correctly reports 500 but:
```<!---sh-->
``` <!---sh-->
echo hundr|./kang
```