ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: Berend de Boer <berend@pobox.com>, ntg-context@let.uu.nl
Subject: Re: font hell
Date: Sun, 20 Jan 2002 22:44:12 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20020120222953.02d58f00@server-1> (raw)
In-Reply-To: <Pine.LNX.4.44.0201191402240.9112-100000@ricardo.ecn.wfu.ed u>

At 02:11 PM 1/19/2002 -0500, Allin Cottrell wrote:

>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).

It looks worse than it is. Actually, the old definitions *assumed* texnansi 
while the new are more explicit.

if you look into type-enc.tex and search for berry, you will notice that 
you can use the standard texmf names by saying things like

\usetypescript[berry][ec]

some more info can be found in cont-sys.rme

 From the 'edu' address i deduce that you're in the usa. For english, it 
seldom matters what encoding you use, which is why the old methods worked 
well. In europe many encodings are in use and one reason for moving to the 
new scheme, is that as soon as one starts fooling around with caps and 
slants the berry naming scheme is not enough, which is why texfont.pl uses 
longer names.

Now, when you want to use the free fonts that come with tex live with 
context, the overhead in extra tfm (that is, if you want them) is small 
compared to the ones already there.

Another reason for the existing scheme is that it makes managing map files 
more comvenient, esp if you also install commercial fonts.

If you have lbr's, you can use texfont to install them. The

I'm sorry if the change is confusing; if i need to add more mapping to raw

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
-------------------------------------------------------------------------
                                   fall-back web server: 
www.pragma-pod.nl
-------------------------------------------------------------------------


      parent reply	other threads:[~2002-01-20 21:44 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
     [not found]   ` <Pine.LNX.4.44.0201191402240.9112-100000@ricardo.ecn.wfu.ed u>
2002-01-20 21:44     ` 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.20020120222953.02d58f00@server-1 \
    --to=pragma@wxs.nl \
    --cc=berend@pobox.com \
    --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).