Landon Curt Noll
4ee4c731f7
While not strictly necessary, replacing the two ASCII tab characters in the markdown copyright comment makes it easier to detect problematic TAB indentation within markdown files. After this commit, only 90 markdown files have leading ASCII TAB characters. And again, while not strictly necessary, we can consider running expand on those 90 markdown files to see what effect that might have on the HTML files they produce. Replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters (the default action of the `expand(1)` tool) might have an negative effect on some HTML formatting where **hack-a-round** formatting was attempted to fix broken indentation caused by problematic ASCII TAB characters. Think of this as a baseline for evaluating leading TAB characters within markdown files. TODO: Consider either using `expand(1)` to replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters AND/OR modifying the appropriate `bin` tool to convert leading ASCII TAB characters into multiples of 8 ASCII SPACE characters.
1.2 KiB
1.2 KiB
To build:
make
To use:
./newbern [file.dat arg]
Try:
./try.sh
Judges' remarks:
The program is formatted using the same font glyphs as the example data file.
Author's remarks:
This is a configurable banner(1)-like program.
Examples:
- To convert a character glyph into a data file:
./newbern char < some_nicely_shaped_text >> data_file
- To print a string using glyphs from a data file:
./newbern data_file a_string
Extra functionality
The program can also act as a Morse encoder, unarguably.
It also has double-super-secret encryption capabilities. Decryption is left as an exercise for the reader.
Portability
The program assumes an ASCII operating environment.
The program is best viewed with tab-stops set to 8.