Merge pull request #1275 from xexyl/1990-tbr-alt

1990/baruch/README.md

@@ -38,10 +38,10 @@ Why is there no output?
 
 This alternate code is for the [very few](https://en.wikipedia.org/wiki/0)
 [users](https://en.wikipedia.org/wiki/Microsoft_Windows)
-[here](https://www.ioccc.org) who will need it but nonetheless if you're using
+[here](https://www.ioccc.org) who will need it. Nonetheless if you're using
-Turbo-C or MSC, the code is based on the authors' remarks except that the `"
+Turbo-C or MSC, the code is available, based on the authors' remarks except that
-#Q"` string was not changed as that showed worse looking output instead of
+the `" #Q"` string was not changed as that showed worse looking output instead
-improved output though admittedly we have no way to test the compilers in
+of improved output though admittedly we have no way to test the compilers in
 question. YMMV.
 
 
@@ -71,7 +71,7 @@ The goal of this work was to write a program that solves the classic [n-queens
 problem](https://en.wikipedia.org/wiki/Eight_queens_puzzle), with a board size
 of up to 99x99, while keeping the program as short as possible.
 
-The program finds all possibilities to place N chess queens on a NxN
+The program finds all possibilities to place N chess queens on an NxN
 [chessboard](https://en.wikipedia.org/wiki/Chessboard) so that no queen is in
 range of any other queen (not in the same column row or diagonal).  For each
 solution the chess board and the place of the queens is printed to stdout.
@@ -90,9 +90,8 @@ even more simple we used a very limited subset of C:
 
 In short, it contains no C language that might confuse the innocent reader. :-)
 
-This program demonstrates the claim that in C, any program
+This program demonstrates the claim that in C, any program can be written using
-can be written using a single 'for' statement, as long as it is
+a single 'for' statement, as long as it is long enough.
-long enough..
 
 ### For PC users:
 

1990/dds/README.md

@@ -121,7 +121,7 @@ The Speed of DDS-BASIC Interpreter (Version 1.00) relative to Microsoft Advanced
 BASIC 3.31 is approximately 60%.
 
 The code size could be further reduced by doing ugly things like not declaring
-the return type of functions, not freeing memory, `#defin`ing define, and joining
+the return type of functions, not freeing memory, defining define, and joining
 lines.  In its present 1536 character form the program is reasonably portable
 (it may fail to run in a tagged object architecture) and nicely formatted (it
 fits in an `80*25` screen).

1990/pjr/.gitignore

@@ -1,3 +1,4 @@
 pjr
+pjr.alt
 pjr.orig
 prog.orig

1990/pjr/Makefile

@@ -112,8 +112,8 @@ OBJ= ${PROG}.o
 DATA=
 TARGET= ${PROG}
 #
-ALT_OBJ=
+ALT_OBJ= ${PROG}.alt.o
-ALT_TARGET=
+ALT_TARGET= ${PROG}.alt
 
 
 #################

1990/pjr/README.md

@@ -1,11 +1,6 @@
 # Most Unusual Data Structure
 
 Peter J Ruczynski\
-Pyramid Technology Ltd.\
-Pyramid House\
-Solatron Road\
-Farnborough\
-Hants GU14 7PL\
 England, U.K.
 
 
@@ -15,6 +10,10 @@ England, U.K.
 make all
 ```
 
+There is an [alternate version](#alternate-code) that does something different
+that can be used if your compiler is incapable of compiling `X=g()...` in
+`main()`. It can be used for another purpose too.
+
 
 ## To use:
 
@@ -23,23 +22,44 @@ make all
 ```
 
 
-## Judges' remarks:
+## Alternate code:
-
-This program prints out a string.  Can you figure out how
-it is done?
-
-By use of pointers to functions returning a struct of pointers\
-to functions!
 
 Note that some compilers will be unable to compile the expression `X=g()...` in
-main() due to lack of temporary stack space.  One might want to try replacing
+`main()` due to lack of temporary stack space.  One might want to try replacing
-main with:
+`main()` with:
 
 ```c
 main(){X=s().v().o().o().l().S().d().l().i().o().w().N();}
 ```
 
-if this is a problem.
+if this is a problem, which is what this alternate code is.
+
+NOTE: it prints something else and it is what the author suggested one try as
+well.
+
+
+### Alternate build:
+
+
+```sh
+make alt
+```
+
+
+### Alternate use:
+
+```sh
+./pjr.alt
+```
+
+
+## Judges' remarks:
+
+This program prints out a string.  Can you figure out how
+it is done?
+
+By use of pointers to functions returning a struct of pointers
+to functions!
 
 
 ### Spoiler:
@@ -48,32 +68,34 @@ This program prints out the string:
 
 > the quick brown fox jumped over the lazy dog
 
-by use of pointers to functions returning a struct of pointers
-to functions!
-
 
 ## Author's remarks:
 
-Rot13:
 
-    Vg vf fvzcyr gb znxr gur cebtenz cevag bgure fgevatf.  Rnpu
+It is simple to make the program print other strings.  Each
-    nycunorgvpny punenpgre sebz n gb m vf cevagrq bhg nf vgf
+alphabetical character from a to z is printed out as its
-    bccbfvgr:
+opposite:
 
-    	n->m o->l p->k rgp
+```c
+a->z b->y c->x etc
+```
 
-    Gb rapbqr n arj fgevat vachg gur fgevat nf vg vf zrnag gb pbzr bhg:
+To encode a new string input the string as it is meant to come out:
 
-    	K=f().i().b().b().y().F().q().y().v().b().j().A();
+```c
+X=s().v().o().o().l().S().d().l().i().o().w().N();
+```
 
-    Abgr: F() ercerfragf n fcnpr naq A() n arjyvar.  Guvf jvyy abj
+Note: `S()` represents a space and `N()` a newline.  This will now
-    cebqhpr...
+produce...
 
-    	uryyb jbeyq
+```
+hello world
+```
 
-    By the way, there is actually a piece of code which is not used
+By the way, there is actually a piece of code which is not used
-    in the original program! I leave it as an intellectual exercise
+in the original program! I leave it as an intellectual exercise
-    to the reader to find out what it is.
+to the reader to find out what it is.
 
 
 ## Copyright and CC BY-SA 4.0 License:

1990/pjr/pjr.alt.c

@@ -0,0 +1,13 @@
+#include <stdio.h>
+#define A(a) G a();
+#define B(a) G (*a)();
+#define C(a,b) G a() { printf(b); return X; }
+typedef struct F G;A(a)A(b)A(c)A(d)A(e)A(f)A(g)A(h)A(i)A(j)A(k)A(l)A(m)A(n)A(
+o)A(p)A(q)A(r)A(s)A(t)A(u)A(v)A(w)A(x)A(y)A(z)A(S)A(N)void Q();struct F{B(a)B
+(b)B(c)B(d)B(e)B(f)B(g)B(h)B(i)B(j)B(k)B(l)B(m)B(n)B(o)B(p)B(q)B(r)B(s)B(t)B(
+u)B(v)B(w)B(x)B(y)B(z)B(S)B(N)void(*Q)();}X={a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,
+q,r,s,t,u,v,w,x,y,z,S,N,Q};C(a,"z")C(b,"y")C(c,"x")C(d,"w")C(e,"v")C(f,"u")C(
+g,"t")C(h,"s")C(i,"r")C(j,"q")C(k,"p")C(l,"o")C(m,"n")C(n,"m")C(o,"l")C(p,"k"
+)C(q,"j")C(r,"i")C(s,"h")C(t,"g")C(u,"f")C(v,"e")C(w,"d")C(x,"c")C(y,"b")C(z,
+"a")C(S," ")C(N,"\n") void Q(){}main(){X=s().v().o().o().l().S().d().l().i().
+o().w().N();}

1990/stig/README.md

@@ -1,8 +1,6 @@
 # Strangest Abuse of the Rules
 
 Stig Hemmer\
-Norwegian Institute of Technology\
-N-7034 Trondheim-NTH\
 Norway
 
 
@@ -29,7 +27,7 @@ NOTE: that's not a typo or mistake but one can also do:
 ## Judges' remarks:
 
 We changed the alias that the author's suggested alias from a
-C-shell alias to a zsh alias.
+C-shell alias to a Bourne-like shell alias.
 
 Note that `shst.c` is renamed to [stig.c](stig.c) in the distribution.
 
@@ -41,8 +39,8 @@ obfuscation.  This type of entry will not be permitted in future contests.
 ## Author's remarks:
 
 If you like shell programming you may also admire my creative quoting. (I use
-echo to create an alias which when run calls cc with the -D option to create a C
+`echo` to create an alias which when run calls cc with the `-D` option to create
-macro with double quotes in it. ARRRRRGGGHHH!)
+a C macro with double quotes in it. ARRRRRGGGHHH!)
 
 The program is totally portable, but the compile commands are very shell
 specific so don't be TOO mad at me if they don't work for you.

1990/tbr/README.md

@@ -13,6 +13,27 @@ US
 make all
 ```
 
+There is an [alternate version](#alternate-code) to this program.
+
+
+### A note about the fixes of this entry in 2023:
+
+In 2023 it was noticed that in some systems like macOS there was confusing
+output due to a warning at runtime that was interspersed with the output of the
+program. For instance it would show:
+
+```sh
+$ ./tbr
+$ warning: this program uses gets(), which is unsafe.
+```
+
+which kind of hid the prompt. Thus the entry was changed to use `fgets(3)` which
+is referred to later in this file.
+
+Also `exit(3)` returns void but the entry was using it in a binary expression so
+this entry would not compile in modern systems. This fix is also referred to
+below, in the [alternate version](#alternate-code) section.
+
 
 ## To use:
 
@@ -54,14 +75,7 @@ The authors include a section called [BUGS](#bugs) that, because they were
 documented, are not considered bugs as such in the context of the contest.
 
 
-## Judges' remarks:
+## Alternate code:
-
-This program touches on a well known Unix utility, the 6th edition Bourne Shell
-(`/bin/sh`), whose original source was considered to be extremely obfuscated by
-many people (although Steve Bourne might disagree). Did you know that the Bourne
-Shell source was a major inspiration for the formation of the IOCCC back in
-1984?
-
 
 The authors supplied us with a slightly smaller unformatted version
 of the program which we include below:
@@ -79,8 +93,32 @@ r(o,0)D o)D*f):4,wait(0):(o?dup2(*f,0)D*f)D o):*i?1 D
 e(x){x<0?write(2,"?\n$ "-x/4,2),x+1||(exit(1),0):5;}
 ```
 
-It has the `exit()` returns void fix as well as the `gets()` to `fgets()` fix
+and in the [alternate source](tbr.alt.c). It has the `exit()` returns void fix
-applied to it to make it functionally equivalent like the authors intended.
+as well as the `gets()` to `fgets()` fix applied to it to make it functionally
+equivalent like the authors intended.
+
+
+### Alternate build:
+
+```sh
+make alt
+```
+
+
+### Alternate use:
+
+```sh
+./tbr.alt
+```
+
+
+## Judges' remarks:
+
+This program touches on a well known Unix utility, the 6th edition Bourne Shell
+(`/bin/sh`), whose original source was considered to be extremely obfuscated by
+many people (although Steve Bourne might disagree). Did you know that the Bourne
+Shell source was a major inspiration for the formation of the IOCCC back in
+1984?
 
 
 ## Authors' remarks:

1991/dds/README.md

@@ -39,20 +39,6 @@ What happens if you give the program a C program like itself? Try:
 You'll get errors yes but what does the generated file look like? What about
 other types of files?
 
-Please note that if the BASIC file cannot be opened for reading or the output
-file cannot be opened for writing then this program will very likely crash or do
-something funny.
-
-This is supposed to happen.  As is written in the
-[The Jargon File](http://catb.org/jargon/html/F/feature.html):
-
-```
-That's not a bug, that's a feature.
-```
-
-These are a mild nuisance but are considered a feature not a bug. We challenge
-you to fix it for learning if you wish. See also [bugs.md](/bugs.md).
-
 
 ## Judges' remarks:
 

1998/schweikh3/.gitignore

@@ -4,4 +4,5 @@ file2
 file3
 file4
 schweikh3.orig
+samefile
 prog.orig

1998/schweikh3/Makefile

@@ -131,6 +131,7 @@ all: data ${TARGET}
 
 ${PROG}: ${PROG}.c
 	${CC} ${CFLAGS} $< -o $@ ${LDFLAGS}
+	${LN} -sf $@ samefile
 
 # alternative executable
 #

1998/schweikh3/README.md

@@ -1,11 +1,8 @@
 # Most Space Efficient
 
-Jens Schweikhardt\
+Jens Schweikhardt <schweikh@schweikhardt.net>\
-DFN Network Operation Center\
+<http://www.schweikhardt.net>\
-Schlartaeckerweg 3 (Home address)\
+Germany
-D-71384 Weinstadt\
-Germany\
-<http://www.schweikhardt.net>
 
 
 ## To build:
@@ -22,7 +19,7 @@ all your favorite pictures off the Internet or from
 `alt.binaries.pictures.*`, do
 
 ```sh
-find dir -type f -print | ./schweikh3
+find dir -type f -print | ./samefile
 ```
 
 Maybe you will not need to buy another 10 Gb disk to store them.  :-)
@@ -33,7 +30,7 @@ Maybe you will not need to buy another 10 Gb disk to store them.  :-)
 If you're in this winning entry's directory:
 
 ```sh
-find . -type f -print | ./schweikh3
+find . -type f -print | ./samefile
 ```
 
 Notice that the tool finds a duplicate file, that of the man page.
@@ -44,21 +41,17 @@ Notice that the tool finds a duplicate file, that of the man page.
 Try this:
 
 ```sh
-cp schweikh3 file1
+./try.sh
-cp schweikh3 file2
-cp schweikh3.c file3
-ln file3 file4
-
-find . -type f -name 'file?' | ./schweikh3
 ```
 
 This program is not as smart as to detect identity of JPEG files with the same
 picture but with different compression levels. On the other hand compression can
-make it thing look/sound/feel different so these probably aren't duplicates
+make a thing look/sound/feel different so these probably aren't duplicates
 anyway. :-)
 
-NOTE: Some non-gcc compilers that are not fully ANSI standard do not compile
+Some time after this entry won, the Internet Systems Consortium (ISC) added the
-this entry correctly.
+samefile utility to its treasure of software gems! See the author's page about
+the tool as well at <http://www.schweikhardt.net/samefile>.
 
 
 ## Author's remarks:
@@ -66,11 +59,17 @@ this entry correctly.
 The source is expected to conform to IEEE Std 1003.1-1990 ("POSIX").
 Thank God the IEEE does not standardize a coding style...
 
+
 ###    What this program does
 
 This is best explained in the man page. The troff source for this
-man page can be found in the file samefile.1. To render try: `man
+man page can be found in the file samefile.1. To render try:
-./samefile.1`. Otherwise:
+
+```sh
+`man ./samefile.1
+```
+
+Otherwise:
 
 
 **SAMEFILE(1)                User Manuals               SAMEFILE(1)**
@@ -80,21 +79,23 @@ man page can be found in the file samefile.1. To render try: `man
 
    **samefile** - find identical files
 
+
 **SYNOPSIS**
 
-   **./samefile**
+   ./samefile
+   
 
 **DESCRIPTION**
 
-**samefile**  reads  a  list  of file names (one file name per
+`samefile`  reads  a  list  of file names (one file name per
-line) from stdin.  For each file name pair with  identical
+line) from `stdin`.  For each file name pair with  identical
 contents, a line consisting of six tab separated fields is
 output: The size in bytes, two file names,  the  character
 `=`  if the two files are on the same device, `X` otherwise,
 and the link counts of the two files.  The  output
 is sorted in reverse order by size.
 
-samefile uses two stages to give optimum performance.
+`samefile` uses two stages to give optimum performance.
 
 In  the  first  stage,  all  non-plain  files are silently
 ignored (directories, devices,  FIFOs,  sockets,  symbolic
@@ -186,7 +187,7 @@ otherwise.
 
 `find(1)`, `ln(1)`, `rm(1)`
 
-\
+
 ### Why I think it is obfuscated
 
 - The code is commented but this gives only an *extremely* faint clue.

1998/schweikh3/try.sh

@@ -0,0 +1,14 @@
+#!/usr/bin/env bash
+
+make all || exit 1
+
+echo "$ cp -f schweikh3 file1"
+cp -f schweikh3 file1
+echo "$ cp -f schweikh3 file2"
+cp -f schweikh3 file2
+echo "$ cp -f schweikh3.c file3"
+cp -f schweikh3.c file3
+echo "$ ln -f file3 file4"
+ln -f file3 file4
+echo "$ find . -type f -name 'file?' | ./samefile"
+find . -type f -name 'file?' | ./samefile

bugs.md

@@ -474,7 +474,7 @@ emulator to test it) but running the code on the binary itself produces a
 
 # 1985
 
-There was no known bugs and (Mis)features for 1985.
+There are no known bugs and (Mis)features for entries in 1985.
 
 
 # 1986
@@ -493,7 +493,7 @@ the judges and shouldn't be fixed.
 
 # 1987
 
-There was no known bugs and (Mis)features for 1987.
+There are no known bugs and (Mis)features for entries in 1987.
 
 
 # 1988
@@ -1942,7 +1942,7 @@ If you want to try and fix this (mis)feature, you are welcome to try.
 
 # 2015
 
-There was no known bugs and (Mis)features for 2015.
+There are no known bugs and (Mis)features for entries in 2015.
 
 
 # 2016

thanks-for-fixes.md

@@ -900,26 +900,6 @@ links and the user executes does that make the compiler the jury, the linker the
 judge and user the executioner? :-)
 
 
-## [1990/dg](1990/dg/dg.c) ([README.md](1990/dg/README.md]))
-
-Cody fixed this for modern systems. There were two problems to be resolved.
-
-One can no longer do:
-
-```c
-#define d define
-
-#d b12(x) 12 x
-
-/* etc. */
-```
-
-so the use of `#d` is now instead `#define` (the macro was originally deleted
-but later Cody added it back to make it more like the original).
-
-The second problem was suggested by the judges at the time of judging, to do
-with if the C preprocessor botches single quotes in cpp expansion.
-
 ## [1990/dds](1990/dds/dds.c) ([README.md](1990/dds/README.md]))
 
 Yusuke and Cody in conjunction fixed this for modern systems (both fixed a
@@ -945,6 +925,27 @@ to read from another file and in this place nothing was changed.
 
 With these improvements the entry looks much more like the original!
 
+
+## [1990/dg](1990/dg/dg.c) ([README.md](1990/dg/README.md]))
+
+Cody fixed this for modern systems. There were two problems to be resolved.
+
+One can no longer do:
+
+```c
+#define d define
+
+#d b12(x) 12 x
+
+/* etc. */
+```
+
+so the use of `#d` is now instead `#define` (the macro was originally deleted
+but later Cody added it back to make it more like the original).
+
+The second problem was suggested by the judges at the time of judging, to do
+with if the C preprocessor botches single quotes in cpp expansion.
+
 ## [1990/jaw](1990/jaw/jaw.c) ([README.md](1990/jaw/README.md]))
 
 Cody fixed the script to work properly in modern environments including paths,
@@ -964,6 +965,13 @@ bugs.md](/bugs.md#1990-jaw) for details.
 NOTE: as `btoa` is not common we used a ruby script from Yusuke.
 
 
+## [1990/pjr](1990/pjr/pjr.c) ([README.md](1990/pjr/README.md]))
+
+Cody added the [alt code](1990/pjr/pjr.alt.c) which was suggested by the judges
+in the case that your compiler cannot compile `X=g()...` but it actually does
+something else and is recommended by the author as well.
+
+
 ## [1990/scjones](1990/scjones/scjones.c) ([README.md](1990/scjones/README.md]))
 
 Yusuke suggested `-ansi` to get the entry to compile due to trigraphs and Cody
@@ -992,8 +1000,10 @@ like the same as the original.
 Additionally, Cody fixed the shortened version provided by the author in the
 same way as the original entry, first the compile fix and then later on making
 it look more like the original by redefining `exit` and also redefining `gets()`
-to be `fgets()` in the same way that the original entry is. This way the alt
+to be `fgets()` in the same way that the original entry is. This way the [alt
-version is equivalent in function, like the author intended, but more compact.
+version](1990/tbr/README.md#alternate-code) is equivalent in function, like the
+author intended, but more compact.
+
 
 ## [1990/theorem](1990/theorem/theorem.c) ([README.md](1990/theorem/README.md]))
 
@@ -1152,7 +1162,11 @@ The key to the string is that it rotates the character by `+1`. This was not
 immediately clear until reading the author's remarks so there was an alt version
 that was something of a kludge, running `make a` instead but that was removed.
 
-Cody also fixed a typo in LANDER.BAS.
+Cody also fixed a typo in LANDER.BAS and made it so that if a file could not be
+opened for reading or a file could not be opened for writing it would not crash.
+The definition of whether that should be a bug to fix or a feature to not fix
+was pondered and changed numerous times and ultimately that problem with this
+entry was fixed. It has not been done in all.
 
 
 ## [1991/fine](1991/fine/fine.c) ([README.md](1991/fine/README.md))
@@ -1541,6 +1555,8 @@ Cody fixed this to not segfault under macOS. The problem was that the function
 pointer `w`, which points to `XCreateWindow()`, did not specify the parameters of
 the function in the pointer assignment.
 
+NOTE: if there is no X server running this program will still crash.
+
 
 ## [1996/westley](1996/westley/westley.c) ([README.md](1996/westley/README.md]))
 
@@ -1589,7 +1605,7 @@ doing:
 ```
 
 Cody also added the [try.sh](1998/schnitzi/try.sh) script to help users try the
-commands (as well as some added by him) we recommended.
+commands that we recommended as well as some added by him.
 
 
 ## [1998/schweikh1](1998/schweikh1/schweikh1.c) ([README.md](1998/schweikh1/README.md]))
@@ -1609,7 +1625,7 @@ So what was wrong with the original?
 
 The call to `freopen()` was incorrect with the second arg (the mode) being
 `5+__FILE__`; it is now `"r"`. (Observe that the mode to the `fopen()`
-call is: `44+__FILE__`. This might seem incorrect and indeed it can be changed
+call is: `43+__FILE__`. This might seem incorrect and indeed it can be changed
 to `"r"` as well but this was not actually necessary so once this was noticed it
 was changed back to the original.)
 
@@ -1667,6 +1683,19 @@ interesting historical explanation and further details and fun, see the
 README.md.
 
 
+## [1998/schweikh3](1998/schweikh3/schweikh3.c) ([README.md](1998/schweikh3/README.md]))
+
+Cody added the [try.sh](1998/schweikh3/try.sh) script to make it easier to try
+the commands that we suggested. One command was not added, that of the to use
+command.
+
+Cody also made the Makefile rule `all` symlink the entry to `samefile` as that
+is the name of the program.
+
+There actually is a web page for the tool and this was added to the author
+information for the entry. It has not been added to any JSON file.
+
+
 ## [2000/anderson](2000/anderson/anderson.c) ([README.md](2000/anderson/README.md]))
 
 Cody changed this entry to use `fgets()` instead of `gets()` to make it safer

tmp/format-headers.sh

@@ -0,0 +1,29 @@
+#!/usr/bin/env bash
+#
+# format-headers.sh - script that formats headers in README.md files so that
+# before a line that starts with '##' (as in '^##') that have specific names
+# there are two blank lines (\n\n).
+#
+# Script written by Landon with minor improvements by Cody Boone Ferguson where
+# now it only acts on files under git control rather than any README.md file in
+# the [0-9]{4} directories.
+#
+
+for i in "$(git ls-files '[0-9][0-9][0-9][0-9]/*README.md')"; do
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(To build):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Bugs and \(Mis\)features):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(To use):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Try):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Original code):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Original build):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Original try):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Original use):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Alternate code):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Alternate build):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Alternate try):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Alternate use):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Judges. remarks):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Author.s remarks):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Authors. remarks):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Copyright and CC BY-SA 4.0 License):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
+done