ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <braslau.list@comcast.net>
To: "Hans Åberg" <haberg-1@telia.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Monospace fallback kerning
Date: Wed, 19 Dec 2018 11:28:50 -0700	[thread overview]
Message-ID: <20181219112850.62a08a69@comcast.net> (raw)
In-Reply-To: <8685CCE8-FA7A-48BD-AFD0-BD2963B258E3@telia.com>

On Wed, 19 Dec 2018 19:16:23 +0100
Hans Åberg <haberg-1@telia.com> wrote:

> 
> > On 19 Dec 2018, at 19:01, Alan Braslau <braslau.list@comcast.net> wrote:
> > 
> > On Wed, 19 Dec 2018 18:46:30 +0100
> > Hans Åberg <haberg-1@telia.com> wrote:
> > 
> >> 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.
> > 
> > Isn't that poor nomenclature, being ambiguous?
> 
> Indeed, but also the norm due to practical limitations.
> 
> > I would explicitly write (𝑥₀)² or (𝑥²)₀ in such cases, and I have also seen 𝑥²|₀ used for example, or other non-ambiguous shorthands.
> 
> Perhaps it might become cumbersome to carry such notation along all through, reserving it for definitions. 

In physics, we love such constructions, such as the so-called Einstein notation as one example.

Alan
___________________________________________________________________________________
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 18:28 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 [this message]
2018-12-19 19:34                 ` Hans Åberg
2018-12-19 18:25           ` Hans Hagen
2018-12-19 19:43             ` Hans Åberg
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=20181219112850.62a08a69@comcast.net \
    --to=braslau.list@comcast.net \
    --cc=haberg-1@telia.com \
    --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).