teubner 3.1 (4sep11)

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

6 files changed, 70 insertions, 50 deletions

diff --git a/Master/texmf-dist/doc/latex/teubner/README b/Master/texmf-dist/doc/latex/teubner/README
index de0ec732d53..fb5a626880b 100644
--- a/Master/texmf-dist/doc/latex/teubner/README
+++ b/Master/texmf-dist/doc/latex/teubner/README
@@ -1,6 +1,6 @@
-This accompanies the teubner bundle version 3.1 dated November 2010.
+This accompanies the teubner bundle version 3.1 dated September 2011.
 
-Copyright 2010 Claudio Beccari
+Copyright 2010-2011 Claudio Beccari
 
 The  bundle contains the files
 
@@ -19,17 +19,21 @@ means for typesetting their documents that usually contain very specific notatio
 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
-CBgreek fonts; 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-doc.pdf, and LGRaccents-gyphs.def. The 
-latter might be separately input and used also without the teubner bundle. 
-
-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 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.
+CBgreek fonts; 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-gyphs.def. The latter might be separately input and used also without 
+the teubner bundle. The readable extend 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 
+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.
 
diff --git a/Master/texmf-dist/doc/latex/teubner/teubner-doc.pdf b/Master/texmf-dist/doc/latex/teubner/teubner-doc.pdf
index 75d8946eec5..07250484b00 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 2d8db6fa813..3020576dacf 100644
--- a/Master/texmf-dist/doc/latex/teubner/teubner-doc.tex
+++ b/Master/texmf-dist/doc/latex/teubner/teubner-doc.tex
@@ -1,5 +1,5 @@
 \documentclass[12pt,a4paper]{article}
-\usepackage[latin1]{inputenc}
+%\usepackage[latin1]{inputenc}
 %\usepackage{lmodern}
 \usepackage{txfonts}
 %\usepackage{pxfonts}
@@ -41,7 +41,7 @@
 \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}
-\date{Turin, June 2010}% <---- this is the date of the teubenr-doc document!
+\date{Turin, August 2011}% <---- this is the date of the teubenr-doc document!
 \def\comando#1{\texttt{\expandafter\string\noexpand#1}}
 \def\ARG#1{\texttt{\char123}$\langle$\textit{#1}$\rangle$\texttt{\char125}}
 \def\Arg#1{$\langle$\textit{#1}$\rangle$}
@@ -78,7 +78,8 @@ 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.
 %\end{sloppypar}
 
-This document does not substitute the official package documentation \texttt{teubner.dtx} and its typeset version \texttt{teubner.pdf}; it extends the information contained into those files.
+{\tolerance=9999
+This document does not substitute the official package documentation \texttt{teubner.dtx} and its typeset version \texttt{teubner.pdf}; it extends the information contained into those files.\par}
 
 This package is supposed to work with my CB fonts available on the
 Comprehensive \TeX\ Archive Network (\textsc{ctan}); one of the actions of this
@@ -210,11 +211,17 @@ fonts\footnote{I chose the CM Greek families, instead of the LM ones, because on
 \end{quote}
 right after the \verb|\usepackage| command with which you call that package.
 
-Example: suppose you want to use the regular Iwona fonts to replace the default roman normal serifed fonts; then you should load the package \texttt{iwona} \emph{after} the \texttt{teubner} extension and specify:
+Example: suppose you want to use the regular Fourier fonts to replace the default roman normal serifed fonts; then you should load the package \texttt{fourier} \emph{after} the \texttt{teubner} extension and specify:
 \begin{verbatim}
-\usepackage{iwona}
-\ifFamily{iwona}{cmr}
+\usepackage{fourier}
+\Lipiandtrue
+\ifFamily{futs}{cmr}
 \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{cuts} 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{cuts}. 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 font name and the 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.
+
+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.
 
 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.
 
@@ -232,9 +239,10 @@ $\langle$\textit{Greek text to be typeset with the Lipsian font}$\rangle$\\
 
 \section{Font installation}
 In order to use the Greek CB fonts and the extensions provided with this
-package, you need to install them. You can freely download those fonts from
+package, you need to install them, if they are not already installed by default when you install your preferred \TeX\ system 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. Probably there are other such programs, but I know only the above mentioned ones.
+ 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 editors; 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.
  
  
 \section{\TeX\ font metric files}
@@ -305,7 +313,7 @@ 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. 
 
-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|} 
+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.
 
 
@@ -351,7 +359,7 @@ attribute \textsf{polutoniko} was specified for the
 Greek language with \babel\ v.3.7. At the same time it must be followed by its argument without using curly braces; if a Greek circumflex accent is desired over a vowel that ordinarily does not receive such an accent, or on any other symbol, then use \texttt{\string\GRcirc}\ARG{symbol} instead.\\
 \ap{2}\quad Most commands may be used also with latin letters.\\
 \ap{3}\quad While typesetting in Greek within a \texttt{tabbing} environment,
-both commands \comando\> and \comando\< play a different rôle as tab shifters;
+both commands \comando\> and \comando\< play a different r�le 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.
@@ -368,7 +376,7 @@ section, the spirit marker and the acute accent inhibit the kerning mechanism wi
 
 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 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 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\'OS} but you have to use the macros of 
@@ -399,47 +407,48 @@ kernings and ligatures; this is why the postfixed ligature for the iota
 subscript may still be used also when the accent--vowel combinations are used.}
 
 \begin{table}[tb]\thrule\let\c\comando\let\l\textLipsias
-\def\V{\rule{0pt}{2.5ex}}
+\def\V{\rule{0pt}{2.5ex}}\def\D{\rule[-1.2ex]{0pt}{2ex}}
 \makebox[\textwidth]{%
-\begin{tabular}{lclclclclclc}
+\begin{tabular}{*6{lc}}
 \c\aa   &\l\aa  &\c\ag  &\l\ag  &\c\ac  &\l\ac  &\c\ai  &\l\ai  &\c\ar  &\l\ar  &\c\as  &\l\as  \\
 \c\asa  &\l\asa &\c\asg &\l\asg &\c\asc &\l\asc &\c\asi &\l\asi &\c\aai &\l\aai \\
 \c\ara  &\l\ara &\c\arg &\l\arg &\c\arc &\l\arc &\c\ari &\l\ari &\c\agi &\l\agi &\c\aci &\l\aci \\
-\c\arai &\l\arai&\c\argi&\l\argi&\c\arci&\l\arci&\c\asai&\l\asai&\c\asgi&\l\asgi&\c\asci&\l\asci\\
+\c\arai &\l\arai&\c\argi&\l\argi&\c\arci&\l\arci&\c\asai&\l\asai&\c\asgi&\l\asgi&\c\asci&\l\asci\D\\
 \hline
 \c\ha   &\l\ha  &\c\hg  &\l\hg  &\c\hc  &\l\hc  &\c\hi  &\l\hi  &\c\hr  &\l\hr  &\c\hs  &\l\hs  \\
 \c\hsa  &\l\hsa &\c\hsg &\l\hsg &\c\hsc &\l\hsc &\c\hsi &\l\hsi &\c\hai &\l\hai \\
 \c\hra  &\l\hra &\c\hrg &\l\hrg &\c\hrc &\l\hrc &\c\hri &\l\hri &\c\hgi &\l\hgi &\c\hci &\l\hci \\
-\c\hrai &\l\hrai&\c\hrgi&\l\hrgi&\c\hrci&\l\hrci&\c\hsai&\l\hsai&\c\hsgi&\l\hsgi&\c\hsci&\l\hsci\\
+\c\hrai &\l\hrai&\c\hrgi&\l\hrgi&\c\hrci&\l\hrci&\c\hsai&\l\hsai&\c\hsgi&\l\hsgi&\c\hsci&\l\hsci\D\\
 \hline
 \c\wa   &\l\wa  &\c\wg  &\l\wg  &\c\wc  &\l\wc  &\c\wi  &\l\wi  &\c\wr  &\l\wr  &\c\ws  &\l\ws  \\
 \c\wsa  &\l\wsa &\c\wsg &\l\wsg &\c\wsc &\l\wsc &\c\wsi &\l\wsi &\c\wai &\l\wai \\
 \c\wra  &\l\wra &\c\wrg &\l\wrg &\c\wrc &\l\wrc &\c\wri &\l\wri &\c\wgi &\l\wgi &\c\wci &\l\wci \\
-\c\wrai &\l\wrai&\c\wrgi&\l\wrgi&\c\wrci&\l\wrci&\c\wsai&\l\wsai&\c\wsgi&\l\wsgi&\c\wsci&\l\wsci\\
+\c\wrai &\l\wrai&\c\wrgi&\l\wrgi&\c\wrci&\l\wrci&\c\wsai&\l\wsai&\c\wsgi&\l\wsgi&\c\wsci&\l\wsci\D\\
 \hline
 \c\ia   &\l\ia  &\c\ig  &\l\ig  &\c\ic  &\l\ic  &\c\ir  &\l\ir  &\c\is  &\l\is  \\
 \c\isa  &\l\isa &\c\isg &\l\isg &\c\isc &\l\isc &\c\ida &\l\ida &\c\idg &\l\idg \\
-\c\ira  &\l\ira &\c\irg &\l\irg &\c\irc &\l\irc &\c\idc &\l\idc &\c\id  &\l\id  \\
+\c\ira  &\l\ira &\c\irg &\l\irg &\c\irc &\l\irc &\c\idc &\l\idc &\c\id  &\l\id  &\c\Id  &\l\Id  \\
 \hline
 \c\ua   &\l\ua  &\c\ug  &\l\ug  &\c\uc  &\l\uc  &\c\ur  &\l\ur  &\c\us  &\l\us  \\
 \c\usa  &\l\usa &\c\usg &\l\usg &\c\usc &\l\usc &\c\uda &\l\uda &\c\udg &\l\udg \\
-\c\ura  &\l\ura &\c\urg &\l\urg &\c\urc &\l\urc &\c\udc &\l\udc &\c\ud  &\l\ud \\
+\c\ura  &\l\ura &\c\urg &\l\urg &\c\urc &\l\urc &\c\udc &\l\udc &\c\ud  &\l\ud &\c\Ud   &\l\Ud \\
 \hline
 \c\ea   &\l\ea  &\c\eg  &\l\eg  &\c\er  &\l\er  &\c\es  &\l\es  \\
 \c\esa  &\l\esa &\c\esg &\l\esg &\c\era &\l\era &\c\erg &\l\erg \\
 \hline
-\c\oa   &\l\oa  &\c\og  &\l\og  &\c\oR\ap{1}&\l\oR  &\c\os  &\l\os  \\
+\c\oa   &\l\oa  &\c\og\ap{1}  &\l\og  &\c\oR\ap{2}&\l\oR  &\c\os  &\l\os  \\
 \c\osa  &\l\osa &\c\osg &\l\osg &\c\ora &\l\ora &\c\org &\l\org \\
 \hline
-\c\rs   &\l\rs  &\c\rr  &\l\rr  &\V     &&&     &\c\Id  &\l\Id  &\c\Ud   &\l\Ud \\
+\c\rs   &\l\rs  &\c\rr  &\l\rr  &\D       \\
 \hline
 \end{tabular}%
 }
 \caption{Glyph name macros}\label{t:compoundvowels}
 \bigskip
 REMARKS\\[3pt]\footnotesize
-\ap{1}\quad As mentioned in the body of this text the  command
-\texttt{\char92or} is incompatibile with the
+\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; I have not experienced any inconvenience,at least with this version of of the \texttt{teubner} package.\par
+\leavevmode\ap{2}\quad As mentioned in the body of this text the  command
+\texttt{\char92or} is incompatible with the
 primitive \TeX\ command with the same name.
 \bhrule
 \end{table}
@@ -461,7 +470,7 @@ Notice that an initial single vowel may receive only a spirit marker with or wit
 
 Assume these words have to go in an all-caps header that is made up (behind the scenes) by making use of the \verb|\MakeUppercase| command; they have to be spelled \textLipsias{A\"ULOS} and \textLipsias{A\"UPNIA}, even if in the sectioning command argument they were spelled in lowercase with all the necessary diacritics. 
 
-This is where the ligature and/or the extended accent macros may show their different behaviour. With the \texttt{teubner} generated secondary \texttt{LGRaccents-glyphs.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.
 
 
@@ -538,7 +547,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 maximium 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{2010}| you get \textLipsias{\AtticNumeral{2010}}
+if you type \verb|\AtticNumeral{2011}| you get \textLipsias{\AtticNumeral{2011}}
 if you type \verb|\AtticNumeral{1999}| you get \textLipsias{\AtticNumeral{1999}}
 \end{quote}
 
diff --git a/Master/texmf-dist/doc/latex/teubner/teubner.pdf b/Master/texmf-dist/doc/latex/teubner/teubner.pdf
index 87418f4df0d..f0db6c32be6 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 8d7b27912d9..305e789995a 100644
--- a/Master/texmf-dist/doc/latex/teubner/teubner.txt
+++ b/Master/texmf-dist/doc/latex/teubner/teubner.txt
@@ -17,8 +17,8 @@ teubner.dtx          documented TeX file
 teubner-doc.tex      documentation file
 
 By running pdflatex on teubner.dtx in addition to the documentation file 
-teubner.doc, the byproduct files teubner.sty, teubnertx.sty, LGRaccents-
-gyphs.def are generated;  teubner-doc.pdf  must be generated  by running 
+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.
 
 File teubner-doc.pdf  is the documentation file  that  shows what can be 
@@ -45,7 +45,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 teubenr.dtx file generates also file teubnertx.sty 
+the processing of the teubner.dtx file generates also file teubnertx.sty 
 that is being  input at begin document time if the user specified the TX 
 fonts by calling the txfonts package. 
 
@@ -78,14 +78,21 @@ 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.  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.
+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 CB Greek ones,  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 CBgreek fonts;  even  
 if you got them pre-installed with  your TeX system distribution, may be  
@@ -138,7 +145,7 @@ you use LaTeX, you know what are its pros and cons.
 
 Happy philological LaTeXing!
 
-Claudio Beccari                                Turin, 2 of November 2010
+Claudio Beccari                               Turin, 3 of September 2011
 Former Professor of Electronics
 Politecnico di Torino, Italy
 claudio dot beccari at gmail dot com
diff --git a/Master/texmf-dist/source/latex/teubner/teubner.dtx b/Master/texmf-dist/source/latex/teubner/teubner.dtx
index 20aac63e5c4..f5e5130829b 100644
--- a/Master/texmf-dist/source/latex/teubner/teubner.dtx
+++ b/Master/texmf-dist/source/latex/teubner/teubner.dtx
@@ -582,7 +582,7 @@ Type X <return> to exit.}%
 %\begin{macro}{\substitutefontfamily}
 %\begin{macro}{\ifLipsian}
 % The font macro |\substitutefontfamily| is already present in the \babel\ kernel;
-% I copes only with the standard families, series and shapes, therefore it does not
+% it copes only with the standard families, series and shapes, therefore it does not
 % consider the Lipsian shape and its series. I had to redefine it together with a
 % new conditional macro in order to do the same job as the original one but taking
 % into consideration also the Lipsian shape; the purpose of this macro is to write