From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6185 Path: main.gmane.org!not-for-mail From: "George N. White III" Newsgroups: gmane.comp.tex.context Subject: Re: latest context problems Date: Fri, 16 Nov 2001 12:00:57 -0400 (AST) Sender: owner-ntg-context@let.uu.nl Message-ID: References: <5.1.0.14.1.20011116141503.02f27100@server-1> Reply-To: "George N. White III" NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1035396728 8306 80.91.224.250 (23 Oct 2002 18:12:08 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:12:08 +0000 (UTC) Cc: Berend de Boer , ConTeXt mailinglist Original-To: Hans Hagen In-Reply-To: <5.1.0.14.1.20011116141503.02f27100@server-1> Xref: main.gmane.org gmane.comp.tex.context:6185 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6185 On Fri, 16 Nov 2001, Hans Hagen wrote: > At 01:36 PM 11/16/2001 +0100, Berend de Boer wrote: > >Hallo Hans, > > > >With the latest context things like: > > > > \setupbodyfont > > [ber,pos] > > > >produce lots of error messages about missing fonts. I went back to my > >previous release. I had the saem experience, but rather than going back, I have been working with texfont.pl and the below mentioned documents describing the new font handling. The examples in showfont.pdf were useful in checking that things were set up properly. > Did you read the cont-sys.rme file? > > Because multiple conflicting encoding need to be supported, and because one > can create instances like slanted or capitalized locally, from now on we > use the more verbose names > > texnansi-blabla > > and alike [see mtexfont.pdf and mfonts.pdf] > > This also means that ber does not make much sense now. I still don't feel that I understand the new mechanisms well enough to make sensible decisions for the following questions (knowing that the answers differ depending on what fonts you normally use, how much use you make of LaTeX, etc.): 0. what options should be enabled in cont-sys.tex? 1. what should pdftex.map contain? Clearly this depends on what options you use from cont-sys.tex. I want to be able to use pdfelatex, but I prefer to load map files in each document because it helps me to keep track of what fonts are used. My current thinking is that pdftex.map should consist of just the cm portion of bsr.map with original-ams-logo .map, etc. loaded via cont-sys.tex. 2. what fonts should I install using texfont.pl? For testing, I have installed the URW fonts using the ber names for the input files and texnansi encoding. I created a Times-Roman-Caps font, but to use it I ended up putting copies of type-syn.tex and type-enc.map in the document directory. In type-enc.tex I added the line(s): \definefontsynonym [Times-Roman-Caps] [\typefaceencoding-utmr8a-capitalized-800] [encoding=\typefaceencoding] and commented out the line: % \definefontsynonym [Times-Roman-Caps] [t1xsc] [encoding=ec] In type-syn.tex I added the line: \definefontsynonym [SerifCaps] [Times-Roman-Caps] inside the "\starttypescript [serif] [times] [name]" block. In retrospect, replacing the ber names with the actual font names (e.g., NimbusRomNo9L-Medi instead of utmb8a) might have been the best approach. Since the font files are stored under directories with the vendor name, the fact that the ber names code for vendor seems redundant. In practice, however, the ber names are used in type-enc.tex. Here is how I installed the URW fonts on a unix system with ksh (note that helvetic might better have been helvetica) with texnansi (the default) encoding: $ awk 'NF==3' /usr/freeware/share/texmf/fontname/urw.map > urw.map $ export d=/usr/people/gwhite/share/ghostscript/fonts $ for f in avantgar courier palatino zapfchan helvetic \ symbol zapfding bookman ncntrsbk times ; do mkdir $f case $f in avantgar) ber=uag ;; [...] esac grep ^$ber urw.map > $d/names.map cd $f # copy the font files (ghostscript names from the 3rd column) # to the installation directory (using ber names from 1st column) awk -v d=$d ' {printf("ln -s %s/%s.afm %s.afm\n", d, $3, $1)}' names.map |sh awk -v d=$d ' {printf("ln -s %s/%s.pfb %s.pfb\n", d, $3, $1)}' names.map |sh # install fonts into $HOME/texmf-fonts texfont --fontroot=$HOME/texmf-fonts --ve=urw \ --co=$(basename $PWD) --ma --in cd - done $ cat avantgar/names.map uagd8a URWGothicL-Demi a010015l uagdo8a URWGothicL-DemiObli a010035l uagk8a URWGothicL-Book a010013l uagko8a URWGothicL-BookObli a010033l I added a Times-Roman-Caps using: $ cd times $ texfont --fontroot=$HOME/texmf-fonts --ve=urw \ --co=$(basename $PWD) --so=. --caps=default utmr8a Next time I may use names from the 2nd column. -- George N. White III Bedford Institute of Oceanography