eudoxia° [ɪʉ·dɔ·ʃi̯ä, –do·ɕĭä] is an engineer. They serve as the primary architect of the DistressNetwork° project.
+
eudoxia° is an engineer. They serve as the primary architect of the DistressNetwork° project.
DistressNetwork° is a virtual system of multimedia aesthetics, and a repository of associated digital artefacts. Select works thereof are published and documented within the distress.network domain under a copyleft license.
@@ -91,17 +92,17 @@ Level Three
InlineMath
as well)
-
“Ünicøde” Test
+
“Ünicøde” Test
(this seems to break the table of contents sometimes)
-
Paragraph Test
+
Paragraph Test
In mathematics, computer science, and linguistics, a formal language consists of words whose letters are taken from an alphabet and are well-formed according to a specific set of rules. The alphabet of a formal language consist of symbols, letters, or tokens that concatenate into strings of the language. Each string concatenated from symbols of this alphabet is called a word, and the words that belong to a particular formal language are sometimes called well-formed words or well-formed formulas. A formal language is often defined by means of a formal grammar such as a regular grammar or context-free grammar, which consists of its formation rules.
The field of formal language theory studies primarily the purely syntactical aspects of such languages—that is, their internal structural patterns. Formal language theory sprang out of linguistics, as a way of understanding the syntactic regularities of natural languages. In computer science, formal languages are used among others as the basis for defining the grammar of programming languages and formalized versions of subsets of natural languages in which the words of the language represent concepts that are associated with particular meanings or semantics.
A lightweight, extensible literate programming tool.
-
Overview
+
Overview
This tool consists of two programs, tangle and weave, both of which accept an input file from stdin and write output to stdout. There are no command-line arguments or other sources of input data. The literate programming interface is language-agnostic with respect to both the source code language and the document formatting language used.
-
Usage
+
Usage
These programs are intended to be intermediary text processing functions, used as components within build automation routines or shell scripts. The build processes for this tool itself, build.sh and gen-docs.sh, serve as example use cases.
A literate programming file consists of plain text sections, code sections, and output configuration commands. Inclusion of the top-level code section, named *, is mandatory within input to tangle, and certain configuration commands are mandatory within input to weave, described in a later section.
-
Section Commands
+
Section Commands
Code sections are created as follows:
@@ -84,7 +86,7 @@
References may be prepended by any amount of whitespace, whereas other commands must be placed at the immediate start of the line.
-
Configuration Commands
+
Configuration Commands
These commands define the format of the code sections and references as they would appear in the output of weave, written as follows:
@@ -124,7 +126,7 @@
@@, which represents the name of the current section being defined, if it occurs within the format string for @start, @add, or @end, or the name of the section being referenced, if it occurs within the format string for @ref.
-
Literate Source Code
+
Literate Source Code
The source code of this tool is rendered as a set of literate program documents, listed below.
The text generation routine performed by weave does not verify the correctness of the section commands within the input file; as such, its output upon receiving malformed input should be considered undefined behaviour. It is therefore recommended to pass newly created or modified files into tangle first, which performs the necessary input validation.
@@ -143,7 +145,7 @@
Attempting to use the Texinfo typesetting language in conjunction with this tool results in namespace collisions with multiple command names.
-
Future Work
+
Future Work
The treatment of whitespace within formatting and configuration commands is currently rather strict, as no trimming of leading or trailing whitespace around the command contents is applied. This may be changed for the sake of convenience, at the expense of added parsing complexity.
A collection of tools for the maintenance of this website.
-
Overview
+
Overview
These scripts must be executed from within their residing directory only, and depend on adjacent files within it in order to function. For convenience it is recommended to create symlinks within this directory to all website directories under maintenance.
The input file may begin with metadata key-value declarations, as specified by lowdown(5). md.sh recognizes and formats the following:
@@ -86,7 +88,7 @@
The table of contents may produce erroneous links if two headers within the page have identical names.
-
Math Rendering
+
Math Rendering
The rendering of LaTeX math mode expressions given within input files may be enabled by adding the m option. This depends on an installation of KaTeX via npm.
@@ -109,7 +111,7 @@
./plain.sh <input txt> <output html>
-
Page Title
+
Page Title
The HTML page title may be specified within the input document using the following declaration: