From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: fontsize changes not understood
Date: Tue, 24 May 2016 17:00:00 +0200 [thread overview]
Message-ID: <57446C70.2030606@gmail.com> (raw)
In-Reply-To: <BB1B45F9-909B-4380-ADCB-AB71857136A7@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1107 bytes --]
> Meer, Hans van der <mailto:H.vanderMeer@uva.nl>
> 24. Mai 2016 um 16:28
>
> Thanks, I really didn't know that, it could not spot it in my copy of
> "Fonts in Context".
>
> But although reset works for \switchtobodyfont, it is not working in
> \usebodyfont[reset,9pt] in the second section.
Why do you think \usebodyfont can be used to change the font size in
your document, is this mentioned in a manual?
> There it keeps the size derived from the section title. Both commands
> however, are reported to inherit from \setupbodyfont (where the reset
> is named). Should that be correct?
IIRC \usebodyfont can be used to preload a typeface at the begin of a
document which make switching to it later in the document with
\switchtobodyfont or \setupbodyfont faster but this also means settings
like the font size have no effect. The reference manual shows "inherits
from XXX" in such a case because a) it is true that the command inherits
its values from another command b) it’s faster to document (can be
changed but one has to check which arguments are valid).
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2382 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-05-24 15:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 13:04 Meer, Hans van der
2016-05-24 13:57 ` Wolfgang Schuster
2016-05-24 14:28 ` Meer, Hans van der
2016-05-24 15:00 ` Wolfgang Schuster [this message]
2016-05-24 15:47 ` Meer, Hans van der
2016-05-24 16:09 ` Jean-Pierre Delange
2016-05-24 15:57 ` win64 : luatex is not recognize as an internal command Jean-Pierre Delange
2016-05-24 16:56 ` Hans Hagen
2016-05-24 17:55 ` Alan BRASLAU
2016-05-24 22:30 ` Hans Hagen
2016-05-24 18:29 ` Jean-Pierre Delange
2016-05-24 22:10 ` Jean-Pierre Delange
2016-05-24 22:42 ` Hans Hagen
2016-05-24 22:48 ` L.S.-Soc&Gam
2016-05-24 22:50 ` L.S.-Soc&Gam
2016-05-25 8:46 ` Mojca Miklavec
2016-05-25 9:18 ` Hans Hagen
2016-05-26 1:00 ` L.S.-Soc&Gam
2016-05-25 9:36 ` Jean-Pierre Delange
2016-05-25 14:14 ` ConTeXt on Mac OS X installation Jean-Pierre Delange
2016-05-25 16:32 ` Jean-Pierre Delange
2016-05-25 17:28 ` Jean-Pierre Delange
2016-05-24 16:59 ` win64 : luatex is not recognize as an internal command josephcanedo
2016-05-24 14:04 ` fontsize changes not understood Hans Hagen
2016-05-24 14:10 ` Sorting index register Manuel Conzelmann
2016-05-24 14:13 ` Wolfgang Schuster
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=57446C70.2030606@gmail.com \
--to=schuster.wolfgang@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).