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

+5 -5
View File
@@ -2,7 +2,7 @@
NOTE: this will run the program itself.
```<!---sh-->
``` <!---sh-->
make clobber all
```
@@ -12,7 +12,7 @@ See the [Alternate code](#alternate-code) section below for more details.
## To use:
```<!---sh-->
``` <!---sh-->
./jar.1
```
@@ -26,14 +26,14 @@ This alternate code, which prints something slightly different, is provided as w
NOTE: this will run the program itself.
```<!---sh-->
``` <!---sh-->
make clobber alt
```
### Alternate use:
```<!---sh-->
``` <!---sh-->
./jar.1.alt
```
@@ -43,7 +43,7 @@ NOTE: this will run the program itself.
On many systems the compiler will not allow you to send the object file to
`/dev/tty`. The author suggested:
```<!---sh-->
``` <!---sh-->
cc -c -o /dev/tty jar.1.c
```