From: "Anthony J. Bentley" <anthony@anjbe.name>
To: tech@mandoc.bsd.lv
Subject: eqn(7): Primes, opprime, and '
Date: Thu, 13 Jul 2017 23:14:20 -0600 [thread overview]
Message-ID: <18793.1500009260@cathet.us> (raw)
Hi,
https://www.w3.org/TR/MathML3/chapter7.html#chars.pseudo-scripts says:
"...the preferred encoding of 'x prime' is
<msup><mi>x</mi><mo>′<!--PRIME--><!--PRIME--></mo></msup>
and not
<mi>x'</mi>
or any other variants not using an explicit script construct."
Superscripting primes this way is common in typesetting. In TeX,
' is equivalent to ^{\prime}:
https://tex.stackexchange.com/questions/87134/
The OpenGL manuals typically use "sup prime", as in gluProject(3):
v sup prime ~=~ P ~times~ M ~times~ v
GNU eqn(1) has the opprime keyword:
e opprime
This is a variant of prime that acts as an operator on e. It
produces a different result from prime in a case such as
A opprime sub 1: with opprime the 1 is tucked under the prime as
a subscript to the A (as is conventional in mathematical
typesetting), whereas with prime the 1 is a subscript to the
prime character. The precedence of opprime is the same as that
of bar and under, which is higher than that of everything except
accent and uaccent. In unquoted text a ' that is not the first
character is treated like opprime.
So it appears that in groff(1) ' and opprime are equivalent to
(essentially) sup prime.
It's, um, hard to grep manuals for this usage, but I can believe that
people would use ' this way, both because it's documented in groff and
because they would expect it to work as TeX. So mandoc(1) having
opprime, and ' equivalent to opprime, would be nice.
--
Anthony J. Bentley
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
reply other threads:[~2017-07-14 5:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=18793.1500009260@cathet.us \
--to=anthony@anjbe.name \
--cc=tech@mandoc.bsd.lv \
/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).