mathastext (4nov22)

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

1 files changed, 52 insertions, 114 deletions

diff --git a/Master/texmf-dist/doc/latex/mathastext/README.md b/Master/texmf-dist/doc/latex/mathastext/README.md
index fd15e838426..b008e822765 100644
--- a/Master/texmf-dist/doc/latex/mathastext/README.md
+++ b/Master/texmf-dist/doc/latex/mathastext/README.md
@@ -12,9 +12,9 @@ of the [LPPL1.3c](http://www.latex-project.org/lppl/lppl-1-3c.txt)
 
 The Author of this Work is Jean-Francois Burnol
 
-Copyright (C) 2011-2019 Jean-Francois Burnol (`jfbu at free dot fr`)
+Copyright (C) 2011-2019, 2022 Jean-Francois Burnol (`jfbu at free dot fr`)
 
-      Source: mathastext.dtx 1.3w 2019/11/16
+      Source: mathastext.dtx 1.3y 2022/11/04
 
 
 DESCRIPTION
@@ -82,119 +82,57 @@ Main options: `italic`, `subdued`, `LGRgreek`.
 RECENT CHANGES
 ==============
 
-1.3w \[2019/11/16\]
+1.3y \[2022/11/04\]
 ----
 
-* LaTeX 2019-10-01 release (up to patch level 3 inclusive)
-  together with `amsmath` conspired `:-)` to break `mathastext`,
-  in connexion with math accents. This has been fixed upstream,
-  but I am releasing nevertheless a hot fix to this
-  [issue](https://github.com/latex3/latex2e/issues/216)
-  (this is compatible with future LaTeX releases).
-
-* Fix: the `\hbar` is originally a robust command but
-  becomes a `\mathchardef` token if (e.g.) `amsfonts` is
-  loaded and then with recent LaTeX `\hbar<space>` is
-  made undefined and `mathastext` definition of it
-  remained without effect. The `\mathastext` own `\hbar`
-  is now defined `\protected`.
-
-* Fix: option `noendash` (or `symboldelimiters` which implies
-  it) caused (since `1.3u`) a bug under Unicode engines when
-  setting up the minus sign.
-
-* Version names declared via the optional argument of
-  `\Mathastext` or as first argument of `\MTDeclareVersion`
-  must not be `normal` or `bold`. Enforce that! (this was
-  marked as a bug to fix since `2012/10/24`...)
-
-1.3v \[2019/09/19\]
-----
+(the 1.3x had an annoying documentation bug, and had already
+been pushed to CTAN, hence the version increase to 1.3y)
+
+* mathastext now requires the `\expanded` primitive (which is
+  available with all major engines since TeXLive 2019).
+
+* Revisit parts of the documentation (mainly
+  the Examples, and the section on Greek letters) and shuffle
+  the other parts to surely improve things. Mention
+  the [mathfont](https://ctan.org/pkg/mathfont)
+  and [frenchmath](https://ctan.org/pkg/frenchmath) packages.
+
+* Add the `ncccomma` option which loads the
+  [ncccomma](https://ctan.org/pkg/ncccomma)
+  package to allow the comma as decimal separator.
+
+* Add the `binarysemicolon` option to let the semi-colon
+  be of type `\mathbin`, not `\mathpunct`.
+
+* Add the `frenchmath*` option which does all three of
+  `frenchmath`, `ncccomma` and `binarysemicolon`.
+
+* Under the `LGRgreek` and `LGRgreeks` options only:
+
+  - make available upright and italic Greek letters in math mode
+    via `\alphaup`, `\alphait`, ...  control sequences, in
+    addition to those not using such postfixed-names.
+
+  - add `\mathgreekup` and `\mathgreekit` math alphabets.
+
+  - add `\MTgreekupdefault` and `\MTgreekitdefault`.  The former
+    replaces `\updefault` which was used in some places and since
+    LaTeX 2020-02-02 caused systematic Font Warnings about the
+    substitution of `up` by `n`.
+
+  These new features required an extensive internal refactoring
+  which is expected to not induce changes to most existing
+  documents.  But it may induce changes to those using some
+  unusual configuration in the preamble, as made possible via the
+  package macros; this can apply only to documents authored by
+  those few people who actually read the documentation.  For full
+  details make sure to read the PDF documentation about this
+  change.
+
+* Fix "`\Digamma` under `LGRgreek` option uses the shape for
+  lowercase not uppercase Greek".
 
-* LaTeX 2019-10-01 release has made more math macros robust.
-  This applies in particular to the math accents and to the
-  `\hbar`. This required for mathastext to adapt. Also
-  `\leftarrowfill` and `\rightarrowfill` are now defined
-  robust by the kernel, hence mathastext does the same. These
-  changes are dropped if mathastext detects an older LaTeX
-  format.
-
-* These LaTeX kernel changes motivated an examination of some
-  redefinitions done (optionally) by mathastext:
-  - The user math alphabet macros got redefined as expanding
-    to some other (robust) math alphabet macros, but were not
-    robust in the strict sense. This does cause some issues
-    for moving arguments in the context of multiple math
-    versions, hence it was a bug. The special behaviour of the
-    math alphabet commands (they redefine themselves and other
-    macros on first use) makes is somewhat problematic for
-    mathastext to keep them updated across math versions and
-    at the same time strictly LaTeX2e robust. Thus mathastext
-    now requires the e-TeX primitive `\protected` and uses it
-    for the definitions of the user level math alphabet
-    macros.
-  - There are a number of `\mathchardef` tokens which (under
-    certain options and/or configuration via the package user
-    interface), mathastext redefines as macros. These macros
-    cause no issue in moving arguments (they are not
-    "fragile"), still it is probably better if they expand
-    only at the time of typesetting. To this effect they are
-    now also `\protected`: `\exists`, `\forall`, `\colon`,
-    `\setminus`, `\mid`, `\prod`, `\sum`, `\imath`, `\jmath`.
-  - The macro `\vert` (which expands to a `\delimiter`) is now
-    defined robust by LaTeX. Its mathastext redefinition is a
-    `\protected` one rather.
-  - The `\{` and `\}` (which get redefined only under
-    `\MTexplicitbracesobeymathxx` regime) are now strictly
-    robust in the LaTeX2e sense (formerly they were `\let` to
-    some robust macros, and this did not make them strictly
-    LaTeX2e-robust entities).
-
-* The various changes in mathastext described in the previous item
-  apply independently of the LaTeX release version. The
-  LaTeX format itself requires the e-TeX extensions since 2015.
-
-1.3u (2019/08/20)
----
-
-* new feature: the initial release dealt with only one font, and
-  although shortly thereafter the 1.11 version added support for
-  extended math versions, it was documented that some font-dependent
-  set-up (minus as endash, dotless i and j, hbar, math accents) was
-  done only once. This release makes the relevant characters font
-  encoding savvy in each mathastext-extended math version. Thus,
-  they should render correctly even with multiple math versions
-  using fonts with varying encodings.
-
-  This reinforces importance of using `\MTversion` and not the
-  LaTeX `\mathversion` when switching to a new math version (which
-  got declared via the package interface). The implementation is
-  compatible with Unicode engines and mixed usage of `TU` encoding
-  (OpenType fonts) with traditional 8bits TeX font encodings. For
-  all engines, all used (8bits) encodings must have been passed as
-  options to the `fontenc` package.
-
-  Thanks to Falk Hanisch for feature request and code suggestions.
-
-* new option `unimathaccents`: this adds to option `mathaccents`
-  the demand to use the text font accents for OpenType fonts in math
-  mode via the `\Umathaccent` primitive. Indeed, as my testing
-  showed that this gave non-satisfactory results both with XeTeX
-  and LuaTeX regarding the horizontal placement of the accents,
-  the main option `mathaccents` acts only on 8bits encoded fonts.
-
-* bugfix: the `\Mathastext` without optional argument forgot to
-  repeat some font-encoding dependent initialization set-up done
-  originally during package loading.
-
-* bugfix: under the `subdued` option macros `\MTmathactiveletters`
-  or `\MTnonlettersobeymathxx` now act like no-ops if
-  issued explicitly while in the `normal` or `bold` math version.
-  Formerly, this was not the case and could cause bugs such as a
-  disappearing minus sign in math mode.
-
-* bugfix: the letter `h` used in the `\hbar` obeyed the extra
-  skips as set-up by `\MTsetmathskips`, badly interfering with the
-  horizontal positioning of the bar accent. They are now ignored
-  (as well as the added italic correction).
+* Fix some incongruities in log messages related to Greek
+  letters and emitted during math version creation in the
+  preamble.