From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: Do typescripts slow down ConTeXt?
Date: Sun, 28 Sep 2003 15:36:55 +0200 [thread overview]
Message-ID: <D3831220-F1B8-11D7-82DF-0030659899AA@fiee.net> (raw)
In-Reply-To: <a05210600bb9c75b5c37c@[217.184.8.20]>
Sorry, I can't tell you anything about speed, but perhaps some other
useful hints...
Am Sonntag, 28.09.03, um 13:44 Uhr (Europe/Zurich) schrieb Steffen
Wolfrum:
> \usetypescriptfile[type-buy]
why?
> %
> \starttypescript [serif] [agaramond] [ec]
> \definefontsynonym [AGaramond-Regular] [padr9e] [encoding=ec]
You should perhaps use "\defaultencoding" instead of "ec", that's more
flexible.
Or are your font files in ec? (I wouldn't use berry names at all, but
that's
a matter of taste.)
> \usetypescript[serif][fallback]
I don't think that's necessary.
Grüßlis vom Hraban!
--
http://www.fiee.net/texnique/
next prev parent reply other threads:[~2003-09-28 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 11:44 Steffen Wolfrum
2003-09-28 12:18 ` Patrick Gundlach
2003-09-29 8:52 ` Hans Hagen
2003-09-28 13:36 ` Henning Hraban Ramm [this message]
2003-09-29 10:39 Steffen Wolfrum
2003-09-29 11:37 Steffen Wolfrum
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=D3831220-F1B8-11D7-82DF-0030659899AA@fiee.net \
--to=hraban@fiee.net \
--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).