ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Hans Åberg" <haberg-1@telia.com>
To: Alan BRASLAU <alan.braslau@cea.fr>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Latin setupmathematics
Date: Fri, 17 Jun 2016 10:15:37 +0200	[thread overview]
Message-ID: <CFA43F2E-FD87-4863-AE44-34891540EE9C@telia.com> (raw)
In-Reply-To: <20160616222034.101d207f@cea.fr>


> On 17 Jun 2016, at 06:20, Alan BRASLAU <alan.braslau@cea.fr> wrote:
> 
> On Fri, 17 Jun 2016 01:02:48 +0200
> Hans Åberg <haberg-1@telia.com> wrote:
> 
>> The idea is avoiding clashes between variables and constants, like
>> this:
>> 
>> \starttext
>> 
>> \setupmathematics[default=normal]
>> 
>> $𝑒 = ∑_{𝑖=1}^∞ e^{i-𝑖}$
>> 
>> \setupmathematics[default=italic]
>> 
>> $𝑒 = ∑_{𝑖=1}^∞ e^{i-𝑖}$
> 
> Very, very poor mathematical style...
> 
> If you really want to use a variable "e", this would call for the use
> of the function \exp() to be readable.

Unicode has added characters to enable such writing. Also, \exp is already defined to “exp”, for example for the exponential map in differential geometry:
\startformula
  \exp_x: M_x → M
\stopformula

Here, the “:” expands in original TeX as a ratio operator, but Unicode has a special symbol for that, ∶ RATIO U+2236.


___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2016-06-17  8:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-14 17:11 Hans Åberg
2016-05-15 13:37 ` Hans Hagen
2016-05-15 14:15   ` Hans Åberg
2016-05-15 14:28   ` Hans Åberg
2016-05-15 14:44     ` Wolfgang Schuster
2016-05-15 16:06       ` Hans Åberg
2016-05-15 16:36       ` Hans Åberg
2016-05-15 17:12         ` Hans Hagen
2016-05-15 17:28           ` Hans Åberg
2016-05-15 18:06             ` Hans Hagen
2016-05-15 18:34               ` Hans Åberg
2016-05-15 17:08     ` Hans Hagen
2016-05-15 17:42       ` Hans Åberg
2016-05-15 17:59         ` Hans Hagen
2016-05-15 18:31           ` Hans Åberg
2016-05-15 18:42             ` Hans Hagen
2016-05-15 20:06               ` Hans Åberg
2016-05-15 21:18                 ` Hans Hagen
2016-05-15 21:55                   ` Hans Åberg
     [not found]                     ` <f175caa5-45df-5df6-d5a9-5bf9340a6f0d@wxs.nl>
2016-05-16  8:27                       ` Hans Åberg
2016-05-16  8:48                         ` Hans Hagen
2016-05-16  8:59                           ` Hans Åberg
2016-05-16  9:10                             ` Hans Hagen
2016-05-16 12:07                               ` Hans Åberg
2016-06-16 19:15                 ` Hans Åberg
2016-06-16 21:48                   ` Hans Hagen
2016-06-16 23:02                     ` Hans Åberg
2016-06-17  4:20                       ` Alan BRASLAU
2016-06-17  8:15                         ` Hans Åberg [this message]

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=CFA43F2E-FD87-4863-AE44-34891540EE9C@telia.com \
    --to=haberg-1@telia.com \
    --cc=alan.braslau@cea.fr \
    --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).