Ville Voipio wrote:
However, the magic row with "adobekb" is present in almost all examples
I've seen. And yet very few people have the real Adobe fonts. So,
possibly this should be noted somewhere.
The problem *should* go away after the next update of the context
distribution. (I have no p
Try the next two lines instead of those three lines:
\usetypescript[postscript][\defaultencoding]
\setupbodyfont[postscript,11pt]
Thank you, thank you, thank you!
The problem was not the difference between pos and postscript (they seem
to be synonyms, both work) but the magic row:
\
Ville Voipio wrote:
A font problem -- again. I am so sorry.
I try to use the URW postscript fonts with the stand-alone
mswincontext.zip distribution. Everything else seems to work fine, but
when I say:
\usetypescript[adobekb][\defaultencoding]
\usetypescript[pos][\defaultencoding]
\set
A font problem -- again. I am so sorry.
I try to use the URW postscript fonts with the stand-alone
mswincontext.zip distribution. Everything else seems to work fine, but
when I say:
\usetypescript[adobekb][\defaultencoding]
\usetypescript[pos][\defaultencoding]
\setupbodyfont[pos,11pt]
