66
edits
Changes
Jump to navigation
Jump to search
Context Mark IV can use non-tex fonts (in OpenType, TrueType or Type1 format) directly. The first time that you run context myfile.tex on a file that uses such non-traditional fonts (which is probably always), the actual fonts themselves have to be loaded See [[Fonts in luatex's embedded section of fontforge to extract their metric information. This removes the need for tfm and vf files on your disk, but it is also a somewhat lengthy and often memory-hungry process. That is why the results of that internal preprocessing are also saved inside the texmf cache. Future runs using the same font (not just this file, but all files using that particular font) can then use the cached version of the metrics instead. === Font name database === Because Luatex does not know about the names of fonts all by itself, Mark IV uses a database of 'known font names'to allow you to specify fonts by their internal name instead of the name of the disk file. The mtxrun script named'fonts' maintains this database. At any time, you can run mtxrun --script fonts --list LuaTex#Getting access to get the list of currently known fonts. mtxrun --script fonts --help will show some other options. Previously, mtxrun --script fonts --reload was always needed if you wanted to use new system fonts by their font name (as opposed to their file names). In the latest beta (July 2008) versions of Mark IV this is no longer the case. In these new versions, the reload command is run automatically whenever a named font cannot be found. Nowadays, you only have to do the reload manually when you have installed updates to already installed fonts that cause the font and/or file names to change. This normally only happens for fonts that are still in development like [[TeX Gyre]] and [[Latin Modern]].
→Using fonts: Contents moved to a dedicated page
== Using fonts ==
== Downloaded files ==
