From: Jim via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Jim <zlists+context@jdvb.ca>
Subject: Re: Spacing problem around decimal point
Date: Sun, 26 Mar 2023 18:16:01 -0300 [thread overview]
Message-ID: <ZCC2ERtrqdbyVU2G@x360.localdomain> (raw)
In-Reply-To: <87ilenh68p.fsf@ko-sek.at>
Hi all,
Regrettably, I see the same problem and Gavin.
I am using TeXlive 2023 on Slackware64 15.0, for what that is worth.
Jim
On Sun, Mar 26, 2023 at 17:36 (+0200), Günter Kolousek via ntg-context wrote:
> Hi,
> I can confirm that the x64_64-linux from
> https://dl.contextgarden.net/build/luametatex/work/
> version works correctly. So, no excess spaces around the
> decimal points at all.
> HTH
> Günter
> Hans Hagen via ntg-context @ 2023-03-26 13:22 +02:
>> On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:
>>> Hi List,
>>> I’m getting strange spaces around some decimal points after a clean
>>> LMTX
>>> install. MWE:
>>> \starttext
>>> \startformula
>>> v = \frac{1.32}{1.41} = 0.935
>>> \stopformula
>>> \stoptext
>>> This produces the result attached below. The 1.32 looks fine, but
>>> the next two
>>> numbers have excess space around the decimal point. Adding the line
>>> \showmakeup[mathglue] %\mathspacingmode=1
>>> to the preamble reveals that the second and third decimal points are
>>> being
>>> treated as binary operators. It’s very strang. Are others getting
>>> this?
>> can you pick up a binary from:
>> https://dl.contextgarden.net/build/luametatex/work/
>> and test it?
>> Hans
___________________________________________________________________________________
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-03-26 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 2:20 Gavin via ntg-context
2023-03-26 10:16 ` Hans Hagen via ntg-context
2023-03-26 11:22 ` Hans Hagen via ntg-context
2023-03-26 15:36 ` Günter Kolousek via ntg-context
2023-03-26 21:16 ` Jim via ntg-context [this message]
2023-03-26 22:15 ` Bruce Horrocks via ntg-context
2023-03-28 20:56 ` Gavin via ntg-context
2023-03-28 22:29 ` Bruce Horrocks via ntg-context
2023-03-29 0:06 ` Jim via ntg-context
2023-03-29 10:50 ` Hans Hagen via ntg-context
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=ZCC2ERtrqdbyVU2G@x360.localdomain \
--to=ntg-context@ntg.nl \
--cc=zlists+context@jdvb.ca \
/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).