From: Henk Koster <H.A.J.Koster@xs4all.nl>
Subject: Re: LucidaBright fonts...I'm stumped
Date: Thu, 01 Dec 2005 13:38:49 +0100 [thread overview]
Message-ID: <pan.2005.12.01.12.38.48.847209@xs4all.nl> (raw)
In-Reply-To: <pan.2005.12.01.10.20.32.729477@xs4all.nl>
As a follow-up to my earlier message...
I don't understand why ConTeXt cannot use the LB .afm/.pfb/.tfm files that
are already present (for the texnansi encoding) in my LaTeX setup. Why
does texfont need to duplicate all these files? Does ConTeXt not use the
directory path search of teTeX?
It seems to me that, in my case, texfonts only needs to generate files
that are peculiar to ConTeXt, like "texnansi-yandy-lucida.tex and
.map", and further use the .afm, .pfb and .tfm files that are already
present -- is there a way to do that?
--
H.A.J. Koster
"Behavioral axioms are right, but agents make mistakes..."
(attributed to L.J. Savage)
next prev parent reply other threads:[~2005-12-01 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 10:20 Henk Koster
2005-12-01 12:38 ` Henk Koster [this message]
2005-12-02 13:39 ` Hans Hagen
2005-12-01 12:52 ` Hans Hagen
2005-12-02 10:32 ` Richard Gabriel
2005-12-02 15:34 ` Hans Hagen
2005-12-02 15:50 ` Taco Hoekwater
2005-12-02 16:21 ` Hans Hagen
2005-12-02 20:37 ` Henk Koster
2005-12-04 21:10 ` Hans Hagen
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=pan.2005.12.01.12.38.48.847209@xs4all.nl \
--to=h.a.j.koster@xs4all.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).