From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt ML <ntg-context@ntg.nl>
Subject: Re: Installing mathpazo
Date: Wed, 08 Aug 2001 10:00:35 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010808095655.0251fc90@server-1> (raw)
In-Reply-To: <20010806202556.A21884@localhost>
At 08:25 PM 8/6/2001 +0200, Marco Kuhlmann wrote:
>Hans Hagen wrote (2001-08-06 (16:29)):
>
> > the \definetypeface commands then go into your document style,
> > and the newly created file is taken into account too,
>
>I think that was my mistake; I had the \definetypeface commands
>in the typescript file. (I do not really know why this i
>important, though.)
this is because typescripts are not put into tex's memory, but parsed each
time, which means that they need to be stored in a loadable way, i.e. in a file
>Great, I now managed to get things running with my mathpazo
>setup, and things look nice. I even succeeded in convincing
>ConTeXt to do protruding for Roman, Italic, and Bold Italic;
>Bold doesn't seem to feel need to obey. But as I understand,
>support for the protruding mechanism is still changing, right?
protruding should work, also for bold, but you need the latest pdftex [with
the em-based method] and also must load the protruding as early as
possible, since it is connected to the first instantiation of fonts. [nasty
global/efficiency stuff in tex]; also, context disables protruding in
controlled situations, like in page building
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
prev parent reply other threads:[~2001-08-08 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 13:42 Marco Kuhlmann
2001-08-06 14:29 ` Hans Hagen
2001-08-06 18:25 ` Marco Kuhlmann
2001-08-08 8:00 ` Hans Hagen [this message]
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=5.1.0.14.1.20010808095655.0251fc90@server-1 \
--to=pragma@wxs.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).