From: Martin Althoff <martin.althoff@yahoo.com>
To: ntg-context@ntg.nl
Subject: Re: using \definebodyfont with multiple size declarations -- Why?
Date: Wed, 28 Jul 2010 02:47:44 -0700 (PDT) [thread overview]
Message-ID: <147576.20931.qm@web56303.mail.re3.yahoo.com> (raw)
In-Reply-To: <4C4F1A8D.8020103@wxs.nl>
Hans, thanks for the detailed answer! My understanding is slowly advancing :D
> in principle we could do without, but this helps
> predefining a couple of things that otherwise would slow
> down each font switch
This confirms my (vague) assumption that deep in the internals it helps structure things.
> it also relates to bodyfont environments where there are
> relationships between sizes
... thereby creating the a "font enviroment"
> in practice, if you choose say 13pt it will work out
> ok as things are checked and defined on the fly; but
> there might be a slight performance hit
This goes towards my fear: I prefer to state things explicitly. "Automagic" that happens in the background covering up for my sloppyness is great, but... creates confusion when things trip up. Internals might change. Or I might have been building on side effects for all I know.
For this reason examples with wordy declarations are welcome... Working with hard-blocking Modula compilers was a good teacher, but that's long ago.
> you probably want features enables, so "*default"
> \definefont [WonderFont] [BoldItalic*default sa 4.8]
Hm, I'll have to read up on that one.
Thanks ! Martin
___________________________________________________________________________________
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:[~2010-07-28 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 9:36 Martin Althoff
2010-07-27 17:42 ` Hans Hagen
2010-07-28 9:47 ` Martin Althoff [this message]
2010-07-28 10:41 ` Hans Hagen
2010-07-28 10:46 ` luigi scarso
2010-07-28 10:54 ` Arthur Reutenauer
2010-07-29 1:35 ` Martin Althoff
2010-07-27 20:28 ` Wolfgang Schuster
2010-07-28 9:08 ` Martin Althoff
2010-07-28 9:20 ` Arthur Reutenauer
2010-07-28 9:20 ` Hans Hagen
2010-07-28 9:30 ` Martin Althoff
[not found] <4C4FFA8F.9000904@wxs.nl>
2010-07-28 9:50 ` Martin Althoff
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=147576.20931.qm@web56303.mail.re3.yahoo.com \
--to=martin.althoff@yahoo.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).