Some revisions; section ordering improved; formatting changes.

docs/About.tex

@@ -26,7 +26,9 @@
 in {\itshape A Specimen of the
 Several Sorts of Letter Given to the University by Dr. John Fell,
 Sometime Lord Bishop of Oxford. To Which Is Added the Letter Given by
-Mr. F. Junius} (Oxford, 1693).
+Mr. F. Junius} (Oxford, 1693).\footnote{There is a facsimile of this
+work at the
+\href{https://digital.bodleian.ox.ac.uk/objects/876b73f0-3e03-41c1-9fd1-0688a1785561/}{Digital Bodleian}.}
 
 Junicode has two distinct Greek faces. The first, newly designed to harmonize with the roman face, is
 up\-right and modern. The other, accompanying the italic face, is based on type designed by Alexander

docs/GettingStarted.tex

@@ -58,7 +58,10 @@ \chapter{Getting Started with Junicode}\hypertarget{GettingStarted}{}
 
 The static version of Junicode has five weights and five widths, which are combined in many ways
 for a total of nineteen styles in
-both roman and italic. It is not necessary to install all of these; in fact,
+both roman and italic.\footnote{Several of the twenty-five possible combinations
+(e.g. {\lightexp light expanded})
+have been omitted as unlikely to be useful; however, these can be accessed via the variable font.}
+It is not necessary to install all of these; in fact,
 your life will be simplified (font menus easier to navigate) if you
 make a selection. You will probably want the traditional Regular, Bold, Italic, and Bold
 Italic fonts, but you should survey the styles displayed in the Specimen
@@ -118,8 +121,9 @@ \chapter{Getting Started with Junicode}\hypertarget{GettingStarted}{}
 To position a mark correctly over a base character, first enter the base,
 followed by the mark or marks.
 The sequence \textbf{m} + \textbf{◌ᷙ} (\unic{U+1DD9})
-will make \textbf{mᷙ}; \textbf{y} + \textbf{◌̄} (\unic{U+0304}) + \textbf{◌̆} (\unic{U+0306}) will make \textbf{ȳ̆};
-\textbf{e} + \textbf{◌̣} (\unic{U+0323}) + \textbf{◌ᷠ} (\unic{U+1DE0}) will make \textbf{ẹᷠ}.
+will make \textex{mᷙ};
+\mbox{\textbf{y} + \textbf{◌̄}} (\unic{U+0304}) + \textbf{◌̆} (\unic{U+0306}) will make \textex{ȳ̆};
+\textbf{e} + \textbf{◌̣} (\unic{U+0323}) + \textbf{◌ᷠ} (\unic{U+1DE0}) will make \textex{ẹᷠ}.
 
 More than sixteen hundred characters in Junicode can only be accessed via OpenType features—that is,
 by way of the programming built into the font—and many others \textit{should} be

docs/JunicodeManual.sty

@@ -65,8 +65,8 @@
     SizeFeatures={
       {Size={-8.5},      RawFeature={axis={wght=550,wdth=118}}},
       {Size={8.6-10.99}, RawFeature={axis={wght=475,wdth=114}}},
-      {Size={11-21.59},  RawFeature={axis={wght=400,wdth=111}}},
-      {Size={21.6-},     RawFeature={axis={wght=352,wdth=98}}}
+      {Size={11-21.59},  RawFeature={axis={wght=450,wdth=111}}},
+      {Size={21.6-},     RawFeature={axis={wght=372,wdth=98}}}
     },
   },
   BoldFeatures={
@@ -174,6 +174,15 @@
     {Size={22-},       RawFeature={axis={wght=301,wdth=100}}}
   },
 ]
+\setfontface\lightexp{JunicodeVF-Roman.ttf}[
+  RawFeature={mode=harf},
+  SizeFeatures={
+    {Size={-8.5},      RawFeature={axis={wght=300,wdth=125}}},
+    {Size={8.5-11},    RawFeature={axis={wght=300,wdth=125}}},
+    {Size={11-22},     RawFeature={axis={wght=300,wdth=125}}},
+    {Size={22-},       RawFeature={axis={wght=300,wdth=125}}}
+  },
+]
 %\newfontface\medium{Junicode SmExp Medium}
 \setfontface\medium{JunicodeVF-Roman.ttf}[
   RawFeature={mode=harf},

docs/Record_Interpreter_notes.tex

@@ -28,7 +28,7 @@ \section{A preliminary note on transcription}
 screen readers will misinterpret it. To solve one problem (that of visual representation), you may well have introduced
 a host of far more serious problems.
 
-Fortunately, Junicode offers a solution for this particular problem. The OpenType feature \textbf{cv63} substitutes for
+Fortunately, Junicode offers a solution for this particular problem. The OpenType feature \textSourceText{cv63} substitutes for
 the yogh a character that \textit{looks} like the ezh but is semantically a yogh and therefore will be
 handled correctly by applications. But neither Junicode nor any other font can solve every problem of this kind.
 Sometimes you will have to call to mind the important principle stated above: \textit{A transcript is not a
@@ -37,25 +37,25 @@ \section{A preliminary note on transcription}
 
 This document concerns the transcription of texts in Latin (and to some extent, other archaic languages, e.g. Old and
 Middle English, Old French). It is long-standing custom, when transcribing certain kinds of documents, to retain marks
-of abbreviation---for example, the \textbf{\hlig{\char"0A753p\char"0363}} you may find in a manuscript or printed edition representing
+of abbreviation---for example, the \textex{\hlig{\char"0A753p\char"0363}} you may find in a manuscript or printed edition representing
 the word \textit{propterea}. This is okay---and Junicode can help with the task. But when dealing with the
 abbreviations, punctuation, and diacritics of an old text it is more important than ever that you use semantically
 correct characters for your transcription, as this will help readers who already face significant challenges.
 
-For example, the abbreviation \textbf{\hlig{\char"0A753p\char"0363}} as printed here consists of an underlying sequence of Unicode
-characters: \textbf{\char"0A753} (\unic{U+A753}, the common abbreviation for \textit{pro}) + \textbf{p} + \textbf{\char"25CC\char"0363}
-(\unic{U+0363}, the combining small \textit{a}). The OpenType feature \textbf{hlig} (Historical Ligatures) has been
+For example, the abbreviation \textex{\hlig{\char"0A753p\char"0363}} as printed here consists of an underlying sequence of Unicode
+characters: \textex{\char"0A753} (\unic{U+A753}, the common abbreviation for \textit{pro}) + \textex{p} + \textex{\char"25CC\char"0363}
+(\unic{U+0363}, the combining small \textit{a}). The OpenType feature \textSourceText{hlig} (Historical Ligatures) has been
 applied to this sequence, changing its appearance but not its underlying value. That underlying value is intelligible
 to computer applications in the sense that they can recognize each character.
 
-This doesn't mean, though, that computer programs can correctly interpret \textbf{\hlig{\char"0A753p\char"0363}} as
+This doesn't mean, though, that computer programs can correctly interpret \textex{\hlig{\char"0A753p\char"0363}} as
 \textit{propterea}. Many (probably \textit{most}) Latin abbreviations are ambiguous: this one,
 for example, can mean \textit{propterea} or \textit{propria}. Some abbreviations (most
-notoriously \textbf{\char"25CC\char"035B} \unic{U+035B}) can mean many things, depending on context. It takes a human being with a
+notoriously \textex{\char"25CC\char"035B} \unic{U+035B}) can mean many things, depending on context. It takes a human being with a
 knowledge of Latin to interpret them correctly.
 
 So another way you can add value in your transcript is by interpreting abbreviations like
-\textbf{\hlig{\char"0A753p\char"0363}} and
+\textex{\hlig{\char"0A753p\char"0363}} and
 supplying expansions of them. Fortunately, systems for representing texts often offer ways to handle this task
 gracefully. For example, in a TEI (Text Encoding Initiative) text, you would use this construction:\\[1ex]
 
@@ -74,14 +74,15 @@ \section{A preliminary note on transcription}
 
 \section[Common combining marks]{Common combining marks}
 A \textbf{combining mark} is a character that combines with another character (called the \textbf{base}) to form a
-character with accent (e.g. \textbf{\'e}) or an abbreviation (e.g. \textbf{\cvd[1]{81}{p\char"035B}} for \textit{prae}).
+character with accent (e.g. \textex{\'e}) or an abbreviation (e.g. \textex{\cvd[1]{81}{p\char"035B}} for \textit{prae}).
 Unicode and the Medieval Unicode Font Initiative (MUFI) offer code points for many precomposed combinations of base +
 combining mark, but it is also possible to place any mark over any base character by entering first the base and then
 the combining mark. It is also possible to place a combining mark over another combining mark. For example, to produce
-\textbf{\cvd[32]{84}{q\char"0363\char"0304}}, enter this sequence: q (\unic{U+0071}) + \unic{U+0363} + \unic{U+0304}.
+\textex{\cvd[32]{84}{q\char"0363\char"0304}}, enter this sequence: q (\unic{U+0071}) + \unic{U+0363} + \unic{U+0304}.
 
 Junicode 2 contains many variants of combining marks: for example the curly zigzag \cvd[1]{81}{\char"25CC\char"035B} is a variant of
-Unicode's angular zigzag {\char"25CC\char"035B} (\unic{U+035B}), produced by applying the OpenType feature \textbf{cv81[2]} to \textbf{both the base character and the combining mark}. Sometimes the combination of base + combining mark + OpenType
+Unicode's angular zigzag {\char"25CC\char"035B} (\unic{U+035B}), produced by applying the OpenType feature \textSourceText{cv81[2]} to
+\textbf{both the base character and the combining mark}. Sometimes the combination of base + combining mark + OpenType
 feature will not produce the desired effect. When this happens, place \unic{U+034F} (a special invisible combining mark,
 included in Unicode for exactly this purpose) between the base and the (visible) mark.\\
 
@@ -91,11 +92,11 @@ \section{A preliminary note on transcription}
 \textit{dampna}.
 \end{quote}
 The combining macron can also be applied above superscripts and combining marks. Apply the OpenType feature
-\textbf{cv84[33]} for a narrower macron:
+\textSourceText{cv84[33]} for a narrower macron:
 \begin{quote}
 \cvd[32]{84}{antiqua\char"034F\char"0304} \textit{antiquam}; \cvd[32]{84}{q\char"0363\char"0304} \textit{quam}.
 \end{quote}
-For the superscript \textit{a}, use the OpenType feature \textbf{sups} (see r. below).\\[1ex]
+For the superscript \textit{a}, use the OpenType feature \textSourceText{sups} (see r. below).\\[1ex]
 
 \noindent\secletter{b.}\ \ For a straight stroke through a tall letter, use the \textsc{combining short stroke overlay} (\unic{U+0335}): \textex{f\char"0335\ d\char"0335\ l\char"0335}. But Unicode also has precomposed versions of
 \textex{d}, \textex{l} and other characters \mbox{with} stroke, e.g.
@@ -127,19 +128,19 @@ \section{A preliminary note on transcription}
 \textit{Record Interpreter} and the \textit{Statutes} is a gothic variant of this, which MUFI
 encodes as \unic{U+F1C8} (the curly form zigzag). However, because for technical reasons many applications will not position
 the MUFI character correctly over the base, that code point should be avoided. The best way to access this variant is
-to apply \textsc{\textbf{cv81[2]}} to \unic{U+035B}, as here:
+to apply \textSourceText{cv81[2]} to \unic{U+035B}, as here:
 \begin{quote}
 \cvd[1]{81}{deb\char"035Be \textit{debere}; int\char"035B\ \textit{inter}; f\char"035B\hspace{0.2em}r\=u \textit{ferrum}; gn\char"035Bo
 \textit{generatio}; p\char"035B; \textit{prae}; seru\char"035Be \textit{servire}}.
 \end{quote}
 The curly form of the combining zigzag may be attached to any letter, and it may change shape depending on the letter it
-is attached to (including caps, for which use the \textbf{case} feature, and small caps:
-\cvd[1]{81}{A\char"035B B\char"035B \textsc{c\char"035B
-d\char"035B\hspace{0.2em}}}).\\[1ex]
+is attached to (including caps, for which use the \textSourceText{case} feature, and small caps:
+\textex{\cvd[1]{81}{A\char"035B B\char"035B \textsc{c\char"035B
+d\char"035B\hspace{0.2em}}}}).\\[1ex]
 
 \noindent\secletter{g.}\ \ All letters a--z, and several others too, have combining forms.
 You may access these via their code points, when they are standard Unicode, via the
-\textbf{\textsc{cv84}} feature, or via
+\textSourceText{\textsc{cv84}} feature, or via
 Junicode's special entity references. For details, see \hyperlink{ss10}{4.10.3, Character Entities
 for Combining Marks}.
 \begin{quote}
@@ -153,7 +154,7 @@ \section{Spacing characters}
 \textit{competentes}; inf\char"0A76D\ \textit{infortunium}.
 \end{quote}
 This character will sometimes ligature with the preceding letter. The italic version differs from the roman
-stylistically (\textit{for\char"0A76D\ o\={m}\char"0A76D\ \char"0A76Ft\char"0A76D\ inf\char"0A76D}), but it will be
+stylistically (\ \textex{\textit{for\char"0A76D\ o\={m}\char"0A76D\ \char"0A76Ft\char"0A76D\ inf\char"0A76D}}), but it will be
 intelligible to informed readers.\\[1ex]
 
 \noindent\secletter{i.}\ \ There are two characters for \textit{{}-us} in Unicode:
@@ -165,13 +166,14 @@ \section{Spacing characters}
 \textit{postea}; p\char"0A770\ \textit{post}.}
 \end{quote}
 \noindent\secletter{j.}\ \ The three-like sign is the \textsc{et sign} (\char"25CC\char"0A76B, \unic{U+A76B}, also used for
-\textit{us}{}---do not confuse this with Middle English yogh: \textex{\char"021D}, \unic{U+021D}):
+\textit{us} in the Latin ending \textit{-ibus}). Do not use the numeral three (\textex{3})
+or the Middle English yogh (\textex{\char"021D}, \unic{U+021D}):
 \begin{quote}
 quib\char"0A76B\ \textit{quibus}; lic\char"0A76B\ \textit{licet}; s\char"0A76B\ \textit{sed}.
 \end{quote}
 \noindent\secletter{k.}\ \ For \textit{{}-rum} the Unicode \textsc{rum rotunda} (\unic{U+A75D}) is like the one in MUFI/Junicode.
 The one in the \textit{Record Interpreter} and \textit{Statutes} is a late stylized version of
-this. Use \unic{U+A75D} and apply OpenType feature \textsc{\textbf{cv80}} to obtain the correct shape:
+this. Use \unic{U+A75D} and apply OpenType feature \textsc{\textSourceText{cv80}} to obtain the correct shape:
 \begin{quote}
 \cvd{80}{a\~{i}a\char"0A75D\ \textit{animarum}; co\char"0A75Dpere \textit{corrumpere}; beato\char"0A75D\
 \textit{beatorum}}.
@@ -201,9 +203,9 @@ \section{Spacing characters}
 \char"0A757\ \textit{quod}; \char"0A757d \textit{quid}; \char"0A757b\char"0A76B\ \textit{quibus}.
 \end{quote}
 \noindent\secletter{q.}\ \ For \textit{quae}, \textit{que}, use \textex{q}
-followed by \textsc{et} (\unic{U+A76B}) with or without \textbf{hlig}: \textex{q\char"0A76B}
-\textex{\hlig{q\char"0A76B}}. For the semicolon-like \textsc{et} sign (\textbf{\cvd{83}{q\char"0A76B}}), use
-\textbf{cv83[1]}; for the subscripted version (which can also form a ligature via \textbf{hlig}), use \textbf{cv83[2]}:
+followed by \textsc{et} (\unic{U+A76B}) with or without \textSourceText{hlig}: \textex{q\char"0A76B}
+\textex{\hlig{q\char"0A76B}}. For the semicolon-like \textsc{et} sign (\textex{\cvd{83}{q\char"0A76B}}), use
+\textSourceText{cv83[1]}; for the subscripted version (which can also form a ligature via \textSourceText{hlig}), use \textSourceText{cv83[2]}:
 \textex{\cvd[1]{83}{q\char"0A76B\ \hlig{q\char"0A76B}}}.\\[1ex]
 
 \noindent\secletter{r.}\ \ All of the letters a-z are available in superscript form. Access with the \textex{sups}
@@ -213,8 +215,8 @@ \section{Spacing characters}
 \end{quote}
 The basic Latin letters a--z have anchors that allow you to position combining marks over them (see a. above)\\[1ex]
 
-\noindent\secletter{s.}\ \ Tironian \textsc{et} sign \char"204A\ \unic{U+204A}, cap \char"2E52\ \unic{U+2E52}. With \textbf{cv69[1]} \cvd{69}{\char"204A\char"2E52}; with
-\textbf{cv69[2]} \cvd[1]{69}{\char"204A\char"2E52}.\\[1ex]
+\noindent\secletter{s.}\ \ Tironian \textsc{et} sign \char"204A\ \unic{U+204A}, cap \char"2E52\ \unic{U+2E52}. With \textSourceText{cv69[1]} \cvd{69}{\char"204A\char"2E52}; with
+\textSourceText{cv69[2]} \cvd[1]{69}{\char"204A\char"2E52}.\\[1ex]
 
 \noindent\secletter{t.}\ \ For \textit{est}, use \textex{\char"223B} \unic{U+223B} \textsc{homothetic}. Use of a mathematical sign for this
 purpose is not ideal, but Unicode offers no better solution.\\[1ex]
@@ -226,7 +228,7 @@ \section{Spacing characters}
 
 \noindent\secletter{w.}\ \ At least one edition uses a spacing version of the \textsc{combining zigzag}
 (\textbf{f.} above).
-Neither Unicode nor MUFI has a matching character: with Junicode, apply \textbf{cv67} to the spacing
+Neither Unicode nor MUFI has a matching character: with Junicode, apply \textSourceText{cv67} to the spacing
 \textsc{macron} (\unic{U+00AF}): \textex{\cvd{67}{\char"25CC\char"00AF}}.
 
 \section[Other formatting]{Other formatting}
@@ -250,7 +252,7 @@ \section{Spacing characters}
 }
 \end{verbatim}
 
-\noindent But the \textbf{hlig} feature, if applied to the whole text, will produce many unwanted effects, so it should be
+\noindent But the \textSourceText{hlig} feature, if applied to the whole text, will produce many unwanted effects, so it should be
 included in a class definition to be used in a <span> applied just to the target sequence:
 \begin{verbatim}
 .que {

docs/Specimens.tex

@@ -191,7 +191,7 @@ \subsection*{Fleurons}
 
 {\small\semiconditalic Junicode contains a number of fleurons (floral
   ornaments) copied from a 1785 Caslon specimen book. Access
-  these via the OpenType feature \hyperlink{SectionD}{ornm}. Fleurons have only one weight and
+  these via the OpenType feature \hyperlink{ornm}{ornm}. Fleurons have only one weight and
   width, and they are the same in roman and italic.}
 
 \begin{center}

docs/encoded-glyphs.tex

@@ -13,5 +13,5 @@ \chapter{Encoded Glyphs in Junicode}\hypertarget{EncodedGlyphs}{}
 
 \displayfonttable[color=blue,title-format=\caption{Encoded Glyphs in Junicode},
 title-format-cont=\caption{Encoded Glyphs in Junicode, \emph{cont.}}, missing-glyph=•,
-missing-glyph-color=blue, range-end=F005F, glyph-width=12pt, hex-digits=head]{Junicode VF}[Renderer=HarfBuzz]
+missing-glyph-color=blue, range-end=F005F, glyph-width=12pt, hex-digits=head]{JunicodeVF-Roman.ttf}[Renderer=HarfBuzz]
 

source/texput.log

@@ -0,0 +1,20 @@
+This is LuaHBTeX, Version 1.16.0 (TeX Live 2023)  (format=lualatex 2023.7.25)  2 DEC 2023 22:57
+ restricted system commands enabled.
+**
+
+! Emergency stop.
+<*> 
+
+End of file on the terminal!
+
+
+
+Here is how much of LuaTeX's memory you used:
+ 7 strings out of 478285
+ 100000,1977958 words of node,token memory allocated 270 words of node memory still in use:
+   1 hlist, 39 glue_spec nodes
+   avail lists: 2:12,3:3,4:1,5:1
+ 20331 multiletter control sequences out of 65536+600000
+ 14 fonts using 591679 bytes
+ 0i,0n,0p,21b,6s stack positions out of 10000i,1000n,20000p,200000b,200000s
+!  ==> Fatal error occurred, no output PDF file produced!