Wolfgang Zillig said this at Mon, 6 Dec 2004 13:40:24 +0100: >Hello, > >I think I´mgetting confused with all of the font selection within context.
Don't worry: it's a bit complicated at first... but it's learn-able (and easier, to my mind, than LaTeX's way of doing things!). >First: I have a miktex environment on on W2K. I don't have miktex. But I'll try to teach what I know! >1. >to change single fonts: >\definetypeface [palatino] [rm] [serif] [palatino] [default] [encoding=ec] >\switchtotypeface[palatino][12pt,rm] >results in an error that the font is not found (font: uplr8t) okay, let's expand through the typescripts a bit: You invoke these typescripts through your typeface definition (primarily; there are others that automatically get triggered): [serif][palatino][name] [serif][palatino][ec] [serif][default] [size] % etc... Serif then gets mapped in type-syn: \starttypescript [serif] [palatino] [name] \definefontsynonym [Serif] [Palatino] %... Palatino then gets mapped in type-enc: \starttypescript [serif] [palatino] [texnansi,ec,8r,t5] \definefontsynonym [Palatino][\typefaceencoding- uplr8a][encoding=\typefaceencoding] %... This line gets expanded to: \definefontsynonym [Palatino][ec-uplr8a][encoding=ec] %... ...So at this point, your system would be looking around for ec- uplr8a.tfm, but it's not. You provide a clue as to why not: >2. >I thought that the default encoding should be texnansi In the new cont-sys.rme, it's set to ec encoding: \setupencoding [\s!default=ec] ...and the berry type synonyms are invoked: \usetypescript [berry] [\defaultencoding] So the following typescript gets invoked, mapping the above ec-uplr8a: \starttypescript [berry] [ec] \definefontsynonym [ec-uplr8a] [uplr8t] [encoding=ec] That, being the last one in the chain, is what ConTeXt looks for. For those following along at home, the whole chain of name resolution, taking into account the encoding, is therefore: (\rm\tf) > Serif > Palatino > ec-uplr8a > uplr8t >on my system following files are available: That's quite a mixture of types, below. Can you provide a listing of the .tfm files in fonts/tfm/urw/palatino ? >uplr8a.afm (The base Adobe Font Metrics file, which enables you to generate new tfms) >uplr8v.tfm >uplr8v.pfb (Vietnamese variants of the fonts!) >uplr8a.pfb (That's the postscript font file you ultimately want to include in your document.) >uplr8v.htf (Irrelevant to our discussion. TeX4ht-related, I think?) >Summary: > >do I need to get the missing fonts/files and why are they not provided >with miktex. >Perhaps a change of the distribution is to prefer? (which one) Well, I'm wondering where all the tfms have gone on my distribution, as well (gwTeX on the Mac doesn't seem to include 8r or ec/8t metrics, either). It looks like you might have to do a texfont run to build (ConTeXt-named) tfms in order to be useful. It's not all that scary. I gave a rundown of the steps I followed in this primitive MyWay. It might be useful so long as you don't treat it as literal instructions: <http://homepage.mac.com/atl/tex/TexfontExamined.pdf> Cheers, adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED] Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _______________________________________________ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
