ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Changing font for math function
Date: Tue, 12 May 2015 14:05:37 -0400 (EDT)	[thread overview]
Message-ID: <alpine.OSX.2.02.1505121354430.31440@nqv-znpobbx> (raw)
In-Reply-To: <CAJ2CwZ1mjJhOMwS03ndt20xPimVAtsMRrZQtPYpZx2qGR29xMA@mail.gmail.com>

On Tue, 12 May 2015, Maggyero wrote:

>> Hans Hagen wrote:
>> for functions one can now use:
>> \setupmathematics
>>   [functionstyle=\rm]
>
> Fantastic! Thank you Hans, it is way better than the old mechanism
> \setmathfunctionstyle. Now I have a few suggestions to improve the
> consistency of this new mechanism. First, I think this functionstyle key
> a) should be better called 'mathlabelstyle';

No. The style applies to anything called using \mfunction{...}, so 
functionstyle and functioncoloar are appropriate keys.

> b) be default to \tf to make the FONT ALTERNATIVE always upright;

I disagree. The default should be \mathupright (as is the case in amstex 
and latex, and probably also plaintex). We now have the option to change 
it to \tf if desired.

> c) be linked to this following new definition in math-ini.mkiv:
>
> + \unexpanded\def\mathlabel#1{\text{\mathlabelstyle #1}}
>
> so that \mathlabel can be used for labeling math objects like functions but
> ALSO for labeling variables with subscripts (e.g., \rho_{\mathlabel{air}}).
> The hardcoded \text in the definition of \mathlabel is used here for these
> 5 reasons:

Hans already replied to that.

> That \mathlabel should replace \mfunction which should be removed, and
> \mfunctionlabeltext should be removed as well and one should directly use
> the already defined \mathlabeltext instead, for these 3 reasons:

I strongly disagree to this. These are two completely different issues 
(wanting a macro to tag multiletter variable names vs a macro to tag 
log-like operators).

> 1. Every command containing the word 'labeltext' should not have a style
> attached to it.
> 2. The word 'function' is misleading because \mfunction and
> \mfunctionlabeltext do not create a \mathop atom and it makes the user
> believe its usage is restricted for labeling functions while the command
> should also be used for labeling variable with subscripts (e.g.,
> \rho_{\mathlabel{air}} is far better than \rho_\mfunction{air}).
> 3. Using only \mathlabeltext with \setuplabeltext is also more consistent
> with the current \labeltext that works with \setuplabeltext.
>
> Thus the function definitions in math-def.mkiv should be changed:
>
> - \definemathcommand [arccos]  [nolop] {\mfunctionlabeltext{arccos}}
> + \definemathcommand [arccos]  [nolop] {\mathlabel{\mathlabeltext{arccos}}}
> etc.

I don't see the rationale for this.

> And I think you should add in this file the definition of the differential
> operator which is so widely used in mathematics, so that users have at
> their disposal once for all a proper implementation of this operator and
> don't have to make their own hack:
>
> + \definemathcommand[diff]{\mathop{\mathlabel{d}}\mathopen{}}

Note that there is no consensus on how the `d` in calculus should be 
typeset. There are also \differentiald and \differentialD that map to 
unicode slots.

> \definemathcommand[arsinh][nolop]{\mathlabel{arsinh}}
>
> \starttext
> $\arsinh z = \ln\bigl(z + \sqrt{z^2 + 1}\bigr)$\par
> $\rho_{\mathlabel{air}} = \frac{p}{R_{\mathlabel{specific}}T}$\par
> \stoptext

\mfunction already does that.

I'll reply to the rest of the message later.

Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2015-05-12 18:05 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 14:19 Maggyero
2015-05-12 16:03 ` Hans Hagen
2015-05-12 18:05 ` Aditya Mahajan [this message]
2015-05-12 18:29   ` Mikael P. Sundqvist
2015-05-12 20:23 ` Aditya Mahajan
  -- strict thread matches above, loose matches on Subject: below --
2015-05-16 14:23 Maggyero
2015-05-16 15:35 ` Hans Hagen
2015-05-15 23:34 Maggyero
2015-05-16  0:24 ` Aditya Mahajan
2015-05-16  8:23   ` Hans Hagen
2015-05-13 15:51 Maggyero
2015-05-13 16:13 ` Hans Hagen
2015-05-12 15:18 Maggyero
2015-05-09  0:03 Aditya Mahajan
2015-05-09 10:14 ` Hans Hagen
2015-05-09 11:02 ` Wolfgang Schuster
2015-05-09 11:46 ` Hans Hagen
2015-05-09 11:56   ` Wolfgang Schuster
2015-05-09 13:00     ` Hans Hagen
2015-05-09 16:28       ` Wolfgang Schuster
2015-05-09 13:50   ` Aditya Mahajan
2015-05-09 14:16     ` Aditya Mahajan
2015-05-09 23:30       ` Hans Hagen
2015-05-10 12:19         ` Aditya Mahajan
2015-05-10 17:22           ` Hans Hagen
2015-05-11 16:16             ` Aditya Mahajan
2015-05-11 16:44               ` Hans Hagen
2015-05-11 17:08                 ` Aditya Mahajan
2015-05-11 19:28                   ` Hans Hagen
2015-05-10 16:16         ` Otared Kavian
2015-05-11  2:47           ` Aditya Mahajan
2015-05-11  7:07             ` Otared Kavian
2015-05-11  8:05               ` Hans Hagen
2015-05-11  8:33                 ` Otared Kavian

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=alpine.OSX.2.02.1505121354430.31440@nqv-znpobbx \
    --to=adityam@umich.edu \
    --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).