Characters that killed a render, what may sit next to a klammer, and ref/

A character written in the ^...^ mnemonic form -- ^oe^, ^zz^, ^hello^ --
used to kill ktext outright: no message, no output, and an exit status
that looked like a crash because it was one.  Only the forms that happen
to spell hexadecimal digits escaped, and they were right by luck rather
than by reading.  Any caret form that names no character is now a located
error that quotes what was written.

A klammer may now sit inside square brackets and braces as it already
could inside parentheses, and may be followed by the punctuation that
ends a sentence: [@i word@], {@b word@}, @i word@'s.  The rule is a fixed
list of characters, because none of them can occur inside a klammer name
and so none of them is ambiguous next to a delimiter.  A letter still
cannot: "x@" is the named closing delimiter, so a letter before "@" has
two readings and no rule can separate them.

The abbreviations an author writes -- the hyphen form @i-word, a klammer
glued to its neighbouring punctuation -- are now recognised as author
conveniences only.  They are not applied to @@ definitions or @@@ system
commands, which are written by someone who needs no such shorthand and
whose forms are already whole.

Also fixed, each of them silent: an exported shell function in the
environment broke every @eval in the document; a line break written with
@nl was destroyed when it passed through a klammer that generates a
table, printing as \textbackslash{}newline in the finished PDF; and
"kdesc --coverage" shortened its file column by comparing the spelling of
a path rather than the path, so a klammer set reached by a symbolic link
showed a full path where its neighbours showed a short one.

New in the distribution: ref/, a small klammerset that describes the
Klammermachine's own tables in Klammertext.  It currently provides the
character tables -- the diacritics and the extended Latin letters -- as
klammers that render to any target, so the documentation of what can be
written cannot drift from what the machine accepts.  It is early, and
will grow.

The Klammertext taxonomy now has a section on targets, describes the
@@@klammerset system command alongside the other three, and states the
precedence of "^" -- what a caret means before a letter, a digit, a
punctuation character, and a quote, in one ordered list.

(from dev 6594c7ff8c1f)

mac/character.h

@@ -13,6 +13,18 @@
 
 #include "locator.h"
 
+inline
+std::string klammertext_special_characters { "@|*^#" };
+
+inline
+std::string encoding_marker { "UU" };
+
+inline
+std::string diacritic_symbols = "-'`h~\"cbrdwa";
+
+inline
+std::string diacritic_symbols_order = "'`h~\"c-brdwa";
+
 // ^UUUU^ — a Unicode code point in hex, 4 to 6 digits (^263A^ is the BMP,
 // ^13000^ EGYPTIAN HIEROGLYPH A001, ^10FFFD^ the top of the range), or a
 // single digit.  Lengths 2-3 are NOT accepted: two- and three-letter
@@ -131,7 +143,7 @@ std::string encode(const std::string& s, const Locator& loc);
 // UTF-8 encoding of one code point (to U+10FFFF; surrogates and values
 // above the range yield an "Invalid Unicode: N" text).  Used by the
 // character tables here and by the ^UUUU UUUU ...^ sequence pass
-// (process_unicode_sequences in katom_list.cpp).
+// (process_unicode_sequences in katom_process.cpp).
 std::string utf8char(int cp);
 
 // Whether cp may be written in a ^...^ form: within the Unicode range,
@@ -143,8 +155,9 @@ std::string utf8char(int cp);
 bool valid_codepoint(int cp);
 std::string invalid_codepoint_reason(int cp);
 
-void diacritics_examples(const std::string& kt_filename = "");
-void extended_latin_examples(const std::string& kt_filename = "");
+// void diacritics_examples(const std::string& kt_filename = "");
+// void extended_latin_examples(const std::string& kt_filename = "");
+
 void pinyin_examples(const std::string& kt_filename = "");
 void unicode_examples(const std::string& kt_filename = "");