ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Allin Cottrell <cottrell@wfu.edu>
Cc: ntg-context@let.uu.nl
Subject: Re: font hell
Date: Sat, 19 Jan 2002 14:11:53 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0201191402240.9112-100000@ricardo.ecn.wfu.edu> (raw)
In-Reply-To: <874rlig35s.fsf@dellius.nederware.nl>

On 19 Jan 2002, Berend de Boer wrote:

> > But now I find I am in font hell!  No documents will compile, no fonts
> > are found.
>
> Yep, me too :-)
>
> Are there really people who have this stuff working with the standard
> postscript fonts somehow?

Actually, I just made some progress.  The point seems to be that there
is a whole new naming scheme for tfms in the 2001-11 ConTeXt: tfm
names are prefixed with "ec-", "texnansi-" and so on, depending on the
encoding.  You must specify a default encoding, then ensure that
the tfms can be found.  One way would be to copy or symlink the
original tfms to the new names, but better (IMO) is to add a set of
"fontsynonyms" to ConTeXt's type-enc.tex, so that the old names are
usable.  For example, I added the following so that the existing
Y&Y tfms for Lucida would be used:

  \definefontsynonym [texnansi-lbr]               [lbr]
  \definefontsynonym [texnansi-lbd]               [lbd]
  \definefontsynonym [texnansi-lbdi]              [lbdi]
  \definefontsynonym [texnansi-lbi]               [lbi]
  \definefontsynonym [texnansi-lbrsc]             [lbrsc]
  \definefontsynonym [texnansi-lbdsc]             [lbdsc]
  \definefontsynonym [texnansi-lbsl]              [lbsl]

My next question is, how do we get the presentation templates working
with the 2001/11 release?  The directives to make headings boldface
are broken (e.g. \bfc doesn't do anything).

Allin Cottrell.


  reply	other threads:[~2002-01-19 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-19  2:06 Allin Cottrell
2002-01-19  8:23 ` Berend de Boer
2002-01-19 19:11   ` Allin Cottrell [this message]
     [not found]   ` <Pine.LNX.4.44.0201191402240.9112-100000@ricardo.ecn.wfu.ed u>
2002-01-20 21:44     ` 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=Pine.LNX.4.44.0201191402240.9112-100000@ricardo.ecn.wfu.edu \
    --to=cottrell@wfu.edu \
    --cc=ntg-context@let.uu.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).