From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
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 22:20:12 +0200 [thread overview]
Message-ID: <20120603202012.GA15076@phlegethon> (raw)
In-Reply-To: <4FCB9EA2.7040904@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2146 bytes --]
Hi Hans!
···<date: 2012-06-03, Sunday>···<from: Hans Hagen>···
> On 3-6-2012 16:27, Philipp Gesang wrote:
>
> >That’s odd. But this way it seems to do the right thing as
> >performance improves drastically (as much as 30%).
>
> a bodyfont is a collection of related fonts / sizes and when such a
> set is defined first inside a group you potentially end up with many
> (redundant) definitions .. this is why a bodyfont environment has to
> be defined at the outer level (as wolfgang pointed out)
>
> \tracefontdefinitions
Nice forensics tool.
With this I can see plainly that, as reported by Wolfgang,
\definebodyfontenvironment[42.0pt] results in the dimension’s
decimal place to be stripped before font definition.
Which makes me wonder whether \switchtobodyfont should do a
\normalizebodyfontsize on the #specification before triggering
the switch? So that 42.0pt be interpreted as 42pt? Now that I’m
aware of it I can as well build that into my macros either ...
Regards
Philipp
>
> sometimes gives some insight in efficiency
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
> | 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 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
___________________________________________________________________________________
prev parent reply other threads:[~2012-06-03 20:20 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
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 [this message]
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=20120603202012.GA15076@phlegethon \
--to=gesang@stud.uni-heidelberg.de \
--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).