Otared Kavian wrote:
It is right that handling fonts is extremely disappointing and instable... For instance, what used to work does not work anymore properly with the new version of ConTeXt I installed two weeks ago...
much of this has nothing to do with context but with - switching from cm to lm (context has done this switch, latex will do that later) - changes in the tds structure (hard to cope with automatically) - changes in map files etc (there will be some more but in the end that mess will be cleaned up so that we don;t have differences in backends any more)
For instance:
\usetypescript [adobekb][\defaultencoding]
this maps kb names and should work if they are present (only when your encoding is ec!)
\setupbodyfont[postscript] \usetypescript[times][\defaultencoding] %or helvetica, or palatino \setupbodyfont[times,12pt]
nothing has changed here
used to work fine, but now it results in ConTeXt creating, the first time, a whole bunch of things regarding fonts, and then the resulting PDF contains some ugly jagging bitmap-looking characters (interestingly this happens only to the text characters, not to the math characters...).
behaviour also depends on your local cont-sys.tex; what happens if you remove that file (or rename it)? it seems that you have a map file problem
Adding \usetypescript[postscript] does not help neither.
Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------