afsmith wrote:
Hi ntg-context.
I'm very confused about accomplishing something that to me seems as though it should be quite simple, but has proven for weeks of occasional attempts to be very confusing. I'm finding existing information from the contextgarden wiki and ntg-context archives to be very newbie-unfriendly and inconsistent. I'm compelled to improve the wiki, if only I could comprehend what I would be documenting.
What I would like to do is use the full range of TeX-Gyre fonts (and later possibly others) for my existing documents. It is not clear to me... Whether or not I am using MKIV, nor how to determine which engine I am running. If not running MKIV/XeTeX, how to determine which fonts are installed. What the items from the output of "fc-list" or "mtxrun --script fonts --list" correspond to. How to use available fonts, nor where to draw valid parameters from for use in font commands. How to determine what font configurations are available for a given font. Whether I need to write typescripts, nor how to find any existing ones. Whether I need to concern myself with .map or any other font files. Whether I need to configure anything, move any files, etcetera. ....As well as anything else I might need to install or use a font
For what it's worth, I have been using the command "texexec" to process my tex files, am using a context minimals downloaded about two months ago, and am running Linux.
it depends on you language ... the main complication with fonts is that in traditional tex there are only 256 slots in a font available also, fonts relate to hyphenation another complication is that traditional tex fonts come in design sizes and yet another one is that we have math and also in traditional tex fonts it vs sl so, this is why a traditional tex font system is somewhat complex because it operates on several exis now, for english you can ignore encoding issues but not for other languages using the gyre fonts is not that complex as one of the objectives of the project is to provide consistent sets of fonts \usetypescript[palatino][ec] % pdftex, one needs to choose an encoding \usetypescript[palatino] % luatex, no encoding since unicode and then \setupbodyfont[palatino] should for instance give you palatino things like open type features etc etc demand some more knowledge as fonts differ considerably in this areas as well as can contain bugs or inconsistencies if you ever have to use commercial fonts .. be prepared ... an even bigger mess is awaiting you since naming of files and fonts is often quite strange ----------------------------------------------------------------- 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 -----------------------------------------------------------------