From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: \switchtobodyfont behaves differenctly with splitted parameters
Date: Sun, 8 Nov 2020 10:38:28 +0100 [thread overview]
Message-ID: <f75f54d0-ae08-bb04-9e19-9eef62fdf8dd@gmx.es> (raw)
In-Reply-To: <CACNy3NCC+fvVoD1Gx2qvzbE-bAe_aTX042nB6m55U29TfzukJw@mail.gmail.com>
On 11/8/20 2:35 AM, Sylvain Hubert wrote:
> Dear List,
>
> after hours of debugging, I finally found out that
> \switchtobodyfont[face, 20pt] does NOT behave the same with
> \switchtobodyfont[face]\switchtobodyfont[20pt]. In my case the latter is
> the correct one, while the former does nothing but falling back to
> latinmodern.
>
> Does anyone know when or why \switchtobodyfont behaves differently with
> splitted and joined parameters?
Hi Sylvain,
as a general rule, it helps when there is a minimal sample that provides
the problematic behavior.
I don’t get diffferent results:
\definefontfamily[mainface][rm][TeX Gyre Pagella]
\definefontfamily[face][rm][TeX Gyre Heros]
\setupbodyfont[mainface]
\startbuffer
In my case, the latter is the correct one, while the former does
nothing but falling back to latinmodern.\par
\stopbuffer
\starttext
\getbuffer
\switchtobodyfont[face]\switchtobodyfont[20pt]
\getbuffer
\switchtobodyfont[face, 20pt]
\getbuffer
\stoptext
Correct the sample to show what I got wrong from your message.
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 9:38 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 [this message]
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
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=f75f54d0-ae08-bb04-9e19-9eef62fdf8dd@gmx.es \
--to=oinos@gmx.es \
--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).