From: Maarten Sneep <sneep@nat.vu.nl>
Subject: Re: Fonts again in ConTeXt
Date: Wed, 12 Mar 2003 14:26:34 +0100 [thread overview]
Message-ID: <03031214263404.11186@mondriaan> (raw)
In-Reply-To: <C05742C7-548D-11D7-93AD-0050E4258255@fastmail.fm>
On Wednesday 12 March 2003 14:23, you wrote:
> The "8r" at the end of the psnfss version also gives the encoding, and
> I don't really think there's a need to have the precise pfb name in the
> tfm file name. That's not to say there aren't problems with psnfss,
> just that in this context those problems aren't important.
OK.
> > Since texfont uses afm2tfm directly (and the tfm files that come with
> > psnfss are hand tuned) I don't think that using texfont blindly is a very
> > good idea. It would be better to use the existing tfm files.
>
> Right. Patrick has a file that maps the ConTeXt names to the pfsnss
> names, which solves the problem.
Although that means you have to adapt the sources of the files you receive to
use this intermediate translation file. Although I suspect this is something
that could be put in cont-sys.tex (anyone for the exact command?) and make it
a system wide local configuration.
BTW isn't this something that sould be addressed by using
\usetypescript[ber]? (Or did I miss something?)
Maarten
next prev parent reply other threads:[~2003-03-12 13:26 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 16:25 Displayed material, again Giuseppe Bilotta
2003-03-10 16:50 ` Bruce D'Arcus
2003-03-10 20:22 ` Re[2]: " Giuseppe Bilotta
2003-03-10 22:15 ` s-mag-01 Bruce D'Arcus
2003-03-11 8:00 ` s-mag-01 Hans Hagen
2003-03-11 14:11 ` s-mag-01 Bruce D'Arcus
2003-03-11 14:31 ` s-mag-01 Hans Hagen
2003-03-11 14:34 ` s-mag-01 Bruce D'Arcus
2003-03-11 14:46 ` Fonts again in ConTeXt Patrick Gundlach
2003-03-11 15:10 ` Bruce D'Arcus
2003-03-12 13:04 ` Maarten Sneep
2003-03-12 13:23 ` Bruce D'Arcus
2003-03-12 13:26 ` Maarten Sneep [this message]
2003-03-12 14:05 ` Patrick Gundlach
2003-03-12 15:11 ` Hans Hagen
2003-03-12 15:43 ` Patrick Gundlach
2003-03-12 19:35 ` Jens-Uwe Morawski
2003-03-13 8:31 ` Patrick Gundlach
2003-03-14 8:27 ` Hans Hagen
2003-03-12 20:26 ` Hans Hagen
2003-03-13 8:54 ` Patrick Gundlach
2003-03-13 12:37 ` Hans Hagen
2003-03-13 15:07 ` John Culleton
2003-03-13 15:52 ` Hans Hagen
2003-03-21 18:05 ` Patrick Gundlach
2003-03-22 11:10 ` Hans Hagen
2003-03-14 21:34 ` Henning Hraban Ramm
2003-03-14 21:24 ` Henning Hraban Ramm
2003-03-21 18:06 ` Patrick Gundlach
2003-03-12 15:09 ` Hans Hagen
2003-03-11 15:02 ` s-mag-01 Adam Lindsay
2003-03-11 20:52 ` s-mag-01 Hans Hagen
2003-03-11 9:13 ` s-mag-01 Patrick Gundlach
2003-03-10 17:00 ` Displayed material, again Hans Hagen
2003-03-10 23:24 ` Hans Hagen
2003-03-11 10:08 ` Re[2]: " Giuseppe Bilotta
2003-03-11 10:52 ` Hans Hagen
2003-03-11 11:47 ` Re[3]: " Giuseppe Bilotta
2003-03-11 14:57 ` Hans Hagen
2003-03-11 17:04 ` Re[4]: " Giuseppe Bilotta
2003-03-12 20:36 ` Hans Hagen
2003-03-13 9:36 ` Re[5]: " Giuseppe Bilotta
2003-03-13 12:23 ` Hans Hagen
2003-03-11 15:12 ` Re[3]: " Hans Hagen
2003-03-12 21:07 ` Hans Hagen
2003-03-13 9:38 ` Re[4]: " Giuseppe Bilotta
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=03031214263404.11186@mondriaan \
--to=sneep@nat.vu.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).