add hack-a-round for language specified markdown code blocks

When language is specified in a markdown code block such as:

````
```c
    printf("Hello, world!\n");
```
````

is used, the resulting HTML as produced by `pandoc(1)` combined
with our revised `ioccc.css` is not intent the code block well.

A temporary "_hack-a-round_" is to turn the "markdown code language
specifier" into an HTML comment.  For example:

````
```<!---c-->
    printf("Hello, world!\n");
```
````

This commits turns off existing markdown code language specifiers
for now, while preserving our ability to restore them in the future
when a better  "_hack-a-round_" to the "markdown code language
specifier" problem is found.

The HTML impact if this "_hack-a-round_" is to produce HTML that
looks like this:

```
<pre class="&lt;!---c--&gt;"><code> .. </code></pre>
```

We might be able to create a complex set of classes for each markdown
code language (there won't be very many) in `ioccc.css`, or we might
find a more general CSS (or maybe `pandoc(1)`?) solution.

For now, this hack-a-round will have to do.
This commit is contained in:
Landon Curt Noll committed 2024-04-04 14:50:38 -07:00
1 parent 3919df50fb
commit b66c79254a
700 files changed
+7052 -7056

No files matched your search

+8 -8
View File
@@ -1,6 +1,6 @@
## To build:
```sh
```<!---sh-->
make
```
@@ -22,7 +22,7 @@ For more detailed information see [2014 vik bugs](../../bugs.html#2014_vik).
## To use:
```sh
```<!---sh-->
echo foo | ./prog > audio_file.raw
echo foo | ./prog | mplayer -demuxer rawaudio -
@@ -31,7 +31,7 @@ For more detailed information see [2014 vik bugs](../../bugs.html#2014_vik).
## Try:
```sh
```<!---sh-->
./try.sh
```
@@ -44,7 +44,7 @@ instructions on how to get it to work with Windows.
### Alternate build:
```sh
```<!---sh-->
make alt
```
@@ -59,13 +59,13 @@ Use `prog.alt` as you would `prog` above as well as below.
This program sets a new tone for obfuscation. But do you understand
what it says about obfuscation? Perhaps:
```sh
```<!---sh-->
./prog < prog.c > prog.raw
```
might speak to your coding style? If not, then perhaps:
```sh
```<!---sh-->
./prog < README.md | mplayer -demuxer rawaudio -
```
@@ -87,7 +87,7 @@ Don't forget the last '`-`' as it makes `mplayer(1)` read from `stdin`.
## Convert audio file with Morse signals to text
```sh
```<!---sh-->
./prog e < audio_file.raw
```
@@ -106,7 +106,7 @@ Microsoft compilers add a carriage return to newlines, and to compile the
program with this platform, the following line can be added to `main()` before
any code in order for the program to run correctly:
```c
```<!---c-->
_setmode(_fileno(stdout), 0x8000);
```