From: "Mikael P. Sundqvist" <mickep@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Size of fences, factor key
Date: Wed, 25 Apr 2018 07:29:48 +0200 [thread overview]
Message-ID: <CAHy-LL813ObutyiJHorHFn5fM9cD_SiFr+oYMQRuBZbUyXiM6w@mail.gmail.com> (raw)
In-Reply-To: <CAHy-LL-Oo1MMq1_RspNON9aS5z4VuJ6Da=d5frTFMms7rKyG4Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1946 bytes --]
On Sat, Apr 21, 2018 at 7:30 PM, Mikael P. Sundqvist <mickep@gmail.com>
wrote:
> Dear Hans and others,
>
> I'm usually use the \big, \Big, \bigg etc to get the size of parentheses,
> brackets and braces to be the size I want. I realize that the fences
> machinery is probably a cleaner way of doing this.
>
> I tried it a bit, and it usually gives the result I like. But sometimes
> not, and it seems that the way to change the size of the
> parentheses/brackets/braces is to use the factor key.
>
> 1) Are the different options none, auto NUMBER explained somehere?
> 2) Could one have, for exceptional cases where the default is not
> satisfactory, a keyword like factor=big for example, to get the same size
> as if one would have used \big?
>
> I am a bit confused. See the example below, with output (from latest
> standalone) attached.
>
> /Mikael
>
> PS: I would suggest to have
> italic = { feature = 'ss01', value = 1, comment = "Mathematical
> Alternative Lowercase Italic" },
> set in lucida-opentype-math.lfg. In all books (on math) I have seen, I
> think this is what is used.
>
> %%% Example file:
>
> \setupbodyfont[lucidaot]
>
> \definemathfence[Set][left="007B,right="007D,command=yes]
>
> \startbuffer
> \startformula
> \Set{x\in\mathbb R~:~x^2=1}
> \stopformula
> \stopbuffer
>
>
> \startTEXpage[offset=3bp]
>
> \startformula
> \{x\in\mathbb R~:~ x^2=1\}%Too small
> \stopformula
>
> \startformula
> \bigl\{x\in\mathbb R~:~ x^2=1\bigr\}%I like this one
> \stopformula
>
> \startformula
> \Bigl\{x\in\mathbb R~:~ x^2=1\Bigr\}%Too big
> \stopformula
>
> \getbuffer
>
> \setupmathfence[Set][factor=1]%I like this one
> \getbuffer
>
> \setupmathfence[Set][factor=auto]%Too big
> \getbuffer
>
> %\setupmathfence[Set][factor=big]%Perhaps this could work? Or size=big or
> something
> %\getbuffer
> \stopTEXpage
>
I hate to do this, but a small *bump*
(If it is unclear what I'm asking for, I could try to clarify)
/Mikael
[-- Attachment #1.2: Type: text/html, Size: 3004 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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 prev parent reply other threads:[~2018-04-25 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 17:30 Mikael P. Sundqvist
2018-04-25 5:29 ` Mikael P. Sundqvist [this message]
2018-04-25 20:18 ` Hans Hagen
2018-04-26 5:39 ` Mikael P. Sundqvist
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=CAHy-LL813ObutyiJHorHFn5fM9cD_SiFr+oYMQRuBZbUyXiM6w@mail.gmail.com \
--to=mickep@gmail.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).