teubner (18dec13)

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

5 files changed, 174 insertions, 154 deletions

diff --git a/Master/texmf-dist/doc/latex/teubner/README b/Master/texmf-dist/doc/latex/teubner/README
index 30a15089958..6d93c355b1a 100644
--- a/Master/texmf-dist/doc/latex/teubner/README
+++ b/Master/texmf-dist/doc/latex/teubner/README
@@ -1,4 +1,4 @@
-This accompanies the teubner bundle version 3.4a dated September 2013.
+This accompanies the teubner bundle version 4.x dated December 2013.
 
 Copyright 2010-2013 Claudio Beccari
 
@@ -19,25 +19,25 @@ The main purpose of this bundle is to provide classical philologists with some
 means for typesetting their documents that usually contain very specific notation.
 
 This new version allows the typesetter to use both "italic" shapes: the Olga-like
-and the Lipsian-like ones; it contains extended accent macros 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 scalable Latin Type~1 fonts; 
+and the Lipsian-like ones; it complies with the LICR (LaTeX Internal Character
+Representation) of the Greekk gluphs 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 scalable 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 the extraction
-of the byproduct files teubner.sty, teubnertx.sty, teubner.pdf, and 
-LGRaccents-glyphs.def. The latter might be separately input and used also without 
-the teubner bundle. The readable extended documentation file teubner-doc.pdf is 
-obtained by running pdflatex on the teubner-doc.tex file.
+Running pdflatex on the dtx file produces both the documentation and the 
+extraction of 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.
 
-Moreover this new version of the teubner package generates on the fly the font 
-description files necessary to use the LGR encoded Greek fonts with non TeX standard 
-PostScript fonts; for example it automatically generates the necessary files if using 
+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 CBgreek fonts.
+Please, be sure to work with a 2010 updated collection of the CBfonts, and with a 2013 uptdated version of the TeX system.
 
 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 4b8739c4244..5ca479111cd 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 12579b6c78f..46e1cf79e1d 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{2012/09/16}% see two lines ahead
+\def\workingdate{2013/12/10}% see two lines ahead
 \usepackage[boldLipsian,10pt,GlyphNames]% <--------  teubner options
            {teubner}[\workingdate]% <--- older versions don't work well
 \usepackage[scaled=0.90]{helvet}
@@ -45,27 +45,30 @@
 \thanks{This paper documents \texttt{teubner.sty} version \fileversion\ of \filedate.}\\
 An extension to the \textsf{greek} option\\ of the \babel\ package}
 \author{Claudio Beccari\thanks{\texttt{claudio dot beccari at gmail dot com}}}
-\date{Turin, April 2013}% <---- this is the date of the teubenr-doc document!
+\date{Turin, December 2013}% <---- this is the date of the teubenr-doc document!
 \def\comando#1{\expandafter\texttt\expandafter{\string#1}}
-\def\ARG#1{\texttt{\char123}$\langle$\textit{#1}$\rangle$\texttt{\char125}}
-\def\Arg#1{$\langle$\textit{#1}$\rangle$}
-\let\marg\ARG\let\meta\Arg
+\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\opt#1{\texttt{[}$\langle$\textit{#1}$\rangle$\texttt{]}}
+\def\opt#1{\texttt{[}\meta{#1}\texttt{]}}
 \def\g#1 {\textDidot{#1}}
 \def\l#1 {\textLipsias{#1}}
 \renewcommand*{\textfraction}{0}
 \renewcommand*{\topfraction}{1.}
 \renewcommand*{\bottomfraction}{.5}
 \def\acro#1{\expandafter\textsc\expandafter{\MakeLowercase{#1}}}
-\def\babel{\textsf{\slshape babel}}
 
 \def\thrule{\par\hrule\medskip}
 \def\bhrule{\par\medskip\hrule}
 
+\newcommand*\class[1]{\textsf{\slshape#1}}
+\newcommand*\pack[1]{\textsf{\slshape#1}}
+\def\babel{\pack{babel}}
 
 \advance\textheight80pt \advance\topmargin-40pt
-\begin{document}
+
+\begin{document}\errorcontextlines=20
 
 \maketitle
 {\columnseprule=0.4pt
@@ -77,9 +80,9 @@ An extension to the \textsf{greek} option\\ of the \babel\ package}
 %\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 3.x cannot yet typeset the critical
+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{ledmac}, but it may be considered a complement.
+and include also that facility. Apparently it is not incompatible with \textsf{eledmac}, but it may be considered a complement.
 %\end{sloppypar}
 
 {\tolerance=9999
@@ -89,35 +92,37 @@ 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
+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.
 
-This package is generally loaded by default with any major 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.
+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 CBgreek fonts; by default the scalable PostScript versions 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. Otherwise 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 ditribution 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 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.
 
-In any case this \texttt{teubner} extension package makes the \texttt{cbgreek} font collection (full or reduced) directly compatible by construction with both the CM fonts (OT1 and T1 encoded; the latter 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} 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.
 
-This short documentation will start by briefly recalling some peculiarities
+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 \texttt{teubner} extension is loaded in the usual way, but there are some simple rules to follow:
+The \pack{teubner} extension is loaded in the usual way, but there are some simple rules to follow:
 \begin{quote}
 \texttt{\string\usepackage}\opt{options}\brArg{teubner}
 \end{quote}
 
 
-Since \texttt{teubner} is an extension of the \texttt{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. 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 \texttt{teubner}, unless they want also to typeset Greek text. For using an alphabet 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/doc/latex/base/}.
+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. 
+
+\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/}.
 
 \section{Package options}
 
-The  options available to \texttt{teubner} are collected in table~\ref{t:opzioni} with their meaning and usefulness.
+The  options available to \pack{teubner} are collected in table~\ref{t:opzioni} with their meaning and usefulness.
 
 \begin{table}
 \thrule
@@ -131,20 +136,20 @@ 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 \texttt{teubner} extension package}\label{t:opzioni}
+\caption{Options for the \pack{teubner} extension package}\label{t:opzioni}
 \bhrule
 \end{table}
 
 You should never need (and therefore never use) the \textit{or} option for two reasons: $(a)$ glyph name macros are not needed for the first letter of any word since there are no kerning problems with a preceding letter; $(b)$ glyph name macros are insensitive to uppercasing.
 
-You might be forced to use the \textit{10pt} option because your Greek font collection is the minimal one. But if you are using \texttt{teubner}, you are likely to aim to the best possible typeset text; therefore you should download and install the full collection of the Greek CB fonts. This full collection is generally already available with any complete distribution of the \TeX\ system.
+\noindent\textbf{Warning}: You might need to use the \textit{10pt} option because your Greek font collection is the minimal one. But if you are using \texttt{teubner}, you are likely to seek the best possible typeset text; therefore you should download and install the full collection of the Greek CB fonts. This full collection is generally already available with any complete distribution of the \TeX\ system.
 
-If you are using Latin fonts different from the CM 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.
+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 \texttt{teubner} package (see below), the named accented glyphs should not be needed anymore; for backwards compatibility these accented glyph name macros are not defined by default, but are available if the \emph{GlyphNames} option is specified; if you are using the extended accent macros, you should not need them any more and, unless you specify this option, you avoid overloading the internal \TeX\ memory areas, thus leaving extra space for more useful extensions. Therefore 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).
+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.
 
 \section{The CB Greek fonts}
-The CB Greek fonts (full collection) come in  all shapes, sizes and series as the extended European 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
+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.
@@ -152,8 +157,8 @@ yet, at least.
 The regular shape has capital letters with serifs that are in the
 same style as the Latin capital ones, while the lower case letters
 derive from the design by Didot and are very common in all texts.
-This shape comes also in boldface, together with the two
-corresponding oblique (or slanted) versions. The CB fonts contain
+This shape comes also in boldface, together with the corresponding
+oblique (or slanted) versions. The CB fonts contain
 also the upright and slanted, medium and boldface small caps
 alphabets.
 
@@ -166,14 +171,14 @@ 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 family with serifed lower case letters.
+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 CM and LM fonts usually used with \LaTeX; this is easily achieved by passing the \emph{boldLipsian} option when invoking this \texttt{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 the previous versions of this package; now, in the same document, you can use both shapes and produce both versions: 
+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: 
 \foreignlanguage{greek}{\textit{Baq'ulides} 
 \textlatin{and} 
 \textli{Baq'ulides}}. 
@@ -184,33 +189,34 @@ But if you really want to permanently change the ``italic'' Greek font shape to
 \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.
 
-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 \texttt{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} extension 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 and shapes available.
+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 Greek 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 recognized; 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.}  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.
 
-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 Greek 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.
+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.
 
 Going more technical, the default family settings are stored into the three macros 
-\verb|\rmdefault|, \verb|\sfdefault|, \verb|\ttdefault|; the series and the shape symbols are stored in similar macros; these default macros are accessed every time a font characteristic switching declaration or command is used. In the background the \verb|\selectfont| macro is executed and during the whole process the \emph{current} font characteristic macros are updated. Such macros are \verb|\f@encoding|, \verb|\f@family|, \verb|\f@series|, and \verb|\f@shape|; therefore when just one characteristic is modified, the current value is stored in the relevant current value macro and used in order to create the association with the actual font to be used.
+\verb|\rmdefault|, \verb|\sfdefault|, \verb|\ttdefault|; the series and the shape symbols are stored in similar macros; these default macros are accessed every time a font characteristic switching declaration or command is used. In the background the \verb|\selectfont| macro is executed and during the whole process the \emph{current} font characteristic macros are updated. Such macros are \verb|\f@encoding|, \verb|\f@family|, \verb|\f@series|, and \verb|\f@shape|; therefore when just one characteristic is modified, the new value is stored in the relevant current value macro and used in order to create the association with the actual font to be used.
 
-If the font switching macros are used within a group, upon exiting that group the previous values are restored; but if declarations are used without a delimiting scope, there is no simple (universal) way to use another ready made declaration that resets valid font characteristics. 
+If the font switching macros are used within a group, upon exiting that group the previous values are restored; but if declarations are used without a delimiting scope, there is no simple (universal) way to use another ready-made declaration that resets valid font characteristics. 
 
 An example where the necessity of delimiting scopes is shown: suppose we are typesetting with T1 encoded LM roman medium normal (upright) fonts; then the current font characteristics codes are stored in the relevant macros as \texttt{T1}, \texttt{lmr}, \texttt{m}, \texttt{n}. We switch to Greek with a language setting declaration, and the current encoding is changed to \texttt{LGR}, but the other characteristics remain the same, therefore we would be typesetting with LGR encoded, CB Didot (upright) medium normal font. While typesetting in Greek we switch to Lipsian shape with a declaration such as \verb|\lishape|\footnote{Notice that the \texttt{\string\lishape} declaration and the corresponding text command \texttt{\string\textli} are defined in such a way that they switch to the Lipsian shape only when the Greek encoding LGR is in force; with other encodings they behave as the corresponding italic font commands. In spite of this the example being carried on is valid, because the \texttt{\string\lishape} \emph{declaration} is supposed to be issued while the Greek encoding was in force.}, and this declaration changes only the current shape characteristic, so that the four ones would be \texttt{LGR}, \texttt{lmr}, \texttt{m}, \texttt{li}. Up to this point everything runs smoothly because every characteristic that was set is present in the specific font family in use. At this point we revert to typesetting with the Latin script by means of a language switching declaration; the only change that takes place is on the encoding and the four characteristics would become \texttt{T1}, \texttt{lmr}, \texttt{m}, \texttt{li}, but\dots\ The Latin Modern fonts do not contain a Lipsian shape, therefore there is no actual font that meets the requirements and \LaTeX\ selects the \emph{error font}, the T1 encoded LM roman medium normal one, that in this case is the correct one, and apparently the font switching process achieved the correct result. This is only apparent: remember that the \emph{error font} was selected, not the right font. If the Latin family and the Greek family hadn't been the same, there would have been other difficulties and the error font would have been selected; this is why, if the user does not pay attention, when the default font should be, say, the TX font, after a switch to Greek, upon reverting to the Latin script the wrong font series or shape might be used. In the next paragraphs some indications are given in order to overcome this feature.
 
 All these technicalities are really too technical, but it's necessary to have some clues in order to find out why sometimes the font switching commands don't work as expected. In some cases the font description file might provide a smart substitution for missing fonts, but it is not always the case.
 
-In this package I tried to forecast most situations, but I am not sure I coped with every font characteristics combination.
+In this package I tried to forecast most situations, but I am not sure I coped with every font characteristic combination.
+
+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.}. 
 
-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 as the default other font family or families, open the the package file and take notice of the new family names; for each \meta{latin} family (serifed, sanserif, 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 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}
@@ -224,9 +230,12 @@ 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 if the \verb|\ifFamily| command, the boolean switch is automatically reset to \verb|\Lipsianfalse|.
 
-A small caveat: when you issue for the first time the command \verb|\ifFamily| you might not see 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 in any subsequent typesetting run.
+\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.
+
+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.
 
 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.
 
@@ -234,24 +243,22 @@ In order to insert \emph{short texts} in Greek, either in Didot upright or in Li
 
 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 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's syntactically correct and useful to input something such as:
 \begin{quote}
 \verb|\begin{Lipsiakostext}|\\
-$\langle$\textit{Greek text to be typeset with the Lipsian font}$\rangle$\\
+\meta{Greek text to be typeset with the Lipsian font}\\
 \verb|\end{Lipsiakostext}|
 \end{quote}
 
 
 \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 complete distribution. You can freely download those fonts from \textsc{ctan}, where you can find both the PostScript scalable ones and the driver files for generating their bit- (pixel-) maps 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: at the beginning of 2010, there is the multi\-platform shell editor \textsf{TeXworks}, that incorporates 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 approximately in the same way. For Mac platforms, besides the default shell editor and previewer TeXShop, and the multi-platform program TeXworks, one can proceed with Aquamacs as a shell editor and Skim as PDF previewer that work together so as to allow direct and inverse search. 
-There are also \textsf{TeXmaker} and \textsf{TeXstudio}, multi platform shell editors, that perform very well with their internal PDF readers; they exhibit other useful features that may appeal to many users. Probably there are other such programs, but I know and have direct experience only with the above mentioned ones.
- 
+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. 
  
 \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 CBfont collection (may be you should update your whole \TeX\ system installation).
+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 updated \texttt{.tfm} files add some ligature and kerning information that is missing from the ``old'' ones. The Type~1 \texttt{pbf} 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}
@@ -285,12 +292,14 @@ boundary after a sigma; therefore if you type \texttt{sv}, you get
 
 The invisible character \texttt{v} may be used also as a support
 for (apparently) isolated accents, especially when macros have to
-be used; if you type \verb"\={v}" you get
-\enspace\textDidot{\=v}\enspace, while if you omit the invisible
-\texttt{v} you get \enspace\textDidot{\={}}\enspace.
+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.
 
 Accents, spirits and dieresis may be input \emph{before} each letter
-(prefix notation) without using any particular control sequence;
+(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 must be prefixed (in any order), while the iota
@@ -307,16 +316,16 @@ 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 all almost 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 the standard \LaTeX\ commands \verb|\=| and \verb|\u| respectively
-in order to use them as accents. 
+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}. 
 
-Thanks to Günter Milde, whom I thank very much and acknowledge his work, this package  uses an extended set of macros that involve only the ``upper'' diacritics; they can be used in place of the combining diacritics described in table~\ref{t:accenti}; simply the accents 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.
+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 resort 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.
 
 
 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}. 
@@ -333,9 +342,9 @@ Example     & \multicolumn1c{Syntax}            & Example    & \multicolumn1c{Sy
 \g \'{a}    & \comando\A\ARG{letter}\ap{1}     & \g\Ab{a}    & \comando\Ab\ARG{letter}  \\
 \g \~{a}    & \comando\C\ARG{letter}\ap{1}     & \g\Gb{a}    & \comando\Gb\ARG{letter}  \\
 \g \"{i}    & \comando\D\ARG{letter}\ap{1}     & \g\Arb{a}   & \comando\Arb\ARG{letter} \\
-\g \u{a}    & \comando\u\ARG{letter}           & \g\Grb{a}   & \comando\Grb\ARG{letter} \\
+\g \B{a}    & \comando\B\ARG{letter}\ap{4}     & \g\Grb{a}   & \comando\Grb\ARG{letter} \\
 \g \U{ai}   & \comando\U\ARG{diphthong}        & \g\Asb{a}   & \comando\Asb\ARG{letter} \\
-\g \=a      & \comando\=\ARG{letter}           & \g\Gsb{a}   & \comando\Gsb\ARG{letter} \\
+\g \M{a}      & \comando\M\ARG{letter}\ap{4}   & \g\Gsb{a}   & \comando\Gsb\ARG{letter} \\
 \g \>a      & \comando\>\ARG{letter}\ap{3}     & \g\Am{a}    & \comando\Am\ARG{letter}  \\
 \g \<a      & \comando\<\ARG{letter}\ap{3}     & \g\Gm{a}    & \comando\Gm\ARG{letter}  \\
 \g \r{a}    & \comando\r\ARG{letter}           & \g\Cm{a}    & \comando\Cm\ARG{letter}  \\
@@ -356,13 +365,14 @@ Example     & \multicolumn1c{Syntax}            & Example    & \multicolumn1c{Sy
 \caption{Accent macros}\label{t:accentmacros}
 \vskip\baselineskip
 REMARKS\\[3pt]\footnotesize
-\ap{1}\quad These four commands superimpose the corresponding accent over the \meta{letter} belonging to the Greek alphabet; the corresponding commands \comando\`, \comando\', \comando\~, and \comando\" play the same rôle also with non Greek letters; this allows the stacking of several accents on the same base \meta{letter}. \\
-\ap{2}\quad Most commands may be used also with latin letters.\\
-\ap{3}\quad While typesetting in Greek within a \texttt{tabbing} environment,
+\mbox{\quad}\ap{1}These four commands superimpose the corresponding accent over the \meta{letter} belonging to the Greek alphabet; the corresponding commands \comando\`, \comando\', \comando\~, and \comando\" play the same rôle also with non Greek letters; this allows the stacking of several accents on the same base \meta{letter}. \\
+\mbox{\quad}\ap{2}Most commands may be used also with latin letters.\\
+\mbox{\quad}\ap{3}While typesetting in Greek within a \texttt{tabbing} environment,
 both commands \comando\> and \comando\< play a different r\^ole as tab shifters;
 in this case either \comando\s\ and \comando\r\ are used for the spirit macros, or 
 the standard ligature mechanism is used, especially if the spirit diacritics 
-fall on the very first vowel of a word. Suggestion; never use the \texttt{tabbing} environment; there are more effective ways to align chunks of text, for example the \texttt{tabular} environment.
+fall on the very first vowel of a word. Suggestion; never use the \texttt{tabbing} environment; there are more effective ways to align chunks of text, for example the \texttt{tabular} environment.\\
+\mbox{\quad}\ap{4}In \pack{teubner} versions preceding 4.0 macros for typesetting macrons and breves in Greek had the same name as the corresponding macros used when typesetting with Latin script, that is \comando\=\ and \comando\u. With the new Greek support for the \pack{babel} package that was implemented during year 2013, the Latin macros were not functional any more in the proper way, and were updated in \pack{teubner} version 4.0 with new names.
 \bhrule
 \end{table}
 
@@ -370,19 +380,19 @@ fall on the very first vowel of a word. Suggestion; never use the \texttt{tabbin
 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 between tau and the accented omicron is hardly 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.}. 
+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.
 
 For this reason two mechanisms are implemented in this package:
 \begin{enumerate}\itemsep=0pt\parsep=0pt
-\item  the extended accent macros suggested by Günter Milde have been adapted to this package in order to have accent macros that help fetching the accented character in the font table, and
+\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 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 capitalizing the upper diacritics must be written at the left of the initial letter); for example\footnote{In the capitalized 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 polutoniko 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 examle 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 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{tenbner} package: a set of macros has been defined such that it is
+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
@@ -390,8 +400,8 @@ complex glyph in a certain order, precisely every macro is made
 up as such:
 \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 capitalized vowels I~or~U;
-\item the next optional character is the code for dieresis, smooth or rough spirit, with one of the letters d, s, r;
+\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.
@@ -446,31 +456,32 @@ subscript may still be used also when the accent--vowel combinations are used.}
 \caption{Glyph name macros}\label{t:compoundvowels}
 \bigskip
 REMARKS\\[3pt]\footnotesize
-\ap{1}\quad Some users remarked that this \verb|\og| command may conflict the homonymous command available when typesetting French texts with the \texttt{french} option to \texttt{babel} in force; For this reason it's necessary to use \verb|\`o| in its place, therefore using the extended accent macros.\par
-\leavevmode\ap{2}\quad As mentioned in the body of this text the  command
-\comando{\or} is incompatible with the primitive \TeX\ command with the same name, therefore it is necessary to use the extend accent macro \verb|\<o|.\par
-\leavevmode\ap{3}\quad In both cases  macros are unnecessary, specifically for \verb|\>o|, since an initial accented letter has no preceding letter which whom some kerning might be necessary; therefore at the start of a word always use \verb|'o| or \verb|<o|, and use \verb|\'o| only in a word internal position, should some kerning be necessary; actually the shape of the omicron seldom requires any kerning.
+\mbox{\quad}\ap{1}Some users remarked that with previous \pack{teubner} versions  \verb|\og| macro conflicted with the homonymous command available when typesetting French texts with the \texttt{french} option to \babel\ in force; for this reason it's necessary to use  \verb|\`o| in its place.\par
+\mbox{\quad}\ap{2}As mentioned in the body of this text the  command
+\comando{\or} is incompatible with the primitive \TeX\ command with the same name, therefore it is necessary to use  \verb|\<o| in its place.\par
+\mbox{\quad}\ap{3}In both cases  macros are unnecessary, specifically for \verb|\<o|, since an initial accented letter has no preceding letter whith whom some kerning might be necessary; therefore at the start of a word use \verb|'o| or \verb|<o|, and use \verb|\'o| in a word internal position, should some kerning be necessary; actually the shape of the omicron seldom requires any kerning.
 \bhrule
 \end{table}
 
 What I suggest is to typeset your paper with the regular accent
 vowel ligatures and to substitute them in the final revision with
-the extended accent macros or the glyph name macros only in those instances where the lack of kerning is disturbing. The extended accent  macros should set forth less conflicts with other packages and should be the first choice when cleaning up the final revision. May be the glyph names will be eliminated in future releases of this package. Up to now these glyph name macros are disabled by default but, if the option \emph{GlyphNames} is specified in the call statement to the \texttt{teubner.sty} package, they are turned on and become available.
+the extended accent macros or the glyph name macros only in those instances where the lack of kerning is disturbing. The extended accent macros should set forth less conflicts with other packages and should be the first choice when cleaning up the final revision. The glyph names will be kept in future releases of this package just for backwards compatibility. Up to now these glyph name macros are disabled by default but, if the option \emph{GlyphNames} is specified in the call statement to the \texttt{teubner.sty} package, they are turned on and become available.
+
 
 
-\section{Upper case initials and capitalized text}
+\section{Upper case initials and capitalised text}
 As we have seen in the previous sections the ligature and kerning mechanisms are strictly connected and the extended accent macros may be useful in solving certain situations. The suggestion at the end of the previous section holds true, but some remarks must be underlined in order to use at its best the coexistence of both methods for using the accented glyphs.
 
-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 dieresis.
+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 polutoniko spelling, since this package \texttt{teubner} sets this spelling as the default one; nobody forbids to spell in monotoniko even when the polutoniko 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 capitalizing or uppercasing, and if you follow the suggestions given in this section you should not meet any particular inconvenience; in particular, I stress this point here again: \emph{never use the extended accent macros for marking the initial vowel but use only the accent vowel ligatures}.
+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.
 
-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 behavior. 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 
+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.
 
 
@@ -488,12 +499,12 @@ 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 wrong because \verb|\MakeUppercase| does not act on macros, but \verb|\>| is a macro, while \verb|'| is just a character that, as all the other accents, has an uppercase code mapped to a zero height dummy invisible character, therefore when conversion to uppercase is performed, the smooth spirit goes over a zero height invisible character, and that's why it appears to be sitting on the baseline; 5) is wrong because in all-caps spelling accents should not be shown. Case 6) displays the result of using the accented glyph names which are not subject to capitalization 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 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. 
 
-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; by simply inverting the sequence of the dieresis and the acute accent, case 8),  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 but the capital iota has both the dieresis and the acute accent, while the latter should be absent; 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 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.
 
 When using small caps or caps and small caps, in other words, when using the 
-\verb|\scshape| declaration or the \verb|\textsc| command you use pay attention to other details; for example:
+\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}\\
@@ -503,9 +514,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, except the the extended accent macros use a different definition for the accent macro so as to being able to put the accent on any glyph. But accents are apparently used in French also when proper names are typeset in caps and small caps, contrary to Greek, and 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 suitable for supporting any diacritic mark at the proper height. This remark comes from a mail exchange with Julien Browaeys who pointed out this specific typesetting French tradition. Julien Browaeys spotted also a sneaky glitch in the set of extended accent macros that was corrected thanks to his bug notification. I am pleased to acknowledge his contributions.
+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 only ligatures before the first vowel and use \verb|\"| (in the proper sequence with other accents) for the internal diereses, as in cases 3) and 8) above; don't use extended accent macros for the other internal accents. If you need to correct internal kerning by using internal extended accent macros, play with the sectioning command optional argument in order to use the right strategy for the correct typesetting of both the sectioning title and the page heading. The worst it can happen is a wrong kerning in the table of contents entry. 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.
+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.
 
 \section{Other Greek symbols}
 Other Greek symbols may be obtained with ligatures or explicit
@@ -559,7 +570,7 @@ if you type \verb+\greeknumeral{123456}+ you get \textLipsias{\greeknumeral{1234
 
 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{2012}| you get \textLipsias{\AtticNumeral{2012}}
+if you type \verb|\AtticNumeral{2013}| you get \textLipsias{\AtticNumeral{2013}}
 if you type \verb|\AtticNumeral{1999}| you get \textLipsias{\AtticNumeral{1999}}
 \end{quote}
 
@@ -580,7 +591,7 @@ 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
+\begin{table}[!p]\thrule%\centering
 \let\c\comando
 \resizebox*{\textwidth}{!}{\footnotesize
 \begin{tabular}{cl|cl}
@@ -588,7 +599,7 @@ Example                 & Syntax                        &Example
 \l{Baq\'ulides}         & (declaration)                 &abcde                  & (declaration)                 \\
 \l{Baq\'ulides}         & \c\textLipsias\ARG{text}      &\l{\lesp{abg}}         &\c\lesp\ARG{text}              \\
 \g{Baq\'ulides}         &\c\textDidot\ARG{text}         &\LitNil                &\c\LitNil                      \\
-text                    & \c\textlatin\ARG{text}        &\cap{g}                &\c\cap\ARG{letter}             \\
+text                    & \c\textlatin\ARG{text}        &\cap{g}                &\c{\cap}\ARG{letter}\ap{($a$)} \\
 \l\frapar{Baq\'ulides}  & \c\frapar\ARG{text}           &\Coronis               &\c\Coronis                     \\
 (                       & \c\lpar                       &\lmqi                  &\c\lmqi                        \\
 )                       &\c\rpar                        &\rmqi                  &\c\rmqi                        \\
@@ -628,8 +639,11 @@ text                    & \c\textlatin\ARG{text}        &\cap{g}
 \splus                  &\c\splus                       &\stimes                &\c\stimes                  
 \end{tabular}%
 }
+\bhrule\smallskip
+
+{\footnotesize\mbox{\ap{($a$)}\enspace}Ansten M\o rch Klev spottes a conflict 
+with the Homonymous math command; this is now resolved. Thank you Ansten.\par}
 \caption{Extended commands}\label{t:extcomandi}
-\bhrule
 \end{table}
 
 
diff --git a/Master/texmf-dist/doc/latex/teubner/teubner.pdf b/Master/texmf-dist/doc/latex/teubner/teubner.pdf
index 405559dcb19..e6d98803ac4 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 d3732df0c1e..0939d0cb493 100644
--- a/Master/texmf-dist/doc/latex/teubner/teubner.txt
+++ b/Master/texmf-dist/doc/latex/teubner/teubner.txt
@@ -1,4 +1,4 @@
-             THE TEUBNER PACKAGE VERSION 3.4a OF SEPTEMBER 2013
+             THE TEUBNER PACKAGE VERSION 4.x OF DECEMBER 2013
                  EXTENSION FOR PHILOLOGICAL TYPESETTING
 
 
@@ -16,25 +16,31 @@ README               short information abut installing this bundle
 teubner.txt          this file
 teubner.dtx          documented TeX file
 teubner-doc.tex      documentation file
+teubner.pdf          technical documentation
+teubner-doc.pdf      usage documentation
 
-By running pdflatex on teubner.dtx in addition to the documentation file 
-teubner.pdf,  the byproduct files teubner.sty, teubnertx.sty, LGRaccents-
-glyphs.def are generated; teubner-doc.pdf  must be generated  by running 
-pdflatex on the source file teubner-doc.tex file. The two mentioned .pdf
- files are already contained in the bundle
+By running  pdflatex  on teubner.dtx  in addition  to the  documentation 
+file teubner.pdf,  the byproduct files  teubner.sty,  teubnertx.sty, are 
+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 3.x of the teubner package contains many new enhancements, among 
-which  it's worth  noting  the new  extended  accent macros  (that avoid 
-kerning  problems  that might show up using the ligature  mechanism) and 
-the  new  macros  that allow  to use  the LGR  encoded  CBgreek fonts in 
-conjunction  with other  PostScript  scalable  fonts;  the compatibility 
-with the Times eXtended  and  the  Palatino  eXtended  fonts, accessible  
-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 the teubner package.
+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 
@@ -47,7 +53,7 @@ bold series and match the TX latin fonts pretty well.
 Although  Tsolomitis' fonts  satisfy very well  the everyday typesetting 
 necessities  of the Greek  users  and blend  well also  with the TX math 
 fonts, they do not satisfy the requirements of the teubner package. This 
-is why the processing of the teubner.dtx file  generates  also  file the
+is why the processing of the teubner.dtx file  generates  also  the file
 teubnertx.sty  that is being  input at begin  document time  if the user 
 specified the TX fonts by calling the txfonts package. 
 
@@ -57,44 +63,44 @@ distribution  already  provided  for  it;  may  be  your  TeX  system is
 configured  to load  missing  packages  on the fly.  In any case you can 
 check and possibly run your Package Manager (with MiKTeX follow the path 
 Programs|MiKTeX Settings|Packages;   with TeXlive and MacTeX   (if their 
-installation configuration was not the default complete one) run tlmgr).
+installation configuration was not the default complete one) run tlmgr.
   
 If you feel more comfortable to do everything by yourself and/or want to 
 make  a personal  installation,  run teubner.dtx  through  pdflatex; the 
-generated  files are teubner.sty and LGRaccents-glyphs.def,  besides the 
-aforementioned  teubnertx.sty  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 
-root directory structures,  you probably  have a  \localtexmf rooted TDS, 
-or a /texmmf one in your Home directory containing a tex directory which 
-on turn contains  a latex directory.  Under the latter one  create a new 
-directory named, say, teubner, and move there teubner.sty, teubnertx.sty, 
-and LGRaccents-glyphs.def.
+generated  files are  teubner.sty  and the aforementioned  teubnertx.sty  
+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 
+containing  a tex directory  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.
 
 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
-teubner.pdf  that you  get  by running pdflatex directly on teubner.dtx.
+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 n eeds  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. 
-A complete TeX system installation does not exhibit  this limitation. 
+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. 
+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 fonts 
-it is not strictly necessary todo the same with the sizes of the CBfonts,  
-but if you prefer you can.
-
-In any case the teubner package copes  with this situation if you specify 
-the "10pt" option   when calling  this package,  but if you want  to have  
-perfect  optical sizes,  then  you should  download  from  CTAN  the full  
-collection  and  install it  in  your  computer.   The details  for  this 
-installation require  you read with due attention  the instructions  that 
-come  with  your  TeX system  distribution;  it's not  difficult,  but it 
-requires  to be very careful  at every step.  Remember, though, that your 
+Fourier  ones,  that  come  only  in one size,  the 10pt one;  for these 
+fonts it is not strictly necessary  to do the same with the sizes of the 
+CBfonts, but if you prefer you can.
+
+In any case the teubner package copes with this situation if you specify 
+the "10pt" option   when calling  this package, but if you want  to have  
+perfect  optical sizes,  then  you should  download from  CTAN  the full  
+collection  and  install it  in  your  computer.  The details  for  this 
+installation require  you read with due attention  the instructions that 
+come  with  your  TeX system  distribution;  it's not  difficult, but it 
+requires  to be very careful  at every step. Remember, though, that your 
 Package Manager can do all the work for you.
 
 It's important to control that you have the latest CBfonts;  even if you 
@@ -108,7 +114,7 @@ verify if your fonts are up to date.
 Another question you might ask yourself:  is my TeX system complete  and
 up to date? The fact you installed a TeX system and you did not have the
 CBfonts may be an index that  you still have the babel package locked at
-a  version  number  earlier than 3.7. I suggest you to upgrade  your TeX
+a  version  number  earlier than 3.9g. I suggest you to upgrade your TeX
 system to the most up to date one you can find on CTAN.
 
 Connected  to this point  there is  the question  of the updated  metric 
@@ -124,14 +130,14 @@ documentation file teubner-doc.pdf and that you have the hard copy close
 to you. 
 
 Remember,  though,  that most commands  are Latin names or abbreviations 
-that  should  be familiar  to any philologist  specialized in classical/
-ancient European languages, such as classical Greek, Latin, et cetera.
+that  should  be familiar  to any philologist  specialised in classical/
+ancient European languages, such as classical Greek, Latin, and so on.
 
 This set of extension  commands  has been tested  in several  documents;
-nevertheless I prepared them as a hobby, trying to help a friend philolo-
-gist. I hope this package may be useful also to you, but I must disclaim 
-any liability for any unwanted results you might get, including the worst  
-possible things that may happen to anybody using a computer.  
+nevertheless  I prepared them as a hobby,  trying to help  a philologist 
+friend.  I hope  this  package  may be useful  also to you,  but  I must 
+disclaim any liability for any unwanted results you might get, including 
+the worst possible things that may happen to anybody using a computer.  
 
 I will not write down any strong disclaimer sentence in capital letters,  
 because it should be absolutely evident that I did something  I consider
@@ -140,7 +146,7 @@ useful,  but is up to you  to decide to use it and face the consequences
 
 If you find this package of some utility but you find some errors and/or    
 some glitches,  please write me by e-mail (see below).  If you'd like me 
-to realize some other commands,  please send me  by e-mail  your request  
+to realise some other commands,  please send me  by e-mail  your request  
 together with a scanned image containing the visual result you'd like to 
 obtain. I don't guarantee I'll be able to satisfy your request, but I'll 
 give it a try.  In any case  don't ask for things LaTeX can't do; and if 
@@ -148,11 +154,11 @@ you use LaTeX, you know what are its pros and cons.
 
 Happy philological LaTeXing!
 
-Claudio Beccari                             Turin, 29 of September 2013
+Claudio Beccari                                    Turin, December 2013
 Former Professor of Electronics
 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 be simply "trash" to the eyes of a real philologist!
\ No newline at end of file
+work might be simply "trash" to the eyes of a real philologist!