-- Nigel
> All definitions in type-* are based on the more extended naming of fonts, > i.e. the -encoding scheme; now, on my machine (with map loading enabled) i > can say: I assume you mean \autoloadmapfilestrue > > \definetypeface[charter] [rm][serif][charter] [default][encoding=texnansi] > \definetypeface[utopia] [rm][serif][utopia] [default][encoding=texnansi] > \definetypeface[bookman] [rm][serif][bookman] [default][encoding=texnansi] > \definetypeface[palatino][rm][serif][palatino][default][encoding=texnansi] > > \starttext > \switchtobodyfont[ 10pt] \input tufte \par > \switchtobodyfont[charter, 10pt] \input tufte \par > \switchtobodyfont[utopia, 10pt] \input tufte \par > \switchtobodyfont[bookman, 10pt] \input tufte \par > \switchtobodyfont[palatino,10pt] \input tufte \par > \stoptext All but charter worked for me, I don't think I have run texfont on charter. We ought to be able to use the Acrobat 14 embedded fonts shouldn't we. Helvetica, times, courier, etc. You wouldn't happen to have wonderful example lines would you? I have been fighting this as well. What I am guessing that the above lets us do is to grow into the delights of fontsynonyms later. > > So, the free fonts on tex live (there are some more defined) are already > available! > > If you want, i can send you a zip with the texmf-fonts tree (as generated > by texfont) that is needed for this. > > If you want berry names, you can start your file with > > \usetypescript[berry][texnansi] > > or [ec] if you've used encoding=ec > I think this is one of the complexities that new starters have trouble with. I am sure the statement is true but what us less expert people need is the consistent simple place to start and then move on when we have to. Nigel King
