Updated docs for 2.003.

docs/Feature_Reference.tex

@@ -72,7 +72,7 @@ \section{Introduction}
 e.g. \textex{ȯ́} \textUName{latin small letter o with dot above and acute}, where the
 acute appears beside the dot instead of above. This and other characters like it should still be entered as a sequence
 of base character + marks (here \textex{o}, \textUName{combining dot above} \unic{U+0307},
-\textUName{combining acute} \unic{U+0301}). Junicode will position the marks correctly.
+\textUName{combining acute} \unic{U+0301}). Junicode will position the marks in the manner prescribed by MUFI.
 \item Characters for which a base character (a Unicode character to which it can be linked) cannot be identified, or for
 which there may be an inconsistency in the MUFI recommendation. These include:
 
@@ -1352,8 +1352,8 @@ \subsection{\textSourceText{hlig} -- Historic Ligatures}
 {\color[rgb]{0.38039216,0.09019608,0.16078432}
 \revthorn{{\th}{\textcompwordmark}r$\rightarrow ${\th}r}}
 
-{\color[rgb]{0.38039216,0.09019608,0.16078432}
-\revthorn{{\th}{\textcompwordmark}s$\rightarrow ${\th}s}}
+%{\color[rgb]{0.38039216,0.09019608,0.16078432}
+%\revthorn{{\th}{\textcompwordmark}s$\rightarrow ${\th}s}}
 
 {\color[rgb]{0.38039216,0.09019608,0.16078432}
 \revthorn{{\th}{\textcompwordmark}ẝ$\rightarrow ${\th}ẝ}}
@@ -1369,8 +1369,7 @@ \subsection{\textSourceText{hlig} -- Historic Ligatures}
 
 \subsection{\textSourceText{dlig} --
 Discretionary Ligatures}
-Produces lesser-used ligatures, but also roman numbers, e.g.
-{\addfontfeature{Ligatures=Rare}ii, II, xi, XI}. The lesser-used ligatures:
+Produces lesser-used ligatures:
 \textex{\textcolor[rgb]{0.5529412,0.15686275,0.11764706}{\addfontfeature{Ligatures=Rare}ct, ſp, str, st, tr, tt, ty}}.
 
 \subsection{\textSourceText{ss17} -- Rare

docs/GettingStarted.tex

@@ -67,6 +67,11 @@ \chapter{Getting Started with Junicode}\hypertarget{GettingStarted}{}
 styles for main text, several SemiExpanded styles for footnotes, and
 SemiCondensed for titles.
 
+Junicode’s static fonts come in two types, TrueType (files with a .ttf extension) and
+CFF (files with an .otf extension). These are functionally identical, but they may look
+subtly different on your computer’s screen because of the different technologies used to
+render glyphs. Choose the one you find most appealing.
+
 With around 5,000 characters, Junicode is a large font. Finding the things you
 want in a collection that size can be a challenge, and then entering them in your
 documents is another challenge. This document will help, but it
@@ -135,8 +140,10 @@ \chapter{Getting Started with Junicode}\hypertarget{GettingStarted}{}
 \href{https://www.libreoffice.org/}{LibreOffice Writer}, all major browsers
 (Firefox, Chrome, Safari and Edge), and
 the typesetting programs {\LuaLaTeX} and {\XeLaTeX}. Adobe InDesign supports
-OpenType features only partially, but provides access to all of Junicode's characters
-through its own interface.
+OpenType features only partially, but all features can be accessed via
+Roland Dreger’s \href{https://github.com/RolandDreger/open-type-features}{open-type-features}
+script, and InDesign provides access to
+all of Junicode's characters via its “Glyphs” dialog.
 
 Microsoft Word, unfortunately, provides only limited support for OpenType
 features. It supports the \hyperlink{req}{Required Features} discussed below, and also

docs/JunicodeManual.tex

@@ -13,7 +13,7 @@
 \huge \centering the font for medievalists \\[1cm]
  \Huge\centering {\color{myRed}} \\[1cm]
  \huge\centering {\stditalic specimens and user manual} \\[1ex]
- \Large\centering{\regular for version 2.002}\\
+ \Large\centering{\regular for version 2.003}\\
 \vfill
 {\color{myRed}}
 \end{titlepage}