ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Xavier B." <somenxavier@posteo.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Why overbar is so big
Date: Sun, 13 Aug 2023 07:08:00 +0000	[thread overview]
Message-ID: <20230813090800.4beca3138668b332a3b547b1@posteo.net> (raw)
In-Reply-To: <4c2f67e2-94cc-d571-3697-9dea5d159975@freedom.nl>

So,

Finally is it a bug in MKIV? It seems you fix some kind of bug in your messages. Is it true?

>     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.

Regards,
Xavier
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2023-08-13  7:11 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. [this message]
2023-08-13  8:10       ` Hans Hagen via ntg-context
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=20230813090800.4beca3138668b332a3b547b1@posteo.net \
    --to=somenxavier@posteo.net \
    --cc=ntg-context@ntg.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).