Hi Hans,
Thank you for the new upload and the rewriting of the math fonts stuff, thanks
also to Mikael S. I did several tests on real size math projects and did not
notice important issues.
The two issues I noticed, show up mainly with LucidaOT, and are explained in
the following example:
\setupbodyfont[lucidaot]
\definemathstackers[MySymbol]
[voffset=-1.4\mathexheight, % -.8\mathexheight
hoffset=\zeropoint,
mathclass=ord,
topoffset=.3\mathemwidth, % poor man's italic correction
middlecommand=\mathematics]
\define[1]\interior{\mathover[MySymbol]{176}{#1}} %2218 U+00B0
\definemathcommand [Argmin] [limop] {\mfunctionlabeltext{ArgMin}}
\definemathcommand [liminfbar] [limop] {\underline{\mfunctionlabeltext{lim}}}
\definemathcommand [limsupbar] [limop] {\overline{\mfunctionlabeltext{lim}}}
\starttext
If $A \subset {\Bbb R}$ is a set, its interior is denoted by $\interior{A}$.
Can one have the circle over $A$ slightly bigger (probbaly this is font
dependent)?
The built-in commands $\liminf$ and $\limsup$ do not work properly with
LucidaOT (I tried other fonts and there they are fine):
\startformula
x_{n} := (-1)^n, \quad\mbox{then} \quad \liminf_{n \geq 0}x_{n} = -1, \quad
\limsup_{n\geq 0} x_{n}= +1.
\stopformula
The commands defined above, \type{\liminfbar} and \type{\limsupbar}, behave
correctly in all fonts I tested:
\startformula
x_{n} := (-1)^n, \quad\mbox{then} \quad \liminfbar_{n \geq 0}x_{n} = -1, \quad
\limsupbar_{n\geq 0}x_{n} = +1,
\stopformula
but not the command \type{\Argmin} (which does not show Argmin in any font…)
\startformula
\Argmin_{x\in {\Bbb R}} (x^2 - x + 1) = {1 \over 2}.
\stopformula
\stoptext
Best regards: Otared
> On 13 Nov 2021, at 21:19, Hans Hagen via ntg-context <[email protected]>
> wrote:
>
> Hi,
>
> I uploaded a new lmtx versions. It mostly concerns new math lfg file
> functionality (and control) that Mikael Sundqvist and I are currently working
> on so there might be subtle differences in math, which is, unless there are
> bugs, intentional and for the best. At some point there will be additional
> test files in the distribution and a chapter on fonts in the math manual (the
> deadline is next years ctx meeting).
>
> If you have wishes wrt fonts you can tell us and we'll take them into account
> (if possible) but we need proper (real) minimal examples, and not for only
> one font as we're looking at:
>
> cambria (the reference font, very little tweaking needed)
> modern (which has some properties different from other gyre fonts)
> modernlatin (the boldened aka bachotex version)
> dejavu (a gyre font but different from other gyre fonts)
> pagella (a gyre font, all have subtle differences)
> schola (a gyre font, all have subtle differences)
> termes (a gyre font, all have subtle differences)
> bonum (a gyre font, all have subtle differences)
> lucida (commercial but rather cheap from tug)
> xits (is that one still used?)
> libertinus (a mixed bag)
> stix-two (a mixed bag)
> asana (we might drop it because of quality reasons)
> ebgaramond (this one is quite cambria conforming)
> minion (tricky because commercial and not generally available)
>
> Maybe later the newlatin modern will get a lfg too but it's beta and we
> 'modernlatin' anyway which uses our normal lm lgf file as it's A runtime
> derived font and therefore fully compatible.
>
> The bold (heavy) math fonts also are dealt with automagically.
>
> For practical reasons we might freeze fonts in the distribution and only
> update when explicitly checked for changes (and/or I might cook up version
> support in the lfg file assuming version checking is doable as often version
> strings are somewhat messy). We're not that bound to conventions (in the
> perspective of tex usage) and can "fix" them once and for all (read: we can
> divert from how these fonts are currently tuned for usage and expectations in
> e.g. latex and plain tex) so feel free to suggest esthetical pleasing
> options. If needed we can add variants (for which we can extend the lfg
> format). We also have plenty of yet unused (detailed) control in the engine.
> We can for instance have specific parameter sets / finetuning defined in the
> lfg files too but I don't know how useful and in demand that is (Mikael is
> looking into that).
>
> (I'm sure Aditya has some wishes. We'll deal with Euler later as that's a
> virtual mix and virtual opentype might be redone later because we can simply
> matters a bit due to the fact that we have some more and better trickery wrt
> virtual fonts now.)
>
> More in due time (as it's a tedious and somewhat boring job that demands lots
> of testing and investigation),
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : [email protected] / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : [email protected] / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
