From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mathias Schickel <msch@fa.uni-tuebingen.de>
Subject: Manually scaling math fences
Date: Mon, 6 Mar 2017 11:57:31 -0800 (PST) [thread overview]
Message-ID: <alpine.OSX.2.02.1703061127090.31305@nqv-znpobbx> (raw)
Hi Hans,
There are instances where the automatic scaling provided by \left and
\right is not ideal and one has to use manual scaling. For example:
\starttext
\startTEXpage \startformula
\left\langle \sum_{i=1}^n A_i x_i \right\rangle
\hbox{ vs. }
\bigg\langle \sum_{i=1}^n A_i x_i \bigg\rangle
\stopformula \stopTEXpage
\stoptext
Currently, math fences always default to using \left and \right, which can
lead to undesirable results. For example:
\definemathfence [MEAN] [angle] [command=yes, color=blue]
\starttext
\startTEXpage \startformula
\MEAN{ \sum_{i = 1}^n A_i x_i }
\hbox{ vs. }
\bigg\langle \sum_{i=1}^n A_i x_i \bigg\rangle
\stopformula \stopTEXpage
\stoptext
Could we add an option to \definefence that allows the user to select the
delimiter scaling using a key (say, `delimiter`) so that
\MEAN[delimiter=auto] expands to \left\langle .. \right\langle
\MEAN[delimiter=] expands to \langle .. \rangle
\MEAN[delimiter=big] expands to \big\langle ... \big\rangle
\MEAN[delimiter=Big] expands to \Big\langle ... \Big\rangle
\MEAN[delimiter=bigg] expands to \bigg\langle ... \bigg\rangle
\MEAN[delimiter=Bigg] expands to \Bigg\langle ... \Bigg\rangle
I am not sure whether `delimiter` is the best key. I think that `scale`
may be better, but using `scale` for specifying the scaling of math
delimiters will be inconsistent with how `scale` is used everywhere else.
Another option is to use `alternative` key.
Thanks,
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2017-03-06 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 19:57 Aditya Mahajan [this message]
2017-03-07 6:35 ` Otared Kavian
2017-03-07 9:49 ` Hans Hagen
2017-03-08 1:45 ` Aditya Mahajan
2017-03-23 16:10 ` Hans Hagen
2017-03-24 7:24 ` Aditya Mahajan
2017-03-24 9:09 ` Hans Hagen
2017-03-24 9:56 ` Otared Kavian
2017-03-24 9:59 ` 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.1703061127090.31305@nqv-znpobbx \
--to=adityam@umich.edu \
--cc=msch@fa.uni-tuebingen.de \
--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).