From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: Math bug (maybe) - prime
Date: Wed, 28 Dec 2022 00:27:39 +0100 [thread overview]
Message-ID: <5d65daaa-0aab-8415-b4c2-d130e5cecea3@freedom.nl> (raw)
In-Reply-To: <20221227103333.162073b9@boo.my.domain>
On 12/27/2022 6:33 PM, Alan Braslau via ntg-context wrote:
> MWE:
>
> \starttext
>
> $a^2′$
>
> $a′^2$
>
> $\mathord{a′}^2$
>
> $a^*^2$
>
> \stoptext
>
>
> Should the \mathord{} be necessary to get the desired result?
> (I would expect the second line to work, just like $a^*^2$.)
primes are kind of special and a pain in tex
- traditional tex sees them as superscripts and therefore expects soem
active character and parsing magick for successive scripts
- that assumes a special way of havign these primes in the font (read:
is it a text size thing already raised or a script one not yet raised)
- it also sort of spoils spacing (as one can end up with an empty
nucleus inserted)
- in mkiv we use different magick than in mkii
anyway, in lmtx (luametatex) primes have been promoted to first class
citizens which means that a nucleus can have
- super(post)script
- sub(post)script
- superprescript
- subprescript
- prime
and each comes with spacing and positioning properties cf opentype and
our own additions for the pre/prime)
there is some magick wrt subscripts as these often are indices (which is
why we have for instance ^^^ and ___ too)
What you can do is:
$\primed{a}^2$
which basically makes the prime an operation .. a small price to pay for
more robust handling of primes (also across fonts)
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:[~2022-12-27 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 17:33 Alan Braslau via ntg-context
2022-12-27 23:27 ` Hans Hagen via ntg-context [this message]
2022-12-28 4:58 ` Alan Braslau via ntg-context
2022-12-28 7:26 ` Mikael Sundqvist via ntg-context
2022-12-28 17:32 ` Alan Braslau 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=5d65daaa-0aab-8415-b4c2-d130e5cecea3@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).