From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6558 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: font hell Date: Sun, 20 Jan 2002 22:44:12 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <5.1.0.14.1.20020120222953.02d58f00@server-1> References: <874rlig35s.fsf@dellius.nederware.nl> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Trace: main.gmane.org 1035397082 11666 80.91.224.250 (23 Oct 2002 18:18:02 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:18:02 +0000 (UTC) Cc: Berend de Boer , ntg-context@let.uu.nl Original-To: Allin Cottrell In-Reply-To: Xref: main.gmane.org gmane.comp.tex.context:6558 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6558 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 -------------------------------------------------------------------------