teubner (18nov20)

git-svn-id: svn://tug.org/texlive/trunk@56956 c570f23f-e606-0410-a88d-b1316a301751

5 files changed, 184 insertions, 218 deletions

diff --git a/Master/texmf-dist/doc/latex/teubner/README b/Master/texmf-dist/doc/latex/teubner/README
index f1c8b924fc8..1031c6c12d9 100644
--- a/Master/texmf-dist/doc/latex/teubner/README
+++ b/Master/texmf-dist/doc/latex/teubner/README
@@ -1,6 +1,6 @@
-This accompanies the teubner bundle version 4.x dated November 2015 or later.
+This accompanies the teubner bundle version 5.0 dated November 2020 or later.
 
-Copyright 2010-2016 Claudio Beccari
+Copyright 2010-2020 Claudio Beccari
 
 The  bundle contains the files
 
@@ -15,30 +15,36 @@ The bundle is distributed under the LPPL license version 1.3c or any later versi
 
 The bundle has the status of author maintained.
 
-The main purpose of this bundle is to provide classical philologists with some
-means for typesetting their documents that usually contain very specific mark up.
+The main purpose of this bundle is to provide classical philologists with 
+some means for typesetting their documents that usually contain very 
+specific mark up.
 This version allows the typesetter to use both "italic" shapes: the Olga-like
-and the Lipsian-like ones; it complies with the LICR (LaTeX Internal Character
-Representation) of the Greek glyphs that avoid the kerning problems that arise 
-with the ligature mechanism embedded in the LGR encoded default CBfonts; it is 
-compatible with the use of different vector Latin Type 1 fonts; 
-contains new designs for the horizontally stretchable markers, et cetera.
+and the Lipsian-like ones; it complies with the LICR (LaTeX Internal 
+Character Representation) of the Greek glyphs that avoid the kerning problems 
+that arise with the ligature mechanism embedded in the LGR encoded default 
+CBfonts; it is compatible with the use of different vector Latin Type 1 
+fonts; contains new designs for the horizontally stretchable markers, et 
+cetera.
 
 Running pdflatex on the .dtx file produces both the documentation and  
 extracts the byproduct files teubner.sty, teubnertx.sty, teubner.pdf.  
-The readable extended documentation file teubner-doc.pdf is obtained by running 
-pdflatex on the teubner-doc.tex file.
+The readable extended documentation file teubner-doc.pdf is obtained by 
+running pdflatex on the teubner-doc.tex file.
 
 Moreover this teubner package generates on the fly the font description files 
 necessary to use the LGR encoded Greek fonts with some non standard TeX 
-PostScript fonts; for example, it automatically generates the necessary files if using 
-the TX or the PX fonts; with other Type 1 fonts the necessary .fd files require 
-manual intervention, which simply means giving a suitable command from within another 
-open file that loads teubner.
-
-Please, be sure to work with a 2010 updated collection of the CBfonts; with a 2014 
-updated version of the TeX system; with a babel version 3.9g or later; with the 
-language description file greek.ldf version 1.9b or later. The teubner package works also with previous versions of the above pieces of software, but with limited performances.
+PostScript fonts; for example, it automatically generates the necessary 
+files if using the TX or the PX fonts; with other Type 1 fonts the 
+necessary .fd files require manual intervention, which simply means giving 
+a suitable command from within another open file that loads teubner.
+
+Please, be sure to work with a *2010* updated collection of the CBfonts; 
+moreover with a *2019* or later updated version of the TeX system; with a
+babel version 3.9g or later; with the language description file greek.ldf 
+version 1.9b or later; teubner version 5.0 and later patches the 
+modifications of greek.ldf 1.10 so as cope with the ancient Greek numbering 
+system. The teubner package does not work with previous versions of 
+the above pieces of software; it may even produce fatal errors; therefore be sure to work only with a complete and up-to-date TeX system installation.
 
 Claudio Beccari
 claudio dot beccari at gmail dot com
\ No newline at end of file
diff --git a/Master/texmf-dist/doc/latex/teubner/teubner-doc.pdf b/Master/texmf-dist/doc/latex/teubner/teubner-doc.pdf
index 803ba492c40..8e7dd8cca78 100644
--- a/Master/texmf-dist/doc/latex/teubner/teubner-doc.pdf
+++ b/Master/texmf-dist/doc/latex/teubner/teubner-doc.pdf
diff --git a/Master/texmf-dist/doc/latex/teubner/teubner-doc.tex b/Master/texmf-dist/doc/latex/teubner/teubner-doc.tex
index a1ec488d22b..651f46cf2a5 100644
--- a/Master/texmf-dist/doc/latex/teubner/teubner-doc.tex
+++ b/Master/texmf-dist/doc/latex/teubner/teubner-doc.tex
@@ -9,7 +9,7 @@
 %\usepackage{pxfonts}
 \usepackage{mflogo}
 \usepackage[greek,english]{babel}
-\def\workingdate{2016/03/31}% see two lines ahead
+\def\workingdate{2020/11/01}% see two lines ahead
 \usepackage[boldLipsian,10pt,GlyphNames]% <--------  teubner options
            {teubner}[\workingdate]% <--- older versions don't work well
 \usepackage[scaled=0.90]{helvet}
@@ -43,15 +43,15 @@
 \usepackage{multicol}
 \title{\texttt{teubner.sty}%
 \thanks{This paper documents \texttt{teubner.sty} version \fileversion\ of \filedate.}\\
-An extension to the \textsf{greek} option\\ of the \babel\ package}
+A package to extend the \textsf{greek} option\\ of the \babel\ package}
 \author{Claudio Beccari\thanks{\texttt{claudio dot beccari at gmail dot com}}}
-\date{Turin, March 2016}% <---- this is the date of the teubenr-doc document!
+\date{November 2020}% <---- this is the date of the teubenr-doc document!
 \def\comando#1{\expandafter\texttt\expandafter{\string#1}}
 \def\cs#1{\texttt{\char92#1}}
 \def\ARG#1{\texttt{\char123}\meta{#1}\texttt{\char125}}
 \def\meta#1{$\langle${\normalfont\itshape#1}$\rangle$}
 \let\marg\ARG\let\Arg\meta
-\def\brArg#1{\texttt{\char123#1\char125}}
+\def\Marg#1{\texttt{\char123#1\char125}}\let\brArg\Marg
 \def\opt#1{\texttt{[}\meta{#1}\texttt{]}}
 \def\g#1 {\textDidot{#1}}
 \def\l#1 {\textLipsias{#1}}
@@ -74,9 +74,12 @@ An extension to the \textsf{greek} option\\ of the \babel\ package}
 
 \advance\textheight80pt \advance\topmargin-40pt
 
+\providecommand\setfontsize{}
+\DeclareRobustCommand*\setfontsize[2][1.2]{%
+\linespread{#1}\fontsize{#2}{#2}\selectfont}
+
 \begin{document}\errorcontextlines=20
 
-%\expandafter\show\csname ver@greek.ldf\endcsname %%versione del file-opzione
 
 \maketitle
 {\columnseprule=0.4pt
@@ -85,46 +88,30 @@ An extension to the \textsf{greek} option\\ of the \babel\ package}
 \end{multicols}}
 
 \section{Introduction}
-%\begin{sloppypar}
-This package \texttt{teubner.sty} is an extension of the \textsf{greek} option
-of the \babel\ package intended to typeset classical Greek with
-a philological approach. This version 4.x cannot yet typeset the critical
-apparatus as the philologists are used to, but may be this work will continue
-and include also that facility. Apparently it is not incompatible with \textsf{eledmac}, but it may be considered a complement.
-%\end{sloppypar}
+This package \texttt{teubner.sty} is a module that extends the \textsf{greek} option of the \babel\ package intended to typeset classical Greek with a philological approach. This version 4.x cannot yet typeset the critical apparatus as the philologists are used to, but may be this work will continue and include also that facility. Apparently it is not incompatible with \textsf{eledmac}, but it may be considered a complement.
 
 {\tolerance=9999
 This document does not substitute the official package documentation \texttt{teubner.dtx} and its typeset version \texttt{teubner.pdf}; it extends the information contained into those files.\par}
 
 This package is supposed to work with my CB fonts available on the
-Comprehensive \TeX\ Archive Network (\textsc{ctan}); one of the actions of this
-package consists in adding to the default ``italic'' Greek shape another one
-called ``Lispiakos'' in Greece; this name derives from the high quality of the
-fonts used in the printers' shops in the city of Lipsia in the past 100~years
-or so; one of the printer shops that continues printing books for philologists
-(since 1849) is the B.G.~Teubner Verlags\-gesell\-schaft, that publishes the
-collection called ``Bibliotheca Scriptorum Graecorum et Latinorum
-Teubneriana''. The name given to this extension package is in homage to that
-printing company and to its high quality tradition in printing Greek texts.
+Comprehensive \TeX\ Archive Network (\textsc{ctan}); one of the actions of this package consists in adding to the default “italic” Greek shape another one called “Lispiakos” in Greece; this name derives from the high quality of the fonts used in the printers' shops in the city of Lipsia in the past 100~years or so; one of the printer shops that continues printing books for philologists (since 1849) is the B.G.~Teubner Verlags\-gesell\-schaft, that publishes the collection called “Bibliotheca Scriptorum Graecorum et Latinorum Teubneriana”. The name given to this package is in homage to that printing company and to its high quality tradition in printing Greek texts.
 
 This package is generally loaded by default with any complete distribution of the \TeX\ system; in basic distributions it might not be there, but in general it is sufficient to use the distribution facilities for loading it; with MiKTeX, for example one uses the MiKTeX settings and the Package tab. With \TeX\-live it is sufficient to operate with the program \textsf{tlmgr}; and so on.
 
-The problem, if there is one, is to have the full collection of the CB fonts; in partial distributions the scalable PostScript CB fonts are in one size, 10\,pt, and it is necessary to use the \emph{10pt} option in order to have the various enlarged or reduced sizes. For professional work, if the user has a partial \TeX\ system installation, it is necessary to load the \texttt{cbgreek-full} font collection and be sure that the map files are duly upgraded. In case, read your distribution instructions to see how to control and, possibly, how to provide for this upgrade. Please, notice that this very file has been typeset with the \emph{10pt} option in force, so that if you want to typeset it again from source, you need the minimum amount of vector fonts needed by \textsf{pdflatex} to do its job.
+The problem, if there is one, is to have the full collection of the CB fonts; in partial distributions the scalable PostScript CB fonts are in one size, 10\,pt, and it is necessary to use the \emph{10pt} option in order to have the various enlarged or reduced sizes. For professional work, if the user has a partial \TeX\ system installation, it is necessary to load the \texttt{cbgreek-full} font collection and be sure that the map files are duly upgraded. In case, read your distribution instructions to see how to control and, possibly, how to provide for this upgrade. Please, notice that this very document has been typeset with the \emph{10pt} option in force, so that if you want to typeset it again from source, you need the minimum amount of vector fonts needed by \textsf{pdflatex} to do its job.
 
-In any case this \texttt{teubner} extension package makes the CB font collection (full or reduced) directly compatible by construction with both the CM fonts (OT1 and T1 encoded; the latter ones are often referred to as the EC fonts) and with the LM fonts; it also contains adequate hooks in order to make them compatible and usable with other font collections; this very file has been successfully typeset using the CM and LM fonts, and also resorting to the Times and Palatino eXtended collections requested with the packages \texttt{txfonts}\footnote{Antonis Tsolomitis wrote package \textsf{txfontsb} for using a different Greek font collection together with the TX fonts so that the Latin and Greek glyph styles directly match each other; see the \textsf{txfontsb} package documentation for more information.} and \texttt{pxfonts} respectively.
+In any case this \texttt{teubner} package makes the CB font collection (full or reduced) directly compatible by construction with both the CM fonts (OT1 and T1 encoded; the latter ones are often referred to as the EC fonts) and with the LM fonts; it also contains adequate hooks in order to make them compatible and usable with other font collections; this very file has been successfully typeset using the CM and LM fonts, and also resorting to the Times and Palatino eXtended collections requested with the packages \texttt{txfonts}\footnote{Antonis Tsolomitis wrote package \textsf{txfontsb} for using a different Greek font collection together with the TX fonts so that the Latin and Greek glyph styles directly match each other; see the \textsf{txfontsb} package documentation for more information.} and \texttt{pxfonts} respectively.
 
-This additional documentation will start by briefly recalling some peculiarities
-of the CB fonts and their mapping to the Latin keyboard; afterwards it will
-list the new commands and their syntax.
+This additional documentation will start by briefly recalling some peculiarities of the CB fonts and their mapping to the Latin keyboard; afterwards it will list the new commands and their syntax.
 
 \section{Usage}
-The \pack{teubner} extension is loaded in the usual way, but there are some simple rules to follow:
+The \pack{teubner} package is loaded in the usual way, but there are some simple rules to follow:
 \begin{quote}
-\texttt{\string\usepackage}\opt{options}\brArg{teubner}
+\texttt{\string\usepackage}\opt{options}\Marg{teubner}
 \end{quote}
 
 
-Since \pack{teubner} is an extension of the \pack{babel} package, it must be loaded after the latter. If you load it before and/or if you load it after, but you invoked the \texttt{babel} package without specifying the \meta{greek} language and the \texttt{polutoniko} Greek language attribute, \texttt{teubner} refuses to be completely loaded and emits a message very clear on this subject, so that you know what you should do in order to use the facilities offered by its extensions. 
+Since \pack{teubner} is a module that adds to the |greek.ldf| support for \pack{babel} package the functionalities needed by the Hellenists, it must be loaded after the latter. If you load it before and/or if you load it after, but you invoked the \texttt{babel} package without specifying the \meta{greek} language and the \texttt{ancient} Greek language attribute, \texttt{teubner} refuses to completely load and outputs a message very clear on this subject, so that you know what you should do in order to use the facilities offered by this module. 
 
 \noindent\textbf{Warning}: Some people like the Lipsian font shape and want to load it also for writing mathematics with it. No problem, but they shouldn't do this with \pack{teubner}, which is useful only to typeset Greek text. For using other alphabets in mathematics there are more suitable ways that rely on the commands described in the \texttt{fntguide.pdf} distributed with every \TeX\ system in \texttt{\$TEXMFDIST\slash doc\slash latex\slash base/}.
 
@@ -144,7 +131,7 @@ Option	& Meaning\R	\\\hline
 \i GlyphNames & to be selected in order to have available also the set of macros that directly address the accented glyphs\\[1ex]
 \hline
 \end{tabular}
-\caption{Options for the \pack{teubner} extension package}\label{t:opzioni}
+\caption{Options for the \pack{teubner} package}\label{t:opzioni}
 \bhrule
 \end{table}
 
@@ -154,13 +141,11 @@ You should never need (and therefore never use) the \textit{or} option for two r
 
 If you are using Latin fonts different from the CM , EC, or LM collections, you have to control what you get with or without the option \textit{boldLipsian}; generally speaking, this option is best used with darker normal fonts; I have tried the Times, the Palatino, and the Fourier ones, and actually this option is desirable. This might not be true with other vector fonts.
 
-With the inclusion of the extended accent macros in the \pack{teubner} package (see below), the named accented glyphs should not be needed anymore; these accented glyph name macros are not defined by default, but for backwards compatibility they are available if the \emph{GlyphNames} option is specified; with the 2013 new Greek support for the \babel\ package, the extended accent macros are defined in a more efficient way and you should not need them any more; therefore, unless you specify this option, you avoid overloading the internal \TeX\ memory areas, thus leaving extra space for more useful extensions. I suggest you to let the \emph{default} option \textit{NoGlyphNames} act as its name implies, and make use of the extended accent macros, should the need arise (see below). Moreover, if your keyboard has facilities for entering polytonic Greek, or if you installa a keyboard driver that allows you to do so, you can directly input Greek text with the Greek alphabet, without using the transliteration provided by the Greek support for \babel.
+With the inclusion of the extended accent macros in the \pack{teubner} package (see below), the named accented glyphs should not be needed anymore; these accented glyph name macros are not defined by default, but for backwards compatibility they are available if the \emph{GlyphNames} option is specified; with the 2013 new Greek support for the \babel\ package, the extended accent macros are defined in a more efficient way and you should not need them any more; therefore, unless you specify this option, you avoid overloading the internal \TeX\ memory areas, thus leaving extra space for more useful packages. I suggest you to let the \emph{default} option \textit{NoGlyphNames} act as its name implies, and make use of the extended accent macros, should the need arise (see below). Moreover, if your keyboard has facilities for entering polytonic Greek, or if you install a keyboard driver that allows you to do so, you can directly input Greek text with the Greek alphabet, without using the transliteration provided by the Greek support for \babel.
 
 \section{The CB Greek fonts}
-The CB Greek fonts (full collection) come in  all shapes, sizes and series as the European Modern fonts that conform with the T1 encoding introduced after the Cork Conference of the \TeX\ Users Group Society in 1991\footnote{If you want to or you have to use the single 10pt size fonts, you certainly produce smaller PDF files, at the expense of a slightly poorer typographical quality.}. The CB fonts conform
-to the encoding that is still being called LGR, since up to now there is no
-established encoding name for the Greek alphabet among the \TeX\ users, not
-yet, at least.
+The CB Greek fonts (full collection) come in all shapes, sizes and series as the European Modern fonts that conform with the T1 encoding introduced after the Cork Conference of the \TeX\ Users Group Society in 1991\footnote{If you want to or you have to use the single 10pt size fonts, you certainly produce smaller PDF files, at the expense of a slightly poorer typographical quality.}. The CB fonts conform to the encoding that is still being called LGR, since up to now there is no
+established encoding name for the Greek alphabet among the \TeX\ users, not yet, at least. For several reasons I suggest to use the Latin Modern fonts, instead of the CM or EC (CM-Super) ones, because the former are piecewise continuously scalable, while the latter offer only fixed font sizes. Recently also the CM-Super fonts may be continuously scaled as the Latin Modern ones, but it is necessary to use a specific extra package without any option.
 
 The regular shape has capital letters with serifs that are in the
 same style as the Latin capital ones, while the lower case letters
@@ -170,47 +155,36 @@ oblique (or slanted) versions. The CB fonts contain
 also the upright and slanted, medium and boldface small caps
 alphabets.
 
-The ``italic'' shape was designed in order to imitate the Olga font designed so
-as to have a contrasting style compared with the slanted Didot shape, in order
-to play  the same role as the italic letters play with the Latin roman
-ones. The Olga alphabets come in medium and boldface series, and in
-oblique and upright shapes.
+The “italic” shape was designed in order to imitate the Olga font designed so as to have a contrasting style compared with the slanted Didot shape, in order to play the same role as the italic letters play with the Latin roman ones. The Olga alphabets come in medium and boldface series, and in oblique and upright shapes.
 
 The CB fonts are completed with the sans serif fonts, the
 monospaced typewriter fonts and the fonts for slides, besides an
 outline family that shows the regular shapes and series just with
 their contours; there is also a shape with serifed lower case letters.
 
-The CB Lipsian fonts imitate the beautiful shapes used in
-Lipsia; they come in medium, bold, and extra-bold series, without
-an upright version, and they are meant to replace the
-corresponding Olga shapes. Their `simple bold' series is good for mixing
-with PostScript fonts, whose medium series is slightly blacker
-than the corresponding EC and LM fonts nurmally used with \LaTeX; this is easily achieved by passing the \emph{boldLipsian} option when invoking this \pack{teubner} extension file. Notice that the Lipsian font produces an alternative to the ordinary `italic' Olga shape, it is not any more the default `italic' shape as it used to be with previous versions of this package; now, in the same document, you can use both shapes and produce both versions: 
+The CB Lipsian fonts imitate the beautiful shapes used in Lipsia; they come in medium, bold, and extra-bold series, without an upright version, and they are meant to replace the corresponding Olga shapes. Their `simple bold' series is good for mixing with PostScript fonts, whose medium series is slightly blacker than the corresponding EC and LM fonts normally used with \LaTeX; this is easily achieved by passing the \emph{boldLipsian} option when invoking this \pack{teubner} file. Notice that the Lipsian font produces an alternative to the ordinary ‘italic’ Olga shape, that is not any more the default `italic' shape as it used to be with previous versions of this package; now, in the same document, you can use both shapes and produce both versions: 
 \foreignlanguage{greek}{\textit{Baq'ulides} 
-\textlatin{\upshape and} 
+\textlatin{and} 
 \textli{Baq'ulides}}. 
-With the availability of the unslanted Olga font and the serifed lowercase alphabet, you can use also the \verb|\textui| and the \verb|\textrs| commands so as to obtain \foreignlanguage{greek}{\textui{Baq'ulides} \textlatin{\upshape and} \textrs{Baq'ulides}}; also in extended boldface: \foreignlanguage{greek}{\bfseries\textui{Baq'ulides} \textlatin{\upshape \mdseries and} \textrs{Baq'ulides}}.
+With the availability of the upright Olga font and the serifed lowercase alphabet, you can use also the \verb|\textui| and the \verb|\textrs| commands so as to obtain \foreignlanguage{greek}{\textui{Baq'ulides} \textlatin{and} \textrs{Baq'ulides}}; also in extended boldface: \foreignlanguage{greek}{\bfseries\textui{Baq'ulides} \textlatin{\mdseries and} \textrs{Baq'ulides}}.
 
-But if you really want to permanently change the ``italic'' Greek font shape to the Lipsian one, without keeping the alternative, then in your preamble add the following statements \emph{after} you have loaded the \texttt{teubner} package:
+But if you really want to permanently change the “italic” Greek font shape to the Lipsian one, without keeping the alternative, then in your preamble add the following statements \emph{after} you have loaded the \texttt{teubner} package:
 \begin{verbatim}
 \addto\extrasgreek{\def\itdefault{li}}%
 \addto\noextrasgreek{\def\itdefault{it}}%
 \end{verbatim}
-With these settings, \verb|\textit| and \verb|\textli| become equivalent and both use the Lipsian shape while typesetting Greek text. Reverting to Latin script the \verb|\textli| text command uses the italic shape by default and there is no need to add anything else to the \verb|\noextrasgreek| macro.
+With these settings, \verb|\textit| and \verb|\textli| become equivalent and both use the Lipsian shape while typesetting Greek text. Reverting to Latin script the \verb|\textli| text command uses the italic shape by default and there is no need to add anything else to the 
+\verb|\noextrasgreek| macro.
 
 
 \subsection*{Technical information}
 Typesetting documents with different scripts sets forth some problems. The \emph{greek} option to the \babel\ package, besides setting up the typographical rules for Greek, as it does for any other language, provides the script change; it defines also the \verb|\textlatin| macro in order to typeset something with the Latin script while the default script is Greek, as well as the \verb|\textgreek| macro to typeset something with the Greek script when typesetting with a Latin one. Of course the usual \verb|\selectlanguage| and \verb|\foreinglanguage| commands, as well as the \texttt{otherlanguage} environment, provide for a global change of the typesetting characteristics or an environment where the settings are reset to Greek.
 
-\noindent\textbf{Beware}! Differently from before, \verb|\textlatin| changes only the encoding and sets some other small details, but it does not reset the local font family to "roman", as it used to do before \verb|teubner| version~4.8. This was remarked by Jens Börstinghaus, whom I thank very much for this bug notification. In facts \verb|\textlatin| is often used behind the scenes by \LaTeX\ internal commands and the user has little or no control over the font characteristics; before the font family was reset to the default, instead of continuing with the current family, series and shape. Now it does, and the users should explicitly  declare some other family, series or shape if they do not want the current ones.
-
-
-With standard \babel\ the CB fonts used to work only in conjunction with the CM fonts with either the OT1 (real CM fonts) or T1 (EC fonts) encoding. Since the 2008 distribution of standard \babel, the CB fonts work fine also with the Latin Modern fonts. This \pack{teubner} extension tries to work seamlessly also with other font families, but it is not that simple. Some technical explanations are necessary.
+With standard \babel\ the CB fonts used to work only in conjunction with the CM fonts with either the OT1 (real CM fonts) or T1 (EC fonts) encoding. Since the 2008 distribution of standard \babel, the CB fonts work fine also with the Latin Modern fonts. This \pack{teubner} module tries to work seamlessly also with other font families, but it is not that simple. Some technical explanations are necessary.
 
 When \LaTeX\ needs to use a specific font in a certain encoding and belonging to a  particular family, series and shape, available in such and such sizes, it gets this information by reading a \emph{font description file}; this file's name is composed with the encoding and the family names glued together and has the extension \texttt{.fd}; for OT1 encoded Computer Modern CM regular (serifed) fonts this file would be \texttt{ot1cmr.fd}. Any other package that is requested for using different fonts defines possibly a different encoding and certainly different family names. For using the Times eXtended TX fonts with T1 encoding, the \texttt{txfonts.sty} package defines the family name \texttt{txr} (for serifed fonts) so that \LaTeX\ reads the font description file \texttt{t1txr.fd} that contains the relevant information for all the series, shapes, and sizes available.
 
-The CB fonts are encoded according to the LGR encoding but have the same family names as the CM ones; since 2008, also the family names of the Latin Modern LM collection are recognised; therefore the relevant font description files for the regular\footnote{The regular lower case Greek alphabet does not have serifs; serifs are present in the font shape called `serifed' that corresponds to the\texttt{\string\textrs} font command.}  family are \texttt{lgrcmr.fd} and \texttt{lgrlmr.fd} respectively. The two collections of description files are not equivalent with one another, and they are not equivalent to the OT1 or T1 encoded CM or LM fonts, in the sense that the series and shapes available for these sets of fonts are not identical, even if most of them are.
+The CB fonts are encoded according to the LGR encoding but have the same family names as the CM ones; since 2008, also the family names of the Latin Modern LM collection are recognised; therefore the relevant font description files for the regular\footnote{The regular lower case Greek alphabet does not have serifs; serifs are present in the font shape called `serifed' that corresponds to the\texttt{\string\textrs} font command.}  families are \texttt{lgrcmr.fd} and \texttt{lgrlmr.fd} respectively. The two collections of description files are not equivalent with one another, and they are not equivalent to the OT1 or T1 encoded CM or LM fonts, in the sense that the series and shapes available for these sets of fonts are not identical, even if most of them are.
 
 In this way with CM and LM fonts the script switching for the same (existing) series and shapes amounts to switching the encoding name. At the same time there might exist some font switching commands that refer to a series or shape that does not exist in the other script families; one important example in our case is the Lipsian shape that is available only with the CB fonts. There is no problem in declaring the Lipsian shape switching commands that behave in a proper way together with the CM and LM fonts, but even if I did my best for working with other font families, I am not 100\% confident that my macros restore correctly the other font characteristics when declaring a different series or shape.
 
@@ -227,13 +201,13 @@ In this package I tried to forecast most situations, but I am not sure I coped w
 
 In particular I hooked the language changing declarations with suitable default family names; for example, when using the Times or the Palatino eXtended TX or PX  fonts,  three new family description files are created so as to connect the LGR encoding and the names of the above scalable fonts to the corresponding CB fonts\footnote{I chose the CM Greek families, instead of the LM ones, because only the former are described by means of macros that cope with the \emph{10pt} option to the \texttt{teubner} package; just in case\dots\ The actual used fonts are the same in any case, except possibly for the visual sizes; the CM fonts come in fixed sizes, while the LM fonts are continuously scalable by enlarging or reducing a smaller number of base visual sizes.}. 
 
-If you use different scalable fonts you can specify yourself the font associations you want to use; simply, after loading a package that sets other default font family or families, open the the package file and take notice of the new family names; for each \meta{latin} family (serifed, sans serif, monospace) create a connection with the corresponding  \meta{greek} family by means of the following command:
+If you use different scalable fonts you can specify yourself the font associations you want to use; simply, after loading a package that sets other default font family or families, open the package file and take notice of the new family names; for each \meta{latin} family (serifed, sans serif, monospace) create a connection with the corresponding  \meta{greek} family by means of the following command:
 \begin{quote}
 \texttt{\string\ifFamily}\marg{latin}\marg{greek}
 \end{quote}
 right after the \verb|\usepackage| command with which you call that package.
 
-Example: suppose you want to use the regular Fourier fonts to replace the default roman normal serifed fonts; then you should load the package \texttt{fourier} \emph{after} the \texttt{teubner} extension and specify:
+Example: suppose you want to use the regular Fourier fonts to replace the default roman normal serifed fonts; then you should load the package \texttt{fourier} \emph{after} the \texttt{teubner} module and specify:
 \begin{verbatim}
 \usepackage{fourier}
 \Lipsiantrue
@@ -241,20 +215,21 @@ Example: suppose you want to use the regular Fourier fonts to replace the defaul
 \end{verbatim}
 You can see that the family name \texttt{futs}, corresponding to the regular Fourier font family, has been matched to the CB Greek \texttt{cmr} font family; the name \texttt{futs} has been deduced by reading the \texttt{fourier.sty} file from which one can see that the family declaration for the regular Fourier font family is \texttt{futs}. This sort of coding does not take place with all fonts: if the Iwona fonts had to be chosen, for example, then the font family name would coincide with the font name, making it difficult to distinguish between the \emph{font name} and the \emph{font family name}.
 
-Notice the \verb|\Lipsiantrue| command before issuing the matching command 
-\verb|\ifFamily}|. This command is optional and is used only if the composer wishes to use the Lipsian fonts; in this case the \texttt{li} shape is also defined, so that the \verb|\textli| and \verb|\lishape| commands do not issue any error message. At the end of the execution if the \verb|\ifFamily| command, the boolean switch is automatically reset to \verb|\Lipsianfalse|.
+Notice the \verb|\Lipsiantrue| command before issuing the matching command \verb|\ifFamily}|. This command is optional and is used only if the composer wishes to use the Lipsian fonts; in this case the \texttt{li} shape is also defined, so that the \verb|\textli| and 
+\verb|\lishape| commands do not issue any error message. At the end of the execution of the \verb|\ifFamily| command, the boolean switch is automatically reset to \verb|\Lipsianfalse|.
 
-\noindent\textbf{Warning}: According to several maintainers of the language support packages, the procedure used with \verb|\ifFamily|, that produces in the local working directory a real, permanent \texttt{.fd} file, is not the best approach to create such pairing of fonts. G\"unter Milde, for example, produce a \pack{substitutefontfamily} package that defines the command \comando\subtitutefontfamily\ which creates a similar association, but does not write anything to the disk; simply the created association declarations are stored in the job memory, so that when the typesetting job is over, no traces remain on disk; this certainly avoids clogging the disk with the same files scattered all over in different directories that were the working one for different typesetting jobs.
+\noindent\textbf{Warning}: According to several maintainers of the language support packages, the procedure used with \verb|\ifFamily|, that produces in the local working directory a real, permanent \texttt{.fd} file, is not the best approach to create such pairing of fonts. G\"unter Milde, for example, produced a \pack{substitutefontfamily} package that defines the command \comando\subtitutefontfamily\ which creates a similar association, but does not write anything to the disk; simply the created association declarations are stored in the job memory, so that when the typesetting job is over, no traces remain on disk; this certainly avoids clogging the disk with the same files scattered all over in different directories that were the working ones for different typesetting jobs.
 
-A small caveat: when you issue for the first time the command \verb|\ifFamily| you might not see the expected result (while with Milde's package you immediately obtain the expected result), and your Greek text might be typeset with the default ``Greek error font''. But the second time you typeset your document the expected result is obtained with the correct fonts. This is because with the very first run a new font description file is generated, and this file will be available only in subsequent typesetting runs.
+A small caveat: when you issue for the first time the \verb|\ifFamily| command you might not see the expected result (while with Milde's package you immediately obtain the expected result), and your Greek text might be typeset with the default “Greek error font”. But the second time you typeset your document the expected result is obtained with the correct fonts. This is because with the very first run a new font description file is generated, and this file will be available only in subsequent typesetting runs.
 
 Nevertheless this does not imply that the correct fonts are used if the font switching macros are used without scoping groups or environments. Sometimes, when you use declarations instead of commands, it might be necessary to issue an apparently redundant \verb|\rmfamily| or \verb|\selectfont| command in order to re-establish the correct defaults.
 
-In order to insert \emph{short texts} in Greek, either in Didot upright or in Lipsian inclined shape, the \emph{text} commands \verb|\textDidot| and \verb|\textLipsias| may be used, as well as a redefined \verb|\textlatin| \emph{text} command for typesetting a short Latin script text while typesetting in Greek; these macros should already select the correct encoding, family, series and shape in most circumstances. If the users want to change some of these font characteristics, they have to do it explicitly.
+In order to insert \emph{short texts} in Greek, either in Didot upright or in Lipsian inclined shape, the \emph{text} commands \verb|\textDidot| and \verb|\textLipsias| may be used, as well as a redefined 
+\verb|\textlatin| \emph{text} command for typesetting a short Latin script text while typesetting in Greek; these macros should already select the correct encoding, family, series and shape in most circumstances.
 
 The \emph{text commands}, contrary to the corresponding \emph{text declarations}, typeset their argument within a group, so that the font characteristics are also correctly restored after the command execution is completed. 
 
-Therefore I suggest you to either use the text commands or to use the declarations as environment names (without the initial backslash), so that they provide the necessary group delimiters; it's syntactically correct and useful to input something such as:
+Therefore I suggest you to either use the text commands or to use the declarations as environment names (without the initial backslash), so that they provide the necessary group delimiters; it is syntactically correct and useful to input something such as:
 \begin{quote}
 \verb|\begin{Lipsiakostext}|\\
 \meta{Greek text to be typeset with the Lipsian font}\\
@@ -263,13 +238,13 @@ Therefore I suggest you to either use the text commands or to use the declaratio
 
 
 \section{Font installation}
-In order to use the Greek CB fonts and the extensions provided with this
-package, you need to install them, if they are not already installed by default when you install your preferred \TeX\ system \emph{complete} distribution. You can freely download those fonts from \acro{ctan}, where you can find both the PostScript scalable ones and the driver files for generating their bitmaped with \MF; since nowadays it's very unlikely that \LaTeX\ users limit themselves to a final DVI file, but typeset their documents in PDF (or PS formats), the pixel files are very unlikely needed to produce their final documents; the \MF\ pixel files just allow the DVI previewer (should one be used) to run \MF\ in the background in order to produce the necessary pixel files so as to display on the screen the typeset documents\footnote{I mean documents that have been typeset with \textsf{latex}, not with \textsf{pdflatex}.}. These days there are other solutions to preview directly the typeset output file in PDF format and to use the previewer for direct and inverse search, so that the DVI format becomes really necessary only in very special and rare occasions. In the future it's very likely that the choice among such PDF previewers is much greater than today: there are certainly the multi\-platform shell editors \textsf{TeXworks}, \textsf{TeXstudio}, and \textsf{Texmaker} that incorporate a PDF previewer capable of direct and inverse search; for modern Windows platforms there is the \textsf{SumatraPDF} previewer that may be configured to work with various shell editors in order to perform in the same way. For Mac platforms, besides the default shell editor and previewer \textsf{TeXShop}, and the multi-platform program \textsf{TeXworks}, the Mac specific \textsf{TeXnicle} and \textsf{Texpad}, one can proceed with \textsf{Aquamacs} as a shell editor and \textsf{Skim} as PDF previewer that work together so as to allow direct and inverse search. 
+In order to use the Greek CB fonts and the facilities provided by this
+package, you need to install them, if they are not already installed by default when you install your preferred \TeX\ system \emph{complete} distribution. You can freely download those fonts from \acro{ctan}, where you can find both the PostScript scalable ones and the driver files for generating their bitmapped versions with \MF; since nowadays it's very unlikely that \LaTeX\ users limit themselves to a final DVI file, but typeset their documents in PDF (or PS formats), the pixel files are very unlikely needed to produce their final documents; the \MF\ pixel files just allow the DVI previewer (should one be used) to run \MF\ in the background in order to produce the necessary pixel files so as to display on the screen the typeset documents\footnote{I mean documents that have been typeset with \textsf{latex}, not with \textsf{pdflatex}.}. These days there are other solutions to preview directly the typeset output file in PDF format and to use the previewer for direct and inverse search, so that the DVI format becomes really necessary only in very special and rare occasions. In the future it's very likely that the choice among such PDF previewers is much greater than today: there are certainly the multi\-platform shell editors \textsf{TeXworks}, \textsf{TeXstudio}, and \textsf{Texmaker} that incorporate a PDF previewer capable of direct and inverse search; for modern Windows platforms there is the \textsf{SumatraPDF} previewer that may be configured to work with various shell editors in order to perform in the same way. For Mac platforms, besides the default shell editor and previewer \textsf{TeXShop}, and the multi-platform program \textsf{TeXworks}, the Mac specific \textsf{TeXnicle} and \textsf{Texpad}, the user can proceed with \textsf{Aquamacs} as a shell editor and \textsf{Skim} as PDF previewer that work together so as to allow direct and inverse search. 
  
 \section{\TeX\ font metric files}
-The package \texttt{teubner} requires the updated \TeX\ font metric files \texttt{.tfm} for all sizes and series of the Lipsian fonts.  With your file system explorer go to the folder \texttt{\$TEXMFDIST/fonts/tfm/public/cbfonts/} and read the date of, say, \texttt{grml1000.tfm}; if this date precedes the year 2010, then this \texttt{.tfm} file is ``old'' and must be replaced, and you should update your Greek CB font collection (may be you should update your whole \TeX\ system installation).
+The \texttt{teubner} package requires the updated \TeX\ font metric files \texttt{.tfm} for all sizes and series of the Lipsian fonts.  With your file system explorer go to the folder \texttt{\$TEXMFDIST/fonts/tfm/public/cbfonts/} and read the date of, say, \texttt{grml1000.tfm}; if this date precedes the year 2010, then this \texttt{.tfm} file is “old” and must be replaced, and you should update your Greek CB font collection (may be you should update your whole \TeX\ system installation).
 
-The updated \texttt{.tfm} files add some ligature and kerning information that is missing from the ``old'' ones. The Type~1 \texttt{pfb} font files have not been modified at all.
+The updated \texttt{.tfm} files add some ligature and kerning information that is missing from the “old” ones. The Type~1 \texttt{pfb} font files have not been modified at all.
  
  
 \section{Greek text and Latin keys}
@@ -290,11 +265,11 @@ letters}\label{t:corrispondenza}
 
 Notice that there is the possibility of inputting \texttt{c} in
 order to get the final sigma \textDidot{c}, but the CB fonts are
-conceived with the non-Greek typist in mind, so that it is even
+conceived with the non-Greek user in mind, so that it is even
 possible to input \texttt{s} at the end of words, because the
 whole software is smart enough to detect the word boundary and to
 use the correct shape of the letter sigma within or at the word
-end. This mechanism is so ``sticky'' that it becomes difficult to
+end. This mechanism is so “sticky” that it becomes difficult to
 type an isolated initial or middle sigma; the CB
 fonts contain an invisible character, \texttt{v}, that may be
 used for several purposes, one of which is to hide the word
@@ -307,12 +282,12 @@ be used; if you type \verb"\M{v}" you get
 \enspace\textDidot{\M{v}}\enspace, while if you omit the invisible
 \texttt{v} you get \enspace\textDidot{\M{}}\enspace.
 
-In LICR (\LaTeX\ Internal Character Representation), that is being used by the modern (2013) Greek support for \babel, the \texttt{v} character is represented by the macro \comando\textcompwordmark\ whose name recalls a compound word separator; actually it may perform also in this way; but it is a special character, not simply an invisible strut; it has the same category code as the other alphabetic characters, it has a very small width but its height is equal to the other lower case letters without ascenders; it's a real character even if in practice it is invisible; in particular it does not impeach hyphenation as an equally sized normal strut would do. But its usefulness is $(a)$ to hide the word boundary; $(b)$ to support an accent that would drop to the base line if this character was absent; $(c)$ to break ligatures in those rare cases where it's necessary to do so.
+In LICR (\LaTeX\ Internal Character Representation), that is being used by the modern (2013) Greek support for \babel, the \texttt{v} character is represented by the macro \comando\textcompwordmark\ whose name recalls a compound word separator; actually it may play also this role; but it is a special character, not simply an invisible strut; it has the same category code as the other alphabetic characters, it has a very small width but its height is equal to the other lower case letters without ascenders; it's a real character even if in practice it is invisible; in particular it does not impeach hyphenation as an equally sized normal strut would do. But its usefulness is $(a)$ to hide the word boundary; $(b)$ to support an accent that would drop to the base line if this character was absent; $(c)$ to break ligatures in those rare cases where it's necessary to do so.
 
 Accents, spirits and dieresis may be input \emph{before} each letter
 (prefix notation) without using any particular control sequence, that is resorting to the ligature mechanism  that is part of the font characteristics; but since with certain fonts this mechanism may break kernings, it's better to use the proper accent macros;
 the correspondence between the Latin symbols and the Greek
-diacritical marks is shown in table~\ref{t:accenti}; all ``upper''
+diacritical marks is shown in table~\ref{t:accenti}; all “upper”
 diacritical marks must be prefixed (in any order), while the iota
 subscript must be postfixed. Therefore if you input \verb">'a|", you
 get~\textDidot{>'a|}.
@@ -327,24 +302,22 @@ extended accent macros
         &\t\string\>&\t\string\<&\t\string\"&\t\string\'&\t\string\`&\t\string\~& 
 \end{tabular}
 \caption{Correspondence between the Latin keyboard symbols and
-Greek diacritical marks; extended accent macros are also shown; notice that a couple of ``high'' diacritical marks may be joined in one macro (in any order) to produce the same result as with two separate macros; in other words, \texttt{\string\>\string\'}, \texttt{\string\'\string\>}, \texttt{\string\>'} and \texttt{\string\'>} are equivalent with one another. For what concerns \texttt{\string\~}, see remarks below table~\ref{t:accentmacros}}\label{t:accenti}
+Greek diacritical marks; extended accent macros are also shown; notice that a couple of “high” diacritical marks may be joined in one macro (in any order) to produce the same result as with two separate macros; in other words, \texttt{\string\>\string\'}, \texttt{\string\'\string\>}, \texttt{\string\>'} and \texttt{\string\'>} are equivalent with one another. For what concerns \texttt{\string\~}, see remarks below table~\ref{t:accentmacros}}\label{t:accenti}
 \bhrule
 \end{table}
 
-Macrons and breves are just single glyphs and do not appear in combination with
-any letter, due to the limitation of 256 glyphs per font; but they may be input
-by means of commands \verb|\M| and \verb|\B| respectively when typesetting in Greek
-in order to use them as single diacritics; for more than one diacritic superimposed to one another, when macrons and breves are involved, some other commands are available as shown in table~\ref{t:accentmacros}. 
+Macrons and breves are just single glyphs and do not appear in combination with any letter, due to the limitation of 256 glyphs per font; but they may be input by means of commands \verb|\M| and \verb|\B| respectively when typesetting in Greek in order to use them as single diacritics; for more than one diacritic superimposed to one another, when macrons and breves are involved, some other commands are available as shown in table~\ref{t:accentmacros}. 
 
 The new (2013) Greek support for \babel\ contains now the LICR encoded accent macros that allow to use any encoding input method, including direct input of Greek characters. The internal representation of accent macros resorts to the same symbols shown in table~\ref{t:accenti}; simply they are prefixed by a backslash and/or the accent sequence is prefixed with one backslash; therefore \textDidot{>'a|} may be obtained with \verb+>'a|+, or \verb+\>\'a|+, or  \verb+\>'a|+. The last form is to be  preferred with some shapes as discussed in the following paragraphs. But the LICR (\LaTeX\ Internal Character Representation) is much more than this; it separates the input encoding from the output font encoding, so that direct literal greek input is possible (of course with the \opt{utf8} encoding) and the output is useful for both LGR encoded 8-bit fonts and the UNICODE encoded OpentType fonts; this way \pack{babel} and the Greek support for \babel, provided by the new \file{greek.ldf}, may be used also with \XeLaTeX\ and \LuaLaTeX. Moreover now (October 2014) file \file{greek.ldf} can select the ancient Greek hyphenation when typesetting with \pdfLaTeX\footnote{This is why with this release of the \pack{teubner} package, the default language attribute is set to \texttt{ancient}.}; with \pack{polyglossia} this possibility was available from the very beginning of the Greek support by this package.
+The 2020 version of the \file{greek.ldf} file introduces some new coding incompatible with the extension provided by this module (up to version~48) to get Greek Milesian and Attic numerals. From \pack{teubner} version~5.0, the LICR codes used by the new \file{greek.ldf} file are extended in oder to get Greek numerals that use the ancient glyphs, and therefore some macros are redefined. On the occasion of this update, the necessary macros for the Greek numerals have been redefined by means of the \LaTeX\,3 language through the interface macros previously defined by the \pack{xparse} package and now (2020) integral part of the \LaTeX\ kernel; see below for further details.
 
 Together with the macros for inserting such symbols, a complete set is available for inserting any combination of diacritical marks over or under any letter, not only vowels: see table~\ref{t:accentmacros}. 
 
 Of course the results may not be comparable with the ones one can obtain with the regular ligature mechanism or by using the LICR macros; the advantage of the redefined accent macros is twofold: (a) it is connected to the possibility of inserting macrons and breves and/or to set the various combinations over or under \emph{any} letter, even if it is a consonant; (b) for all accent vowel combinations that have a specific glyph in the font, the actual accented symbol is used so that kernings and ligatures are maintained; this result is achieved also by using the extended accent macros shown in the third line of table~\ref{t:accenti}; as shown elsewhere there is a noticeable difference between {\Lipsiakostext a>ut'os} and \textLipsias{a\s{u}t\'os} or \textLipsias{a\>ut\'os} or \textLipsias{a\>ut'os}. In this example the first word is typed in as \verb+a>ut'os+, while the other words may be typed in as \verb+a\s{u}t\'os+, or \verb*+a\us t\oa s+, or \verb+a\>ut'os+, or even in mixed form \verb*+a\us t'os+, thanks to the fact that there is no kerning between `tau' and `omicron with or without acute'.
 
-The attentive reader might have noticed that some  accent macros use the control symbols that are available for other standard \LaTeX\ environments or even defined in the \LaTeX\ kernel. Accent macros \cs{`}, \cs{'} and \cs{=} are already taken care by the \LaTeX\ kernel that uses a particular trick to use them as control macros in the \amb{tabbing} environment; therefore there should not be any conflict. 
+The attentive readers might have noticed that some accent macros use the control symbols that are available for other standard \LaTeX\ environments or even defined in the \LaTeX\ kernel. Accent macros \cs{`}, \cs{'} and \cs{=} are already taken care by the \LaTeX\ kernel that uses a particular trick to use them as control macros in the \amb{tabbing} environment; therefore there should not be any conflict. 
 
-On the opposite some conflicts may arise with \cs{<} and \cs{>}, as reported by David Kastrup. We have examined these conflict occurrences and we noticed that actually \cs{>} is defined as a `math wide space' command; an alias \cs{:} is defined immediately after the definition, and the \LaTeX\ handbook by Leslie Lamport does not even mention \cs{>}; therefore \cs{>} may be considered a leftover from the beginnings of \LaTeX, and it would be surprising if anybody used it; nevertheless\dots\ The control symbol \cs{<} has been reported as being used as a macro with a delimited argument \cs{<}\meta{arg}\texttt{>} in the documentation of package \pack{calc}. We immagine that it is very unlikely that this \pack{teubner} package might be used in another package documentation, but\dots
+On the opposite some conflicts may arise with \cs{<} and \cs{>}, as reported by David Kastrup. We have examined these conflict occurrences and we noticed that actually \cs{>} is defined as a `math wide space' command; an alias \cs{:} is defined immediately after the definition, and the \LaTeX\ handbook by Leslie Lamport does not even mention \cs{>}; therefore \cs{>} may be considered a leftover from the beginnings of \LaTeX, and it would be surprising if anybody used it; nevertheless\dots\ The control symbol \cs{<} has been reported as being used as a macro with a delimited argument \cs{<}\meta{arg}\texttt{>} in the documentation of package \pack{calc}. We immagine that it is very unlikely that this \pack{teubner} module functionalities might be used in another package documentation, but\dots
 
 These conflicts are avoided if Günter Milde package \pack{textalpha} is loaded; we did not find out any conflict in any testing run we made, but such conflicts may arise; therefore we decided to have \pack{teubner} load the \pack{textalpha} package at \verb|\begin{document}| execution time, so as to avoid any possible conflicts.
 
@@ -394,41 +367,33 @@ fall on the very first vowel of a word. Suggestion; never use the \texttt{tabbin
 \end{table}
 
 \section{Ligatures}
-It should be clear from the previous section that the ligature mechanism is the
-one that offers good results with most accented vowels, while speeding up the keying-in of the text to be typeset; nevertheless there are situations where you might be unsatisfied.
+It should be clear from the previous section that the ligature mechanism is the one that offers good results with most accented vowels, while speeding up the keying-in of the text to be typeset; nevertheless there are situations where you might be unsatisfied.
 
 For example compare \textLipsias{a>ut'os} with \textLipsias{a\>ut\'os}. The small spacing difference, if any, between tau and the accented omicron is not noticeable, but the spacing difference between alpha and the marked upsilon is remarkable. Where does that difference come from? It comes from the fact that the smooth spirit marker inhibits kerning between the previous alpha and the resulting ligature from the spirit marker and the upsilon\footnote{The CB fonts may be used also with monotoniko spelling; in this case \textLipsias{A"ULOS} comes out well even with ligatures \texttt{A"ULOS}, because a special kludge has been devised; with the extended accent macros it would not be too boring to typeset \texttt{A\string\"ULOS} and do away with that kludge; without it and without such extended macros that word would be set as \textLipsias{Av"ULOS} with a much larger space between the capital alpha and the marked capital upsilon.}. 
-In other words, by inputting \verb"a>ut'os", as it is suggested in the previous
-section, the spirit marker and the acute accent inhibit the kerning mechanism with the previous letter. In most instances the lack of such kerning is hardly noticeable, but in others it strikes your attention.
+In other words, by inputting \verb"a>ut'os", as it is suggested in the previous section, the spirit marker and the acute accent inhibit the kerning mechanism with the previous letter. In most instances the lack of such kerning is hardly noticeable, but in others it strikes your attention.
 
-For this reason two mechanisms are implemented in this package:
+For this reason two mechanisms are implemented in this package.
 \begin{enumerate}\itemsep=0pt\parsep=0pt
-\item  the extended accent macros created by Günter Milde are now the default setting in the Greek support for \babel, and
-\item the character names have been defined with macros that access directly their own glyphs.
+\item  The extended accent macros created by Günter Milde are now the default setting in the Greek support for \babel, and
+\item The character names have been defined with macros that access directly their own glyphs.
 \end{enumerate}
-The first solution has been described in the previous section and the extended accent  macros are shown in table~\ref{t:accenti}. At the expense of one slash, these macros create a chain of commands that deeply exploit the \LaTeXe\ kernel commands and allow to fetch directly each accented character; notice that there is no need to treat the \verb+|+ sign this way, because its postfixed position does not break the kerning/ligature mechanism. The spirit macros \verb+\>+ and \verb+\<+ work also with the consonant `r' to produce \textLipsias{\>r, \<r}. The extended accent macros work correctly also with capital letters (where, in all caps, accents should not be typeset, except the dieresis, while in normal initial capitalising the upper diacritics must be written at the left of the initial letter); for example\footnote{In the capitalised word the spirit and accent at the left of A imply a hiatus between the A and the \textDidot{u}; in the all caps word this hiatus is marked with the ``dialytika'' (dieresis) over the \textDidot{U}. This is an unusual example, but it  shows also why the \texttt{\string\uppercase} and the \texttt{\string\MakeUppercase} require some attention in polytonic Greek.} \textDidot{\>'Aulos, A\"ULOS} was typeset with \verb+\>'Aulos, A\"ULOS+. Notice also that the initial capital vowel  has a spirit and possibly an accent, or is not preceded by anything, since the possible spirit with or without accent falls on the second element of a descending diphthong: \textDidot{a\>ut'os}, \textDidot{A\>ut'os}, and \textDidot{AUTOS}; \textDidot{e\>'inai}, \textDidot{E\>'inai}, \textDidot{EINAI}. If you really want to show an example of how accents should \emph{not} be used in all caps words, you can type \textDidot{A\>UT\A{O}S} but you have to use the macros of 
+The first solution has been described in the previous section and the extended accent  macros are shown in table~\ref{t:accenti}. At the expense of one slash, these macros create a chain of commands that deeply exploit the \LaTeXe\ kernel commands and allow to fetch directly each accented character; notice that there is no need to treat the \verb+|+ sign this way, because its postfixed position does not break the kerning/ligature mechanism. The spirit macros \verb+\>+ and \verb+\<+ work also with the consonant `r' to produce \textLipsias{\>r, \<r}. The extended accent macros work correctly also with capital letters (where, in all caps, accents should not be typeset, except the dieresis, while in normal initial capitalising the upper diacritics must be written at the left of the initial letter); for example\footnote{In the capitalised word the spirit and accent at the left of A imply a hiatus between the A and the \textDidot{u}; in the all caps word this hiatus is marked with the “dialytika” (dieresis) over the \textDidot{U}. This is an unusual example, but it  shows also why the \texttt{\string\uppercase} and the \texttt{\string\MakeUppercase} require some attention in polytonic and ancient Greek.} \textDidot{\>'Aulos, A\"ULOS} was typeset with \verb+\>'Aulos, A\"ULOS+. Notice also that the initial capital vowel has a spirit and possibly an accent, or is not preceded by anything, since the possible spirit with or without accent falls on the second element of a descending diphthong: \textDidot{a\>ut'os}, \textDidot{A\>ut'os}, and \textDidot{AUTOS}; \textDidot{e\>'inai}, \textDidot{E\>'inai}, \textDidot{EINAI}. If you really want to show an example of how accents should \emph{not} be used in all caps words, you can type \textDidot{A\>UT\A{O}S} but you have to use the macros of 
 table~\ref{t:accentmacros} as such: \verb+A\>UT\A{O}S+. 
 
-Another solution is available if the \emph{GlyphNames} option is specified to the \texttt{teubner} package: a set of macros has been defined such that it is
-possible to input the accented characters directly, without
-resorting to the ligature mechanism. Such macros have a common
-structure; they are formed with the letters that make up the
-complex glyph in a certain order, precisely every macro is made
-up as such:
+Another solution is available if the \emph{GlyphNames} option is specified to the \texttt{teubner} package: a set of macros has been defined such that it is possible to input the accented characters directly, without resorting to the ligature mechanism. Such macros have a common structure; they are formed with the letters that make up the complex glyph in a certain order, precisely every macro is made
+up as follows
 \begin{enumerate}\itemsep=0pt\parsep=0pt
-\item the first character, obviously, is the backslash character \texttt{\char92};
-\item the next character is the name of the base character, one of the vowels a, e, h, i, o, u, w, or the consonant r, or one of the capitalised vowels I~or~U;
-\item the next optional character is the code for dieresis, or smooth, or rough spirit, with one of the letters d, s, r;
-\item the next character is the code for the circumflex, acute, or grave accent with one of the letters c, a, or g;
-\item the last optional character indicates iota subscript with the presence of an i;
-\item there are no glyph names for upper case letters, since they should never be marked with diacritics, except for the diaeresis over \textDidot{I} and~\textDidot{U} and for these glyphs adequate names are provided.
+\item the first character, obviously, is the backslash character \texttt{\char92}.
+\item The next character is the name of the base character, one of the vowels a, e, h, i, o, u, w, or the consonant r, or one of the capitalised vowels I~or~U.
+\item The next optional character is the code for dieresis, or smooth, or rough spirit, with one of the letters d, s, r.
+\item The next character is the code for the circumflex, acute, or grave accent with one of the letters c, a, or g.
+\item The last optional character indicates iota subscript with the presence of an i.
+\item There are no glyph names for upper case letters, since they should never be marked with diacritics, except for the diaeresis over \textDidot{I} and~\textDidot{U} and for these glyphs adequate names are provided.
 \end{enumerate}
 
-This means that, for instance, \comando\asai\ stands for \textDidot{\asai}. For
-your convenience such macros are collected in table~\ref{t:compoundvowels}.
-Of course one can always resort to the accent--vowel
-combination as exemplified at the end of the previous section; the above
-example \textDidot{\asai} may be obtained also with \verb+\>'a|+ or \verb+\As{a}|+.%
+This means that, for instance, \comando\asai\ stands for \textDidot{\asai}. For your convenience such macros are collected in table~\ref{t:compoundvowels}.
+Of course one can always resort to the accent--vowel combination as exemplified at the end of the previous section; the above example \textDidot{\asai} may be obtained also with \verb+\>'a|+ or 
+\verb+\As{a}|+.%
 \footnote{Postfixed markings do not pose any problem with
 kernings and ligatures; this is why the postfixed ligature for the iota
 subscript may still be used also when the accent--vowel combinations are used.}
@@ -491,12 +456,11 @@ As we have seen in the previous sections the ligature and kerning mechanisms are
 
 The remarks concern the use of capital letters and, to a certain extent also the caps and small caps font shape. As mentioned before in Greek typography words with capital initials starting with a vowel require their diacritics in front and at the left of the initial capital vowel (for example:\textLipsias{>Aristot'elhs}) provided the vowel is not the first element of a Greek diphthong; in the latter case the diacritics go on top of the diphthong lower case second element (for example: \textLipsias{A>isq'ulos}). On the opposite, all-caps words, such as in book titles or, with certain \LaTeX\ classes, in the headings, are typeset without any diacritic, except the diaeresis.
 
-
 I have already shown the unusual example of the word \textLipsias{>'aulos} where the first two vowels do not form a diphthong, but a hiatus; and this is why the diacritics fall on top of the alpha, not on the second element of the diphthong, for the very reason that there is no diphthong. In order to stress this unusual situation the word is most often spelled as \textLipsias{>'a\"ulos}, where the dieresis is sort of redundant, because the diacritics over the alpha already denote the hiatus. Similarly \textLipsias{>a\"upn'ia} is spelled with the redundant dieresis, although the soft spirit on the alpha already marks the hiatus. When these words require a capital initial, they become \textLipsias{>'A\"ulos} and \textLipsias{>A\"upn'ia}. 
 
-Notice that an initial single vowel may receive only a spirit marker with or without an accompanying accent, never a dieresis or a single accent\footnote{Of course we are talking of the polytonic spelling, since this package \texttt{teubner} sets this spelling as the default one; nobody forbids to spell in monotonic even when the polytonic spelling is assumed, but in some rare instances there might be some inconsistencies.}. I tried hard to set up all the ligature and extended accent macros so as to do the right things when capitalising or uppercasing, and if you follow the suggestions given in this section you should not meet any particular inconvenience.
+Notice that an initial single vowel may receive only a spirit marker with or without an accompanying accent, never a dieresis or a single accent\footnote{Of course we are talking of the ancient spelling, since this package \texttt{teubner} sets this spelling as the default one; nobody forbids to spell in monotonic even when the ancient spelling is assumed, but in some rare instances there might be some inconsistencies.}. I tried hard to set up all the ligatures and extended accent macros so as to do the right things when capitalising or uppercasing, and if you follow the suggestions given in this section you should not meet any particular inconvenience.
 
-Assume these words have to go in an all-caps header that is made up (behind the scenes) by making use of the \verb|\MakeUppercase| command; they have to be spelled \textLipsias{A\"ULOS} and \textLipsias{A\"UPNIA}, even if in the sectioning command argument they were spelled in lowercase with all the necessary diacritics. %>>>>>
+Assume these words have to go in an all-caps header that is made up (behind the scenes) by making use of the \verb|\MakeUppercase| command; they have to be spelled \textLipsias{A\"ULOS} and \textLipsias{A\"UPNIA}, even if in the sectioning command argument they were spelled in lowercase with all the necessary diacritics. 
 
 This is where the ligature and/or the extended accent macros may show their different behaviour. With the \texttt{teubner} generated secondary \texttt{LGRaccents-glyphs\discretionary{}{.}{.}def} file, that contains all the extended accent macros, such macros do not disappear in uppercasing, i.e.\ in transforming the mixed case argument of the 
 \verb|\MakeUppercase| command into an all-caps letter string. On the opposite the ligature sequences completely loose any reference to diacritics.
@@ -516,12 +480,11 @@ In other words we have:
 10) \verb|\MakeUppercase{e>uzw\"ia}| yields \textLipsias{\MakeUppercase{e>uzw\"ia}}.%\\
 \end{flushleft}
 %
-and it's easily seen that: 1) corresponds to a non redundant lowercase correct spelling but misses the required dieresis in upper case; 2) is correct but it relies on a special kludge on which it's better not to rely on, because in future releases of the fonts it may be eliminated; meanwhile it is usable; 3) is correct; 4) is correct because \verb|\MakeUppercase| does not act on macros, but \verb|\>'| \emph{is} a macro, precisely an accent macro, that acts on the following letter before uppercasing, and the uppercase of an alpha with diacritics si simply the capital alpha; 5) is corret, but relies in the same kludge as case 2, so the same warnings apply; case 6) displays the result of using the accented glyph names which are not subject to capitalisation since they are given by means of macros; therefore they can never be used for words that are possibly subject to all-caps transformation. 
+and it's easily seen that: 1) corresponds to a non redundant lowercase correct spelling but misses the required dieresis in upper case; 2) is correct but it relies on a special kludge on which it's better not to rely on, because in future releases of the fonts it may be eliminated; meanwhile it is usable; 3) is correct; 4) is correct because \verb|\MakeUppercase| does not act on macros, but \verb|\>'| \emph{is} a macro, precisely an accent macro, that acts on the following letter before uppercasing, and the uppercase of an alpha with diacritics si simply the capital alpha; 5) is correct, but relies in the same kludge as case 2, so the same warnings apply; case 6) displays the result of using the accented glyph names which are not subject to capitalisation since they are given by means of macros; therefore they can never be used for words that are possibly subject to all-caps transformation. 
 
-Let's examine another case where the lower case word has both the dieresis and an accent over the same vowel: \textLipsias{e>uzw"'ia}. Case 7) shows the effect of uppercasing when using ligatures, and the result is not correct because the dieresis does not fall over the capital iota, but between the capital omega end th capital iota; 8) by simply inverting the sequence of the dieresis and the acute accent a correct result is obtained, but kerning problems might take place because of the invisible presence of the lower cased acute accent; notice that the same result would be obtained if instead of the dieresis-vowel ligature the extended dieresis macro had been used; case 9) displays the situation when both extended accent macros are used so that the result does not suffer of any kerning problem; finally, case 10) displays a correct upper case result but the lower case counterpart would miss the acute accent.
+Let's examine another case where the lower case word has both the dieresis and an accent over the same vowel: \textLipsias{e>uzw"'ia}. Case 7) shows the effect of uppercasing when using ligatures, and the result is not correct because the dieresis does not fall over the capital iota, but between the capital omega end the capital iota; 8) by simply inverting the sequence of the dieresis and the acute accent a correct result is obtained, but kerning problems might take place because of the invisible presence of the lower cased acute accent; notice that the same result would be obtained if instead of the dieresis-vowel ligature the extended dieresis macro had been used; case 9) displays the situation when both extended accent macros are used so that the result does not suffer of any kerning problem; finally, case 10) displays a correct upper case result but the lower case counterpart would miss the acute accent.
 
-When using small caps or caps and small caps, in other words, when using the 
-\verb|\scshape| declaration or the \verb|\textsc| command you should pay attention to other details; for example:
+When using small caps or caps and small caps, in other words, when using the \verb|\scshape| declaration or the \verb|\textsc| command you should pay attention to other details; for example:
 \begin{flushleft}
 11)  \verb|\textDidot{\scshape >Arqim'hdhs}| yields \textDidot{\scshape>Arqim'hdhs}\\
 12)  \verb|\textDidot{\scshape \>Arqim'hdhs}| yields \textDidot{\scshape\>Arqim'hdhs}\\
@@ -531,7 +494,9 @@ When using small caps or caps and small caps, in other words, when using the
 16)  \verb|\textDidot{\scshape \>{v}Arqim\'hdhs}| yields \textDidot{\scshape\>{v}Arqim\'hdhs}\\
 \end{flushleft}
 
-With caps and small caps a spirit, or a spirit-accent combination prefixed to a capital letter does not produce any mark; this is the usual modern Greek habit of avoiding accents with capital letters and the \verb|\scshape| specification to Greek fonts excludes all the ligatures and kernings with such signs; the same holds true also with small caps. The extended accent macros explicitly avoid any mark over capital letters, but even in front they are ``silenced'' by the very characteristics of the specific font shape. With small caps there is a similar situation, and  the extended accent macros produce the expected result. But accents are apparently used in French also when proper names are typeset in caps and small caps, contrary to Greek, so that in French the spelling of case 16 is correct; for the initial spirit, therefore it is necessary to resort to the invisible character obtained with the Latin letter `v', that is uppercased to itself and is suitable for supporting any diacritic mark at the proper height. Julien Browaeys pointed out this specific typesetting French tradition; I thank him very much for his feedback on this point.
+%>>>>>>>>>
+
+With caps and small caps a spirit, or a spirit-accent combination prefixed to a capital letter does not produce any mark; this is the usual modern Greek habit of avoiding accents with capital letters and the \verb|\scshape| specification to Greek fonts excludes all the ligatures and kernings with such signs; the same holds true also with small caps. The extended accent macros explicitly avoid any mark over capital letters, but even in front they are “silenced” by the very characteristics of the specific font shape. With small caps there is a similar situation, and  the extended accent macros produce the expected result. But accents are apparently used in French also when proper names are typeset in caps and small caps, contrary to Greek, so that in French the spelling of case 16 is correct; for the initial spirit, therefore it is necessary to resort to the invisible character obtained with the Latin letter `v', that is uppercased to itself and is suitable for supporting any diacritic mark at the proper height. Julien Browaeys pointed out this specific typesetting French tradition; I thank him very much for his feedback on this point.
 
 Conclusion: when writing the input code for a sectioning command, the argument of which has to be transformed to upper case, use \verb|\"| (in the proper sequence with other accents) for the internal diereses, as in cases 3), 4), 8), and 9) above. With the extended accent macros there are really few problems; the remaining ones take place in complete uppercasing remain with French traditions in caps and small caps that can be easily handled through the use of the \texttt{v} special invisible glyph. If you want to avoid also this possibility, then either avoid classes that typeset their headings in all-caps, or use any external package that defines sectioning commands with two optional arguments, one for the heading contents and the other for the table of contents; or use equivalent tricks: for example the \texttt{memoir} class has a specific command \verb|\nouppercaseheads| that eliminates any heading uppercasing.
 
@@ -539,12 +504,12 @@ Conclusion: when writing the input code for a sectioning command, the argument o
 Other Greek symbols may be obtained with ligatures or explicit
 commands; table~\ref{t:gsymbols} contains such ligatures and
 symbols; notice that some of these are specific additions
-introduced with this extension package.
+introduced with this module.
 
 \begin{table}\thrule\let\c\comando\let\l\textDidot
 \makebox[\textwidth]{%
 \begin{tabular}{lclclc}
-\c{''}      &\l{''}     &\c{((}     &\l{((}     &\c{))}     &\l{))} \\
+\c{'{}'}      &\l{''}     &\c{((}     &\l{((}     &\c{))}     &\l{))} \\
 \c\GEodq    &\l\GEodq   &\c\GEcdq   &\l\GEcdq   &\c:        &\l:    \\
 \c\GEoq     &\l\GEoq    &\c\GEcq    &\l\GEcq    &\c?        &\l?    \\
 \c\ENodq    &\l\ENodq   &\c\ENcdq   &\l\ENcdq   &\c;        &\l;    \\
@@ -559,56 +524,44 @@ introduced with this extension package.
 \bhrule
 \end{table}
 
-I draw your attention on the necessity of using the ligature
-\comando{''} for producing the simple apostrophe, which, by the
-way, in Greek typography  must always be followed by a space. The
-single tick mark \comando'\ produces an acute accent, not an
-apostrophe, this is why it is necessary to use the double tick
-mark ligature.  Actually also a double quote mark \verb+"+ followed by a space produces an apostrophe followed by a space.
+Please notice the necessity of using the ligature \comando{'{}'} for producing the simple apostrophe, which, by the way, in Greek typography  must always be followed by a space. The single tick mark \comando'\ produces an acute accent, not an apostrophe, this is why it is necessary to use the double tick mark ligature.  Actually also a double quote mark \verb+"+ followed by a space produces an apostrophe followed by a space.
 
 \section{Milesian and Attic numerals}
 
 The Milesian numerals should not worry anybody, because they are seldom used as
-isolated symbols; the \textsf{greek} or \textsf{polutonikogreek} language option or the \textsf{polutoniko} attribute of the Greek language with the \babel\ package offer the commands \comando\greeknumeral\ and
-\comando\Greeknumeral, that convert common arabic positive numbers in the
-Milesian counterparts within a Greek section of your document; the
-corresponding commands followed by an asterisk change the digamma glyph with
-the stigma one\footnote{The stigma version is the standard one with the
-\babel\ language support for Greek; with this package we
-adopted the digamma as the ``regular'' sign with the value of~6, and attributed
-stigma to the ``variant'', archaic representation of Milesian numbers. Here the archaic qoppa sign is used for the value 90; compare the archaic sign \textDidot{\coppa} with the modern one \textDidot{\koppa}.}:
-\begin{quote}\obeylines
-if you type \verb"\greeknumeral{1996}" you get \textLipsias{\greeknumeral{1996}}
-if you type \verb"\Greeknumeral{1996}" you get \textLipsias{\Greeknumeral{1996}}
-if you type \verb"\greeknumeral*{1996}" you get \textLipsias{\greeknumeral*{1996}}
-if you type \verb"\Greeknumeral*{1996}" you get \textLipsias{\Greeknumeral*{1996}}
-if you type \verb+\greeknumeral{123456}+ you get \textLipsias{\greeknumeral{123456}}
-if you type \verb+\greeknumeral{234567}+ you get \textLipsias{\greeknumeral{234567}}
-This was typeset on \begin{otherlanguage}{greek}\grtoday, \end{otherlanguage} which is \today.
+isolated symbols; the \textsf{greek} or \textsf{greek.ancient} language option or the \textsf{ancient} attribute of the Greek language with the \babel\ package offer the commands \comando\greeknumeral\ and
+\comando\Greeknumeral, that convert common Arabic positive numbers in the
+Milesian counterparts within a Greek section of the document; but the 2020 version of the \file{greek.ldf} file has been modified in such a way that it performs very well with modern Greek, but is missing some features when the real ancient Greek has to be typeset. Since its first version \pack{teubner} had to redefine the above macros so as to use the ancient Milesian symbols \textqoppa, \textvarstigma, \textsampi, with the possibility of using \textdigamma\ in place of \textqoppa.
+
+Therefore version~5.0 of \pack{teubner} redefines those two \comando\greeknumeral\ and \comando\Greeknumeral\ in order to restore the ancient features for the philologist benefit.\footnote{Notice, though, that this document is typeset with the \texttt{txfonts} and the Greek \texttt{txfontsb} fonts; the latter have only the raised digamma glyph which is not suited for “ancient” Greek numerals; in this display example we switched to the usual Latin Modern fonts.} 
+\begin{quote}\fontfamily{lmr}\selectfont\obeylines
+if you type \texttt{\comando\greeknumeral\{1996\}} you get %
+\greeknumeral{1996}
+if you type \texttt{\comando\Greeknumeral\{1996\}} you get %
+\Greeknumeral{1996}
+if you type \texttt{\comando\greeknumeral*{1996}} you get %
+\greeknumeral*{1996}
+if you type \texttt{\comando\Greeknumeral*{1996}} you get %
+\Greeknumeral*{1996}
+if you type \texttt{\comando\greeknumeral\{123456\}} you get %
+\greeknumeral{123456}
+This was typeset on \begin{otherlanguage}{greek}\grtoday, \end{otherlanguage} i.e. \the\day\ \ifcase\month\or
+        January\or February\or March\or April\or May\or June\or
+        July\or August\or September\or October\or November\or
+        December\fi\ \the\year.
 \end{quote}
 
 The \textsf{teubner} package offers also the possibility of typesetting the Attic numerals, without the need of loading Apostolos Syropoulos' \textsf{athnum} package; the functionality is the same, although the code is different; in order to avoid clashes, the \textsf{teubner} command for transforming Arabic numerals into Attic ones is \comando\AtticNumeral. As for the original macro, the maximum value that can be transformed is 99\,999, while, of course, no vanishing or negative numbers can be transformed:
 \begin{quote}\obeylines
-if you type \verb|\AtticNumeral{2015}| you get \textLipsias{\AtticNumeral{2015}}
-if you type \verb|\AtticNumeral{1999}| you get \textLipsias{\AtticNumeral{1999}}
-if you type \verb|\AtticNumeral{55555}| you get \textLipsias{\AtticNumeral{55555}}
+if you type \texttt{\comando\AtticNumeral\{2015\}} you get \textLipsias{\AtticNumeral{2015}}
+if you type \texttt{\comando\AtticNumeral\{1999\}} you get \textLipsias{\AtticNumeral{1999}}
+if you type \texttt{\comando\AtticNumeral\{55555\}} you get \textLipsias{\AtticNumeral{55555}}
 \end{quote}
 
 \section{New commands}
-This extension package introduces many new commands for
-typesetting Greek in a philological way. Most such commands are collected in table~\ref{t:extcomandi}.
-
-A short remark on the command \comando\ap: this useful command inserts
-\emph{anything} as a superscript of anything else; it works both in text mode
-and in math mode\footnote{Numerical superscripts or apices do not require math
-mode; numerical footnote labels are automatically inserted by \LaTeX's
-\comando\footnote\ command; non numerical footnote labels are easily inserted
-with \LaTeX's \comando\footnotemark\ and \comando\footnotetext\ commands with
-their optional arguments.}. In particular while typesetting a philological text
-in different languages and with different alphabets, \comando\ap\ typesets the
-superscript with the current language and alphabet; if any change is required,
-the \comando\ap's argument can contain any language or alphabet specific
-declaration. You can typeset something such as \textLipsias{Baq\'ulides\,\ap{\textlatin{a}}} by switching language and alphabet as required; the specific declarations and the commands contained in table~\ref{t:extcomandi} come handy also in these cases.
+This package introduces many new commands for typesetting Greek in a philological way. Most such commands are collected in table~\ref{t:extcomandi}.
+
+A short remark on the command \comando\ap: this useful command inserts \emph{anything} as a superscript of anything else; it works both in text mode and in math mode\footnote{Numerical superscripts or apices do not require math mode; numerical footnote labels are automatically inserted by \LaTeX's \comando\footnote\ command; non numerical footnote labels are easily inserted with \LaTeX's \comando\footnotemark\ and \comando\footnotetext\ commands with their optional arguments.}. In particular while typesetting a philological text in different languages and with different alphabets, \comando\ap\ typesets the superscript with the current language and alphabet; if any change is required, the \comando\ap's argument can contain any language or alphabet specific declaration. You can typeset something such as \textLipsias{Baq\'ulides\,\ap{\textlatin{a}}} by switching language and alphabet as required; the specific declarations and the commands contained in table~\ref{t:extcomandi} come handy also in these cases.
 
 
 \begin{table}[!p]\thrule%\centering
@@ -680,7 +633,7 @@ The metric glyph names are collected in table~\ref{t:metrics},
 while the declaration command is described hereafter.
 
 The syntax for that definition command is similar to that of
-{\comando\newcommand};
+\comando{\newcommand};
 \[
 \hbox{\comando\newmetrics\ARG{name}\ARG{definition}}
 \]
@@ -737,7 +690,7 @@ visible result as \c\hiatus, except for the fact that it does not
 occupy horizontal space; it is useful in the definitions of full
 verse metrics where a hiatus needs to be inserted between two
 consecutive metric symbols; for example: \longa\Hiatus\longa\,.\\
-\ap{2}\quad This extension package predefines some examples
+\ap{2}\quad This module predefines some examples
 of metric feet and complete verses.\\
 \ap{3}\quad Sometimes it might be convenient to use a shortcut
 for inserting the Aeolic bases
@@ -770,7 +723,7 @@ the composition of verses.
 In order to set poetry it is always possible to use the
 standard \LaTeX\ \texttt{verse} environment; nevertheless such
 simple environment is not suited for philological purposes, except
-perhaps for very short citations. This extension package contains
+perhaps for very short citations. This module contains
 three new environments with various levels of complexity. Due to
 their relative complexity an example will be given for each one
 with both the input code and the corresponding result. All three
@@ -975,10 +928,10 @@ j\rbrk 'arsos;\Dots[4]
 \end{VERSI}%}
 \NoLipsiakostext
 
-\item[\texttt{bracedmetrics}] This is an environment different
+\item[\texttt{bracedmetrics}] This environment is different
 from the preceding ones, although it always deals with verses.
 Its purpose is to set the verse metric lines grouped with a right
-brace, so  as to show the variants of a certain metric scheme.
+brace, so as to show the variants of a certain metric scheme.
 
 In order to align the metric variants and in order to place the
 right brace in the proper place it is necessary to fix  specific
@@ -1051,7 +1004,7 @@ which produces:
 \end{description}
 
 \section*{Acknowledgements}
-This project was  initially carried on with the help of Mr Paolo Ciacchi when he was writing his ancient Greek philology ``master thesis''. After he got his ``master's'' degree at the University of Trieste, I continued by myself, but I remain really indebted to Mr~Ciacchi.
+This project was  initially carried on with the help of Mr Paolo Ciacchi when he was writing his ancient Greek philology master thesis. After he got his master's degree at the University of Trieste, I continued by myself, but I remain really indebted to Mr~Ciacchi.
 
 
 \end{document}
diff --git a/Master/texmf-dist/doc/latex/teubner/teubner.pdf b/Master/texmf-dist/doc/latex/teubner/teubner.pdf
index 90735cb33b7..aeba0adac10 100644
--- a/Master/texmf-dist/doc/latex/teubner/teubner.pdf
+++ b/Master/texmf-dist/doc/latex/teubner/teubner.pdf
diff --git a/Master/texmf-dist/doc/latex/teubner/teubner.txt b/Master/texmf-dist/doc/latex/teubner/teubner.txt
index 6594a1ecc5c..d46ad3eb24d 100644
--- a/Master/texmf-dist/doc/latex/teubner/teubner.txt
+++ b/Master/texmf-dist/doc/latex/teubner/teubner.txt
@@ -1,15 +1,15 @@
              
-             THE TEUBNER PACKAGE VERSION 4.x OF MARCH 2016
+            THE TEUBNER PACKAGE VERSION 5/0 OF NOVEMBER 2020
                  EXTENSION FOR PHILOLOGICAL TYPESETTING
 
 
-Copyright  2001-2004-2016 Claudio Beccari
+Copyright  2001-2004-2020 Claudio Beccari
 
 The programs contained in this bundle can be  distributed and/or modified
 under the terms of the LaTeX Project Public License (LPPL),  version 1.3c 
 dated 2008-05-04 or later as it appears in 
-                     CTAN/macros/latex/base/lppl.tex.
 
+                     CTAN/macros/latex/base/lppl.tex.
 
 This bundle contains the following files
 
@@ -26,35 +26,41 @@ generated; teubner-doc.pdf  must be generated by running pdflatex on the
 source file teubner-doc.tex file. 
 These two .pdf files are already contained in the bundle.
 
-The previous versions 3.x of this packages used a  LGRaccents-glyphs.def 
-file, that now is not necessary, and is not contained in this bundle any 
-more.
-
 File teubner-doc.pdf  is the documentation file  that  shows what can be 
 done with this extension package and displays several examples.
 
-Version 4.x of the teubner package contains many new enhancements, among 
-which  it's worth  noting  the compliance  with  the new  Greek language 
-support to babel, that makes use of the encoding independent LICR (LaTeX
-Internal Character Representation) of the Greek characters & diacritics; 
-it contains  also the macros that allow  using  the  LGR encoded CBfonts 
-together with other  PostScript scalable  fonts;  the compatibility with 
-the Times and the Palatino eXtended fonts,  through the packages txfonts 
-and pxfonts,  are already  built in;  the compatibility  with  the Latin 
-Modern fonts was already available with version 2.x of this package.
-
-While this package was upgraded and uploaded to CTAN, Antonis Tsolomitis 
-uploaded  the package txfontsb  which adds the possibility of using nice 
-TX compatible Greek fonts when using the TX latin fonts so as to let the 
-users typeset their documents in mixed script. 
-The upright shape  resembles  the traditional Didot one,  and the italic 
-shape resembles the Lipsian one;  they come in both  the medium  and the 
-bold series and match the TX latin fonts pretty well. They probably match
-also the newer newtxtext fonts  by Michael Sharpe,  but since the latter
-have different font family names,  the automatically  produced .fd files 
-for adapting the  LGR encoded fonts  to the TX fonts are not  suited any
-more;  in order to have matching .fd files it is necessary to proceed as 
-with any other font collection different from the TX one
+Version 5.0 of the teubner  package is compliant with the Greek language 
+support to babel version 3.9g, that makes use of the encoding independent 
+LICR (LaTeX Internal Character Representation) of the Greek characters & 
+diacritics; it contains  also the macros that allow using the LGR encoded 
+CBfonts together with other PostScript scalable fonts; the compatibility 
+with the Times and the Palatino  eXtended  fonts,  through  the packages 
+txfonts and pxfonts, are already  built in;  the compatibility  with the 
+Latin Modern fonts was already available with version 2.x of this package.
+With  the upgrade of the Greek  support to babel  through file greek.ldf 
+version 1.10, teubner package versions  previous to 5.0 became unable to
+transform  Arabic numerals into the classical  Milesian and Attic number 
+representations.  From version 5.0 the teubner  package has been patched 
+in order to re-establish the above  number  transformations;  some other 
+improvements have been added that are transparent to the end user, since 
+deal with the package internal workings.  But these improvements require 
+a recent installation of the TeX system,  because they use interfaces to 
+the new LaTeX 3  language;  the minimum  date of the LaTeX kernel should 
+not be earlier than January 2019. 
+
+Some time ago  Antonis  Tsolomitis uploaded  the package txfontsb  which 
+adds the possibility of using nice TX compatible  Greek fonts when using 
+the TX latin  fonts so as to let the users  typeset  their  documents in 
+mixed script.  The upright shape  resembles  the traditional  Didot one,  
+and the italic shape  resembles the Lipsian one;  they come in both  the 
+medium  and the bold series and match the TX latin fonts pretty well. 
+They probably  match also  the newer newtxtext fonts  by Michael Sharpe,  
+but since the latter have different font family names, the automatically  
+produced .fd files for adapting  the  LGR encoded fonts  to the TX fonts 
+are not suited for the newtxtext  fonts; in order  to have  matching .fd 
+files it is necessary  to proceed in the same way as with any other font 
+collection different from the TX one;  the procedure is described in the 
+teubner-doc.pdf document.
 
 Although  Tsolomitis' fonts  satisfy very well  the everyday typesetting 
 necessities  of the Greek  users  and blend  well also  with the TX math 
@@ -78,21 +84,22 @@ file;  they must be moved  where TeX-the-program  can  find  them.  This
 depends very much  on your particular implementation  of the TeX system, 
 but if your system copes with the TDS (standard TeX Directory Structure)  
 and has a multiplicity  of different TeX  directory trees,  you probably  
-have a \localtexmf  rooted TDS,  or a /texmmf one in your Home directory 
+have a \localtexmf  rooted TDS,  or a /texmf one in your  Home directory 
 containing a tex directory tree which on turn contains a latex directory.  
 Under  the latter one  create a new directory  named, say,  teubner, and 
-move there teubner.sty, and teubnertx.sty.
+move to this folder the teubner.sty, and teubnertx.sty files.
 
-I suggest you to create a directory teubner  in the doc directory of the  
-locally  rooted structure  and move there  both teubner-doc.pdf  and the  
-teubner.pdf file that you get by running pdflatex directly on teubner.dtx.
+I suggest you to create  a directory /teubner in the  /doc  directory of 
+the locally  rooted structure  and move there  both teubner-doc.pdf  and 
+the teubner.pdf  file  that  you  get  by running  pdflatex  directly on 
+teubner.dtx.
 
 For what concerns fonts,  they should already be installed with a recent 
 TeX system  distribution;  this means  that  there are  already  all the 
 files  TeX-the-program  needs  in order  to do  its  work;  there is one 
 point, though, that  requires  full  attention;  the default  basic  TeX 
 system installation  loads only  the PostScript  fonts in size 10pt; all 
-other sizes are are obtained  by reducing or enlarging that single size. 
+other sizes are obtained  by reducing or enlarging that single size. 
 A complete  TeX system  installation  does not  exhibit this limitation. 
 There are also non standard scalable Type 1 fonts, such for example, the 
 Fourier  ones,  that  come  only  in one size,  the 10pt one;  for these 
@@ -113,7 +120,7 @@ got them pre-installed  with your  TeX system  distribution, may be they
 are not the latest  version.  The full  collection  has  been  redone in 
 the year 2007, and partially upgraded in 2010; the reduced collection is 
 a subset  of the full one.  Earlier distributions,  dated at least 2002, 
-might be compatible;  if you notice  something strange with the CBfonts, 
+might be compatible, but if you notice something strange with the CBfonts, 
 verify if your fonts are up to date.
 
 Another question you might ask yourself:  is my TeX system complete  and
@@ -131,7 +138,7 @@ CBfonts.
 After all these steps are done,  you  are  ready  to  use  your  teubner
 extensions;  it will not be  easy at the beginning,  because  there  are 
 hundreds  of new commands.  Be sure to have already thoroughly read  the 
-documentation file teubner-doc.pdf and that you have the hard copy close 
+documentation file  teubner-doc.pdf  and that you have a hard copy close 
 to you. 
 
 Remember,  though,  that most commands  are Latin names or abbreviations 
@@ -160,11 +167,11 @@ you use LaTeX, you know what are its pros and cons.
 
 Happy philological LaTeXing!
 
-Claudio Beccari                                        Turin, March 2016
+Claudio Beccari                                            November 2020
 Professor Emeritus
 Politecnico di Torino, Italy
 claudio dot beccari at gmail dot com
 
-PS: I underline  my former  professorship  in electronics,  in order to 
-stress  the point  that I am not  a philologist, therefore beware: this 
-work might simply be "trash" to the eyes of a real philologist!
+PS:  My former  professorship  is in electronics,  just  to stress  the 
+point that I am not  a philologist,  therefore beware:  this work might 
+simply be "trash" to the eyes of a real philologist!