From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: definebodyfontenvironment
Date: Mon, 16 May 2016 22:22:59 +0200 [thread overview]
Message-ID: <573A2C23.1040209@gmail.com> (raw)
In-Reply-To: <25B3B06C-2EB5-48A9-8C8C-1865827277DC@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1622 bytes --]
> Meer, Hans van der <mailto:H.vanderMeer@uva.nl>
> 14. Mai 2016 um 21:13
> I think I did not state the problem clear enough.
> The solution given here supposes that the fontsize is known beforehand.
> However, what I am doing is calculating a font size based on the
> current one and than switch to that size.
> It is part of a fontsize changing mechanism inside an xmlsetup. In
> short what I am doing is:
>
> \scratchdimen=\the\dimexpr\bodyfontsize\relax
> \advance\scratchdimen 'somevalue' \relax
> %\definebodyfontenvironment[\the\scratchdimen]
> \begingroup
> % must keep the change local
> \switchtobodyfont[\the\scratchdimen]
> ...
> \endgroup
>
> The commented out \definebodyfontenvironment kills a lot of the font
> messages but I fear that each the time the same work is done as
> without it. The only benefit being the suppression of the font
> messages in the log ;-)
>
> It might be impossible to accomplish this efficiently -- that is
> execute the font calculations once only for the given size. But at
> least I would like to give it a try.
>
You can save time with the \definebodyfontenvironment command.
In the following example context has to create a new bodyfont
environment for each iteration (because the values are local
to the group) to calculate the a, b, c etc. sizes which takes time
but in the same loop context only has to load the predefined size.
\starttext
\testfeatureonce{1000}
{\begingroup
\switchtobodyfont[18pt]
\endgroup}
\definebodyfontenvironment[18pt]
\testfeatureonce{1000}
{\begingroup
\switchtobodyfont[18pt]
\endgroup}
\stoptext
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3959 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:[~2016-05-16 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 15:55 definebodyfontenvironment Meer, Hans van der
2016-05-14 18:00 ` definebodyfontenvironment Wolfgang Schuster
2016-05-14 19:13 ` definebodyfontenvironment Meer, Hans van der
2016-05-16 20:22 ` Wolfgang Schuster [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=573A2C23.1040209@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).