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: math: too big space between function and argument
Date: Wed, 25 May 2011 11:54:32 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.02.1105251149240.4150@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <1306331537.10056.72.camel@mattotaupa>

On Wed, 25 May 2011, Paul Menzel wrote:

> On Di, 2011-05-24 at 09:56 -0400, Aditya Mahajan wrote:
>> On Tue, 24 May 2011, Paul Menzel wrote:
>
>>> to markup the probability measure and the parenthesis around the
>>> argument, I defined the following command.
>>>
>>> 	\define[1]\P{{\mathbf P}\left( #1 \right)}
>>>
>>> Unfortunately the space between the P and the left ( is a little big in
>>> my opinion. Is that correct or should/can I fix that somehow?
>>
>> Getting these spaces is tricky; especially if you consider spaces before
>> and after the definition. Choose your pick:
>>
>> \starttext
>>   \startformula
>>    A{\mathbf P}\left( ABC \right)B \quad
>>    A\mathop{\kern\zeropoint\mathbf P}\left( ABC \right)B \quad
>>    A{\mathbf P}\mathopen{}\left( ABC \right)\mathclose{}B \quad
>>    A\mathop{\kern\zeropoint\mathbf P}\mathopen{}\left( ABC \right)\mathclose{}B \quad
>>   \stopformula
>> \stoptext
>
> That looks tricky and complex.

But can be easily hidden behind a macro.

> Could you explain the advantage over `\!` which Wolfgang suggested at
> least for the space after the definition.

\! only corrects the space between the P and (, not the spacing before P, 
and the space after ). Moreover, some of the math spacing rules change in 
\scriptstyle and \scriptscriptstyle; using \mathop, \mathopen, and 
\mathclose means that those rules are followed.

> In addition, I think AMSTeX defines a command `\DeclareMathOperator` [1]
> which takes care of these things

No. \DeclareMathOperator is just a fancy wrapper around 
\mathop{\operatorfont ...}. A similar result can be achieved in ConTeXt 
using

\declaremathcommand [...] [op] [\mfunction ...]

For defining user macros, I prefer \mathop{\mfunction{...}}.

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
___________________________________________________________________________________


      reply	other threads:[~2011-05-25 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 11:14 Paul Menzel
2011-05-24 13:25 ` Wolfgang Schuster
2011-05-25 13:46   ` Why is `\P` used for not often used ¶? (was: math: too big space between function and argument) Paul Menzel
2011-05-25 14:27     ` Wolfgang Schuster
2011-05-24 13:56 ` math: too big space between function and argument Aditya Mahajan
2011-05-25 13:52   ` Paul Menzel
2011-05-25 15:54     ` Aditya Mahajan [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=alpine.LNX.2.02.1105251149240.4150@ybpnyubfg.ybpnyqbznva \
    --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).