From: Hans Hagen <j.hagen@xs4all.nl>
To: Sylvain Hubert <champignoom@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \switchtobodyfont behaves differenctly with splitted parameters
Date: Sun, 8 Nov 2020 12:52:17 +0100 [thread overview]
Message-ID: <5d4c9245-9b84-d42d-fa28-981dc28d210b@xs4all.nl> (raw)
In-Reply-To: <CACNy3NC67D7dM-uVY6EbgURVHc6dyq+P9s_vDRAvnX207N4iBg@mail.gmail.com>
On 11/8/2020 12:46 PM, Sylvain Hubert wrote:
> On Sun, 8 Nov 2020 at 12:14, Hans Hagen <j.hagen@xs4all.nl
> <mailto:j.hagen@xs4all.nl>> wrote:
>
> when yyou use several bodyfonts you can do this before \starttext:
>
> \usebodyfont[face,24pt]
> \usebodyfont[deface]
>
> \starttext
> ....
> \stoptext
>
>
> Thank you for the information, Hans!
>
> Could you please also shed some light on the relation/difference among
> \{setup,switchto,use}bodyfont?
> There seems to be not much documentation on this. Can one conclude, from
> the wiki <https://wiki.contextgarden.net/Command/switchtobodyfont> and
> the source code
> <https://source.contextgarden.net/tex/context/base/mkiv/font-ini.mklx#l2287>,
> that they are mostly the same, except that \switchtobodyfont is
> restricted to the content area, and \usebodyfont is a helper to call
> \setupbodyfont in the beginning?
>
> If this is the case, is it recommended to always put a
> \setupbodyfont[...] in the beginning, even if it's just a
> \setupbodyfont[modern]?
> One reason might be that the following example somehow enlarges the page
> number in the header, intuitively contradicting what is claimed by the
> wiki <https://wiki.contextgarden.net/Command/switchtobodyfont>:
>
> \switchtobodyfont[dejavu]
> \starttext \switchtobodyfont[dejavu, 24pt]a\stoptext
\setup is document wide
\switch is for local usage
(has to do with picking up font/space related issues after page breaks
and when typesetting page ornaments like headers and footers)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2020-11-08 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 1:35 Sylvain Hubert
2020-11-08 9:38 ` Pablo Rodriguez
2020-11-08 10:18 ` Sylvain Hubert
2020-11-08 10:28 ` Sylvain Hubert
2020-11-08 10:34 ` Pablo Rodriguez
2020-11-08 11:02 ` Sylvain Hubert
2020-11-08 11:06 ` Wolfgang Schuster
2020-11-08 11:14 ` Hans Hagen
2020-11-08 11:46 ` Sylvain Hubert
2020-11-08 11:52 ` Hans Hagen [this message]
2020-11-08 12:08 ` Sylvain Hubert
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=5d4c9245-9b84-d42d-fa28-981dc28d210b@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=champignoom@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).