From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco <netuse@lavabit.com>
Subject: Re: Multiple layers question
Date: Mon, 04 Jun 2012 17:54:46 +0200 [thread overview]
Message-ID: <4FCCDA46.7010506@wxs.nl> (raw)
In-Reply-To: <20120604154127.5f192cb7@Zewz>
On 4-6-2012 15:41, Marco wrote:
> On 2012-06-04 Marcin Borkowski<mbork@wmi.amu.edu.pl> wrote:
>
> Cześć Marcin,
>
>> Dnia 2012-06-04, pon o godzinie 14:33 +0200, Wolfgang Schuster pisze:
>>
>>> Load a font or move the \setlayer commands after \starttext.
>>
>> Thanks a lot!
>>
>> But why is that so?
>
> Until some years ago the latin modern font was always automatically
> loaded, regardless of the users choice of font. Font loading takes a
> considerable amount of time (check the stats at the end of a context
> run). This led to the question:
>
> “Why start loading a big, complex font like latin modern before we
> know which font the user actually wants to use and waste several
> seconds on it, just to start loading the users choice afterwards?”
>
> The answer was:
>
> ”We delay loading the font until we know which font the user wants
> to use. If the user doesn't tell us, then we fall back to latin
> modern.”
>
> The body font is set up in the setup area (the part above
> \starttext). That, in turn, means that when having reached
> \starttext, the users choice of font is known and can be loaded. It
> is more efficient if a font other then latin modern is used.
>
> One drawback is that typeset text in the setup area has no font
> setup and will fall back to latin modern mono. Usually you don't
> typeset text in the setup area. However, layers are an exception and
> you need to set up the body font beforehand.
a good text for the wiki (and also for the font manual)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-06-04 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 12:06 Marcin Borkowski
2012-06-04 12:33 ` Wolfgang Schuster
2012-06-04 12:39 ` Marcin Borkowski
2012-06-04 13:41 ` Marco
2012-06-04 15:54 ` Hans Hagen [this message]
2012-06-04 12:36 ` Marco
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=4FCCDA46.7010506@wxs.nl \
--to=pragma@wxs.nl \
--cc=netuse@lavabit.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).