3,899
edits
Changes
Jump to navigation
Jump to search
m
<{{cmd>|usetypescriptfile</cmd> }} loads a given file ([[source:type-gyr.tex|type-gyr.tex]] in this case). This file usually contains definitions of ''typescripts''. The core typescript files (such as [[source:type-tmf.tex|type-tmf.tex]], [[source:type-one.tex|type-one.tex]] in pdTeX or [[source:type-otf.tex|type-otf.tex]] in LuaTeX/XeTeX, ...) are already preloaded, so you would usually need this only to load your own definitions. <code>\usetypescriptfile[type-gyr]</code> will soon become obsolete (TeX Gyre will be the default).
<{{cmd>|usetypescript</cmd> }} kind of "selects" (?) the specified typescript from that file. It takes up to three parametres and their rôles are still cryptic to me...
Understanding how fonts work in ConTeXt - Old Content (view source)
Revision as of 13:18, 9 August 2020
, 13:18, 9 August 2020Text replacement - "<cmd>" to "{{cmd|"
* http://context.aanhet.net/svn/contextman/context-reference/en/co-fonts.pdf - Chapter on fonts
* [[Old: A Beginner's Guide to Using Fonts in Mark IV]]. The idea is that the page says ''how'' to easily use fonts (or rather typescripts) in Mark IV, so that you just take a ready-to-use recipe from there and paste it into your document.
Most of the following material comes from the answers I got on the mailing list and/or the documentation (mfonts.pdf). Since crediting people for each and every answer would be cumbersome, I'd like to thank here all of you that helped me understand ConTeXt (especially Hans, of course).
</context>
== Defining typescripts ==
One of the keys for defining typescripts is clever usage of the <{{cmd>|definefontsynonym</cmd> }} command. It takes 2 or three parameters. Example from mfonts.pdf:
<texcode>\definefontsynonym[Serif][Times-Roman]
\definefontsynonym[Times-Roman][tir][encoding=texnansi]</texcode>
The second one makes <code>Times-Roman</code> an "alias" (?) for font stored in the file called <code>tir</code> (probably with some extension?). The third argument specifies the encoding (it might be qx, for instance, or something else) and possibly another options, like <code>features=smallcaps</code> (for opentype fonts). Encoding is used by pdfTeX only - XeTeX and LuaTeX both use Unicode (Mojca - thanks for this point!). Other possibilities include <code>mapping</code> and <code>handling</code>, but don't ask me about these;).
[[Category:Old Content]]
