From: Cecil Westerhof <cldwesterhof@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Defined and not defined and better be done global
Date: Sat, 27 Apr 2013 11:44:19 +0200 [thread overview]
Message-ID: <CAG-LmmB7RURu-dyXK5qpM50=AmWvMZ8m3NqiebxKVDxw1s9qUg@mail.gmail.com> (raw)
In-Reply-To: <517AFD5D.3010401@wxs.nl>
2013/4/27 Hans Hagen <pragma@wxs.nl>:
> On 4/26/2013 10:43 PM, Cecil Westerhof wrote:
>>
>> When running ConTeXt I see a lot of this kind of messages:
>> fonts > bodyfont 15pt is defined (can better be done global)
>> fonts > bodyfont 1.25em is defined (can better be done global)
>> fonts > bodyfont 1.25em is not defined
>> fonts > bodyfont 1.25em is defined (can better be done global)
>> fonts > bodyfont 15pt is defined (can better be done global)
>> fonts > bodyfont 1.25em is defined (can better be done global)
>> fonts > bodyfont 1.25em is not defined
>> fonts > bodyfont 1.25em is defined (can better be done global)
>> fonts > bodyfont 15pt is defined (can better be done global)
>> fonts > bodyfont 1.25em is defined (can better be done global)
>> fonts > bodyfont 1.25em is not defined
>>
>> What am I doing wrong?
>
>
> switching a bodyfont with an undefined bodyfontenvironment inside a group,
> which is very inefficient
>
> (and a 1.5em bodyfont switch can probably better be replaced by a direct
> font definition)
I will look into the bodyenvironment stuff. Is not much to go on. :-(
Had to delve into what I am doing. Was a ‘little while ago’ I wrote it.
I thought that 1.5em was used for relative definitions. I have a inc
file that I use. In this I have:
\def\Title{\dodoubleempty\doTitle}
\def\doTitle[#1][#2]{
\ifsecondargument
\testpage[#2]
\else
\testpage[15]
\fi
\startalignment[center]
{
\myblank[2*big]
\switchtobodyfont[1.5em]
\bf\em#1
}
\myblank
\stopalignment
}
In this case I have in my mane document:
\input /home/cecil/ConTeXt-inc/standard-init.inc
\setupbodyfont[palatino,10pt]
What would be a better way to do this? I prefer my include file
deciding the increase of the font.
--
Cecil Westerhof
___________________________________________________________________________________
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:[~2013-04-27 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 20:43 Cecil Westerhof
2013-04-26 22:19 ` Hans Hagen
2013-04-27 9:44 ` Cecil Westerhof [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='CAG-LmmB7RURu-dyXK5qpM50=AmWvMZ8m3NqiebxKVDxw1s9qUg@mail.gmail.com' \
--to=cldwesterhof@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).