From: "dr. Hans van der Meer" <hansm@science.uva.nl>
Subject: definetypeface usage
Date: Mon, 5 Jul 2004 13:48:35 +0200 [thread overview]
Message-ID: <3F1C7339-CE79-11D8-B79D-003065568054@science.uva.nl> (raw)
Trying to findout how ConTeXt's font mechanism works, I come to
following question:
From the brochure "Fonts in Context" (mfonts.pdf) I have picked up the
notion that exercising a call to \definetypeface gets fonts in working
order (see the examples there on font specifiers "funny" and "whow",
for example, and the resulting typeface collection).
Also in file type-exa.tex there is a typescript [postscript] where
\definetypeface is exercised, seemingly to bring a matched series of
times, helvetica and courier into existence.
However, the usage of the postscript fonts via \setupbodyfont[pos]
seems to be completely unconnected with this script (I traced the
typescript checking). Neither can I find somany calls to
\definetypeface (and its derivatives \dodefinetypeface and
\dododefinetypeface); it seems they are barely used in the code.
So, the questions are:
- Does \setupbodyfont[pos] results in the scaled font set as given in
type-exa?
- Or does \definetypeface belong to an alternative/obsolete font
definition scheme, totally unrelated to the definitions called up in
the scripts in type-pre.tex, type-syn.tex, and other friends?
- In preparing font scripts, can I therefore totally ignore
\definetypeface or will that be disastrous for the result?
If somebody would be so kind to enlighten me...
Hans van der Meer
reply other threads:[~2004-07-05 11:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F1C7339-CE79-11D8-B79D-003065568054@science.uva.nl \
--to=hansm@science.uva.nl \
--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).