From: Hans Hagen <pragma@wxs.nl>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: beta/problem with layers
Date: Wed, 02 Feb 2011 18:13:14 +0100 [thread overview]
Message-ID: <4D4990AA.7040003@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.01.1102021141440.7551@ybpnyubfg.ybpnyqbznva>
On 2-2-2011 5:46, Aditya Mahajan wrote:
> On Wed, 2 Feb 2011, Hans Hagen wrote:
>
>> On 2-2-2011 4:07, Aditya Mahajan wrote:
>>
>>> There is no point in not loading the fonts in the begining if one would
>>> then have to come up with clever ways to force loading of a font. I hope
>>> that there is a more robust solution so that
>>
>> well, it depends ... how many use lm for documents?
>
> Don't know, but I am pretty sure that layers are used all over the
> place. In most of my documents, I set the layers in an evironment file,
> which is often loaded before \starttext.
>
>> as Wolfgang mentioned, setting a layer will use the current font which
>> might not be the same as one sets later;
>
> Oh, that is a bigger problem. That means that the first thing in a style
> should be font loading... if nothing else then just \setupbodyfont[11pt].
>
> Perhaps \setlayer (or even \hbox!!) should issue a warning if the fonts
> have not been loaded yet.
How about:
\unprotect
\def\dozerostagepreloadfonts
{\definedfont[\s!file:lmmono10-regular sa 1]}
\def\zerostagepreloadfonts
{\writestatus\m!fonts{beware: no fonts are loaded yet so content will
not show up}%
\glet\zerostagepreloadfonts\dozerostagepreloadfonts
\zerostagepreloadfonts}
\everyhbox{\zerostagepreloadfonts}
\everyvbox{\zerostagepreloadfonts}
\def\resetpreloadfonts
{\global\let\zerostagepreloadfonts \relax
\global\let\firststagepreloadfonts \relax
\global\let\secondstagepreloadfonts\relax
\global\let\thirdstagepreloadfonts \relax
\global\let\fourthstagepreloadfonts\relax
\global\everyhbox\emptytoks
\global\everyvbox\emptytoks
\resetnullfont}
\protect
\setbox0\hbox{xxx}
\starttext
test \box0
\stoptext
-----------------------------------------------------------------
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:[~2011-02-02 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 10:43 Andreas Harder
2011-02-01 11:11 ` Wolfgang Schuster
2011-02-01 12:33 ` Andreas Harder
2011-02-02 10:24 ` Wolfgang Schuster
2011-02-02 15:07 ` Aditya Mahajan
2011-02-02 15:20 ` Hans Hagen
2011-02-02 16:46 ` Aditya Mahajan
2011-02-02 17:02 ` Hans Hagen
2011-02-02 17:13 ` Hans Hagen [this message]
2011-02-02 21:19 ` Wolfgang Schuster
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=4D4990AA.7040003@wxs.nl \
--to=pragma@wxs.nl \
--cc=adityam@umich.edu \
--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).