From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: Why overbar is so big
Date: Sun, 13 Aug 2023 10:10:36 +0200 [thread overview]
Message-ID: <eb9b32ec-3668-594d-14df-e29b5810892f@freedom.nl> (raw)
In-Reply-To: <20230813090800.4beca3138668b332a3b547b1@posteo.net>
On 8/13/2023 9:08 AM, Xavier B. wrote:
> So,
>
> Finally is it a bug in MKIV? It seems you fix some kind of bug in your messages. Is it true?
Not really. It's a a bug in the fonts (that will stay if only for
compaibility reasons). There is a catch in mkiv that compensates for it
but only when characters are not there. So, for these two I now force
the catch.
In lmtx we have a bit different approach: we just assuem they are wrong
in all fonts and fix them or replace them. We also have a more advanced
math engine so we can control placement better.
There are also 'font parameters' involved that can be bad (i guess that
designers can't really test math font parameters). In lmtx we have more
of them, beyond what opentype math provides.
All of this is handled in goodie files. That mechanism is present in
mkiv but no one ever bothered to spent time on it. That said: the last
two years Mikeal and I spent a *lot* of time on math and we don't really
look back at mkiv / mkii also because there is way more neat things now
(most probably go unnoticed) ... you can read about it in some documents
that come with context, articles in tugboat, and there are talks by
Mikael at tug meetings on YT.
>> The output with Luametatex is correct but Luatex creates a raised bar
>> (and different linebreaking).
>>
>> \showglyphs
>>
>> \startTEXpage[offset=1ex]
>> \ruledhbox{$\overline {OA} = \overbar {OA} = 4.2$}
>> \par
>> \ruledhbox{$\underline {OA} = \underbar {OA} = 4.2$}
>> \par
>> \ruledhbox{$\widetilde {OA} = \widebar {OA} = 4.2$}
>> \par
>> \ruledhbox{$\overbracket {OA} = \underbracket {OA} = 4.2$}
>> \stopTEXpage
>>
>> I'll add a 'force fix in spite of extensible being present' in mkiv. In
>> lmtx we always fix also because we drop in nicer shapes (watch the round
>> tips in lm and fancy tips in antykwa) and concluded that fonts will
>> remain as they are.
>>
>> Hans
>
> As you suggested, I will give a try to LMTX but be aware most user still use MKIV until most distros upgrade the texlive version of context to LMTX.
It's not that hard to install lmtx alongside. If distributions take from
texlive then likely you also end up with files that are not needed (base
package) and lack some fonts (esp math) by default. You'd also benefit
from the last couple of years advancements. Keep in mind that for a long
term tex (document) project a snapshot approach is healthy because you
never know what a distribution adds / replaces (esp fonts can be a mess
and you want to know what you use).
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 : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-08-13 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 19:38 [NTG-context] " Xavier B.
2023-08-11 19:46 ` [NTG-context] " Thangalin
2023-08-12 8:10 ` Xavier B.
2023-08-12 9:13 ` Hans Hagen via ntg-context
2023-08-12 9:46 ` Wolfgang Schuster
2023-08-12 12:38 ` Hans Hagen via ntg-context
2023-08-12 12:40 ` Hans Hagen via ntg-context
2023-08-13 7:08 ` Xavier B.
2023-08-13 8:10 ` Hans Hagen via ntg-context [this message]
2023-08-13 20:39 ` Xavier B.
2023-08-13 21:24 ` Hans Hagen
2023-08-14 7:13 ` Xavier B.
2023-08-14 8:15 ` Hans Hagen via ntg-context
2023-08-14 15:06 ` Xavier B.
2023-08-13 8:42 ` Mikael Sundqvist
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eb9b32ec-3668-594d-14df-e29b5810892f@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).