Re: latest context problems

[Hans Hagen <pragma@wxs.nl>]

At 12:00 PM 11/16/2001 -0400, George N. White III wrote:

>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?

I hope that this will become better when pdftex can load map files at each 
page.

\setupencoding [\s!default=texnansi]

\autoloadmapfilestrue
\preloadmapfile [original-ams-cmr]
\preloadmapfile [original-ams-euler]
\preloadmapfile [original-ams-logo]
\preloadmapfile [il2-ams-cmr]
\preloadmapfile [pl0-ams-cmr]
\usesymbols [nav,mvs] % [eur]

\setupsymbolset [navigation 1]

\setupinteraction [\c!symboolset=navigation 1]

Then, my map file looks like:

map              psclean.map

and this file has no full names and looks like psfonts.map :

Math1 <math1.pfb
Math1-bold <math1-bold.pfb
.....

[ps. I embed all fonts, also times cum suis]

one needs at least one entry in the cfg file, otherwise (alas) pdftex loads 
psfont.map

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

in that case you may consider dedicated pdftex.cfg files for context and 
latex (you need to edit the texmf.cnf file for that)

>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]

here i use texnansi, so

   texfont cont-tmf.dat --enc=texnansi

and a dedicated font path texmf-fonts [i hope that this will be defined in 
texmf.cnf in the future] but i may need to bribe the tex live gurus for that.

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

ok, now that we have this mechanism in place, we can upgrade the typescripts.

Also, a better way for overloading is to have new ones, like 
"mytypescripts.tex" on tex/context/user
and register that one by \usetypescriptfile[mytypescripts] in you 
cont-sys.tex file; for projects, here we put a file typeface.tex in each 
project path.

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

I have considered that but don't know enough of those names -) when we have 
a good working system, we may convince fabrice and sebastian ....

>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:

Maybe you should communicate this with Patrick, since he wants to make some 
font tools

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