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
@@ -1,13 +1,13 @@
## To build:
```<!---sh-->
``` <!---sh-->
make
```
## To use:
```<!---sh-->
``` <!---sh-->
./stewart width_and_height iterations file > file.xbm
convert file.xbm file.png
```
@@ -29,7 +29,7 @@ NOTE: `convert(1)` belongs to [ImageMagick](https://imagemagick.org/index.php).
## Try:
```<!---sh-->
``` <!---sh-->
./try.sh
```
@@ -58,7 +58,7 @@ a reasonably experienced user who can parse formats in their mind. :-)
The program should be run with the following
```<!---sh-->
``` <!---sh-->
./stewart <m> <n> <ifs>
```
@@ -77,7 +77,7 @@ are 3. Wrong arguments will cause the program to bomb out.
#### Example:
```<!---sh-->
``` <!---sh-->
./stewart 1024 1000000 gasket > gasket.xbm
```