ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Hans Åberg" <haberg-1@telia.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Monospace fallback kerning
Date: Wed, 19 Dec 2018 20:43:38 +0100	[thread overview]
Message-ID: <D25D4182-7BE3-4896-BA76-74B4113B5ADD@telia.com> (raw)
In-Reply-To: <8c6d5da7-df30-a05d-4d15-c342b7f8b582@xs4all.nl>


> On 19 Dec 2018, at 19:25, Hans Hagen <j.hagen@xs4all.nl> wrote:
> 
>>> \startformula
>>>  \unstackscripts 𝑷₂₀(0), ∀²𝑥⁰⁺²₂₀: 𝑷₂₀(𝑥⁰⁺²₂₀) ⇒ 𝑷₂₀(s(𝑥⁰⁺²₂₀)) ⊢ ∀¹𝑦⁰⁺¹₂₀ 𝑷₂₀(𝑦⁰⁺¹₂₀)
>>> \stopformula
>> That might be useful for those depending on it, and presumably there is a \stackscripts, too. Just comes to my mind:
>> Though probably non-standard in typesetting, one might make a slight typographic difference between 𝑥²₀ and 𝑥₀² by letting the sub- or superscripts that come later partially, but not fully, to the position of the one that comes before. For example, 𝑥₀² might mean the square of 𝑥₀, and 𝑥²₀ the component 0 of 𝑥², not necessarily the same. Traditionally, such things are left for the reader to interpret.
> 
> ok, we can apply selectively ... {\unstackscripts ... {\stackscripts ...} ... } ... maybe we need short commands that take an argument, like
> \unstack{............} but that might clash ... just give it some thought ...

Your suggestion might be great for simplifying tensor component notation, as one then can omit separators like {} or |. But then what would happen, even perhaps not that common, if one would need to have it stacked somewhere else in the formula. So in my mind, this would be just top level \unstackscripts … \stackscripts … \unstackscripts.

The other idea would be something like \partialstackscripts, but actual demand is unclear. :-)


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-12-19 19:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 14:05 Hans Åberg
2018-12-11 20:18 ` Pablo Rodriguez
2018-12-11 20:35   ` Hans Åberg
2018-12-19  9:46 ` Hans Åberg
2018-12-19 10:31   ` Hans Hagen
2018-12-19 14:48     ` Hans Åberg
2018-12-19 17:25       ` Hans Hagen
2018-12-19 17:46         ` Hans Åberg
2018-12-19 18:01           ` Alan Braslau
2018-12-19 18:16             ` Hans Åberg
2018-12-19 18:28               ` Alan Braslau
2018-12-19 19:34                 ` Hans Åberg
2018-12-19 18:25           ` Hans Hagen
2018-12-19 19:43             ` Hans Åberg [this message]
2018-12-19 21:24               ` Hans Hagen
2018-12-19 22:04                 ` Hans Åberg

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=D25D4182-7BE3-4896-BA76-74B4113B5ADD@telia.com \
    --to=haberg-1@telia.com \
    --cc=j.hagen@xs4all.nl \
    --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).