From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: “bodyfont %s is defined (can better be done global)”
Date: Sun, 3 Jun 2012 15:58:57 +0200 [thread overview]
Message-ID: <DBAEF853-BE2F-4DB6-9934-4EC4D5C42DBB@googlemail.com> (raw)
In-Reply-To: <20120603100120.GD22936@phlegethon>
Am 03.06.2012 um 12:01 schrieb Philipp Gesang:
> Hi Wolfgang!
>
> ···<date: 2012-06-03, Sunday>···<from: Wolfgang Schuster>···
>
>> Am 02.06.2012 um 20:13 schrieb Philipp Gesang:
>>
>>> Dear listmates,
>>>
>>> with \switchtobodyfont I get the interface message “fonts:14”
>>> from mult-mes.lua (“bodyfont %s is defined (can better be done
>>> global)”) which is kinda hard to grep for :( Example:
>>>
>>> \definebodyfont[42pt][rm][default]
>>> \starttext
>>> \switchtobodyfont [42pt]
>>> \setupbodyfont [42pt]
>>> \stoptext
>>>
>>> Which results in:
>>>
>>> ········································································
>>> <... />
>>> fonts > bodyfont 42pt is defined (can better be done global)
>>> fonts > bodyfont 50.4pt is defined (can better be done global)
>>> fonts > bodyfont 40.32pt is defined (can better be done global)
>>> <... />
>>> ········································································
>>>
>>> (\setupbodyfont doesn’t cause it.) It seems harmless but (a) I
>>> have a conditional font change that may repeat hundreds of times
>>> over the course of a document and it clutters my terminal, and
>>> (b) it’s a warning after all, so everything is not as it is
>>> supposed to be. What’s it telling me, and why?
>>
>>
>> Add \definebodyfontenvironment:
>>
>> \definebodyfontenvironment[42pt]
>> \starttext
>> \setupbodyfont[42pt]
>> \stoptext
>
> This is getting interesting now. I already do as you say, but a
> bit differently: I’m defining font sizes on the fly, however they
> are created from dimensions, so my macros actually expand to
> something like:
>
> ········································································
> \definebodyfontenvironment[42.0pt] %% a dozen times
> \starttext
> \switchtobodyfont[42.0pt] %% hundreds of times
> %\switchtobodyfont[42pt] %% <- this works, though
> foo
> \stoptext
> ········································································
>
> Which then results in this warning:
> ········································································
> fonts > bodyfont 42.0pt is defined (can better be done global)
> ········································································
>
> Although the size has been „defined“. My problem appears to be
> that I’m abusing dimensions as makeshift floats to calculate
> relative font sizes, interlinespace etc. via \dimexpr.
???
> Hadn’t thought about \switchtobodyfont expecting integers.
Don’t know what’s the problem but the message doesn’t appear
when you use for example 42.1pt.
Wolfgang
___________________________________________________________________________________
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:[~2012-06-03 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 18:13 Philipp Gesang
2012-06-03 0:47 ` S Barmeier
2012-06-03 8:31 ` Wolfgang Schuster
2012-06-03 10:01 ` Philipp Gesang
2012-06-03 13:58 ` Wolfgang Schuster [this message]
2012-06-03 14:27 ` Philipp Gesang
2012-06-03 15:12 ` Wolfgang Schuster
2012-06-03 20:30 ` Philipp Gesang
2012-06-03 17:28 ` Hans Hagen
2012-06-03 20:20 ` Philipp Gesang
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=DBAEF853-BE2F-4DB6-9934-4EC4D5C42DBB@googlemail.com \
--to=schuster.wolfgang@googlemail.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).