From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Re: MP Graph - Berry problems 23/10/2002
Date: Mon, 4 Nov 2002 21:32:36 +0100 [thread overview]
Message-ID: <20021104213236.6aa4dcc2.morawski@gmx.net> (raw)
In-Reply-To: <B9EC4415.B2F8%king@dircon.co.uk>
On Mon, 04 Nov 2002 15:34:45 +0000
Nigel King <king@dircon.co.uk> wrote:
> I mistakenly thought
> that I was expecting 8a on the end for ec encoding. I do have ec-utmr8a.tfm
> manufactured by texfont by type-tmf.dat dated 11/9/01 even thought the
> overall context is 23/10/02.
8a means the original encoding of the AFMs. texfont takes this basename and
precedes this with a ec- for a T1 (ec) encoded font. This is the ConTeXt/texfont
naming scheme. If you stick to the Berry naming scheme then this font will
be 8t in T1 encoding, 7t in OT1 and there are some more, see fontinst.[dvi|ps|pdf]
on CTAN. Normally the T1 encoded fonts are already on your system due to
the LaTeX PSNFSS (PostScript New Font Selection Scheme) has already installed it.
Thus you don't need to install them again using texfont, the only thing to do is
to tell ConTeXt that the Berry fontnames have to be used. This is exactly what
\usetypescript[berry][ec] does.
Jens
prev parent reply other threads:[~2002-11-04 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021028210944.28543@news.comp.lancs.ac.uk>
2002-10-30 8:55 ` MP Graph Hans Hagen
2002-10-30 10:12 ` Adam Lindsay
2002-10-30 13:46 ` Hans Hagen
2002-10-31 16:05 ` Nigel King
2002-10-31 23:28 ` Hans Hagen
2002-11-03 22:05 ` Re: MP Graph - Berry problems 23/10/2002 Nigel King
2002-11-04 8:59 ` Jens-Uwe Morawski
2002-11-04 10:48 ` Nigel King
2002-11-04 14:00 ` Jens-Uwe Morawski
2002-11-04 15:34 ` Nigel King
2002-11-04 20:32 ` Jens-Uwe Morawski [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=20021104213236.6aa4dcc2.morawski@gmx.net \
--to=morawski@gmx.net \
/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).