Changes

Context ConTeXt [[Mark IV]] does not use the kpathsea library to find files and configuration settings. It follows that running [[mktexlsr]] or [[fmtutil]] has no effect. This page explains the details of installing setting up and maintaining [[Mark IV]].

luatools In TeX Live 2011, not even that is needed and you only have to run `mtxrun --generate` when files are installed manually ''outside'' of tlmgr. If you are running tl 2011, this page is just background information, there should be no need to take actual actions.

is * '''Debian''': Mark IV suggests the replacement for tex-gyre package ([[fmtutilTeX Gyre]]), not distributed currently under Debian due to licensing issues (see [[Debian installation]] )

=== Introduction =Quickstart ==

When If you runhave trouble following these instructions, please direct you questions or complaints on the [http://www.ntg.nl/mailman/listinfo/ntg-context ntg-context mailing list], '''not''' the tex-live list.

both the script 'context' luatools --generate # 2010 and the Mark IV code inside the format have to find various files. To make this happen as fast as possible, a file name database is used. There is also some configuration information and some generated font data is cached because extracting the OpenType information is a relatively lengthy and memoryearlieror mtxrun --consuming process.generate # 2011

All of this data stored inside is the 'texmf cache'Mark IV replacement for mktexlsr. To keep this cache up to date, you have to (re)run

luatools context --generatemake

whenever you install or remove files from your tex installation that have to be found by is the Mark IV, like after updating context itself, or installing extra font packages from [[TeX Live]] or [[CTAN]]replacement for fmtutil. System-wide fonts don't count, these are always re-discovered at runtime. {{todo| check that}}

is run, it creates '''A note for windows users: (tl2008/2009)''' the file luatex executable does not accept filenames with spaces in their name database. To prevent duplication of settings This means that if you are on windows you will at least have to set up a texmfcnf.lua as much as possibleexplained below, and you likely will even have to reinstall texlive, it parses because the default texlive installation directory itself contains spaces. [[texmf.cnfRunning_Mark_IV#File_not_found | Details]] as the source for discovering at what directory trees need to be indexed in the database. This ensures that while Mark IV does not actually use kpathsea, it is still compatible with how kpathsea handles things.

Before first use and after each update to either the [[context]] distribution or the [[luatex]] executable you will have to regenerate the formats. The internal logic used manual command for finding the cache location that is as follows:

For completenessStarting with 2011, formats are automatically (re)generated by `context myfile.tex` when it believes it is necessary to do so. Specifically: assuming the format already exists, automatic regeneration takes places whenever the ConTeXt version of the list luatex version do not match the ones in the pre-existing format. Manual patches of tested environment variables is currently:the core files still require manual regeneration of the formats.

=== texmfcnfIn addition to standard [[luatex]] we provide [[luajittex]] which uses just in time compilation to speed up processing.The speedup is mostly due to the faster virtual machine. The exact speedup depends on the tex/lua ===ratio and we measured speedups between 10% and 40%. You force this engine with

Files named texmfcnf context --jit .lua can appear anywhere on the search path where there can also be a [[texmf.cnf]] present. Multiple files can be present. They are read sequentially using the same logic as for [[texmf.ncf]]: earlier files fix values that cannot be overruled by later ones. All texmfcnf.lua files are read before all texmf.cnf files, and values defined in texmfcnf.lua cannot be overruled by texmf.cnf files.

return { TEXMFCACHE = '$HOME/on top of your main document source.texlive2008/texmf-var' }

Note: Windows users should replace $HOME with $USERPROFILE. Both unix and windows users of [[TeX Live]] 2008 and users of Mark IV beta's released after Jul 10, 2008 can use ~ instead. == Generating and updating formats Using fonts == Before first use and after each update to either the [[context]] distribution or the [[luatex]] executable you will have to regenerate the formats. The command for that is:  context --make cont-en

This will generate a new Mark IV format with The <code>OSFONTDIR</code> environment variable should contain the English interface. Without an explicit format argument, it will generate four formats: Mark IV cont-en, Matk IV cont-nl, luatex+mptopdf, and luatex+plainpaths where the system fonts must be looked for.

The generated formats are stored inside See [[Fonts in LuaTex#Getting access to the texmf cache.system fonts]]

== Using fonts Downloaded files ==

Context Mark IV If you have the program 'curl' installed, then your input file can use non-tex fonts (in OpenType, TrueType or Type1 format) directlycontain e. The first time that you run   context myfileg.tex

on a file that uses such non<texcode>\externalfigure [http://www.pragma-traditional fonts (which is probably always), the actual fonts themselves have to be loaded in luatex's embedded section of fontforge to extract their metric informationade. This removes the need for tfm and vf files on your disk, but it is also a somewhat lengthy and often memorycom/show-hungry processgra. pdf]</texcode>

That is why and the results of that internal preprocessing are also saved inside referenced file will be downloaded automatically and placed in the 'texmf cache. Future runs using the same font (' if is not just this file, but all files using that particular font) can then use found in the cached version of the metrics insteadcache already.

=== Font name database =In case of trouble ==

Because Luatex does === File 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 runfound (TL 2008/2009) ===

* You may get errors like mtxrun --script fonts --listI can't find file `C:/Program.tex'.This is likely caused by the luatex executable not handling filename quoting properly yet. If filenames with spaces work at all, you are just lucky.

This problem is most likely to get happen on Windows. There two steps to deal with it:* You must put the main texmf tree in path without spaces. If you're installing Mark IV via TeXLive 2008, then simply change the top installation path at install time.* If you're running XP or Server 2003 (and not Vista or Server 2008), you must also set the TeX user home and the Lua cache to paths without spaces. <code>C:/tlhome</code> is a good candidate.** In <code>texmf.cnf</code> set TEXMFHOME to <code>C:/tlhome/$USERNAME</code> or to something similar of your liking. Using $USERNAME in the path will still give a per-user directory, just not under "Documents and Settings". This assumes that the list user name doesn't have spaces of currently known fontscourse...** As mentioned above, create/edit <code>texmfcnf.lua</code> and put a line like <code>return { TEXMFCACHE = 'C:/tlhome/$USERNAME/.texlive2008/texmf-var' }</code>, which sets each user's cache inside his space-free TeX home path.

PreviouslyIf you look at the folder that TEXMFCACHE points to,you will see a folder named luatex-cache. Inside that, there is the folder context. Inside the context folder, there usually is a single subfolder with a hexadecimal name. This is the md5sum of the name of the 'tex root' location (to be precise, it is the md5sum of the full path expansion of the context lua equivalent of the TEXMFCNF variable).

was always needed if you wanted * '''curl''' contains downloaded files. The url is converted to use new something that can be represented on disk by replacing problematic characters by dashes* '''fonts by their ''' contains the file data/names.tma, this is the 'font name database' (as opposed to their and the derived names.tmc, tmc files are byte-compiled lua code for faster loading). There are also subdirectories containing the preprocessed metrics for non-tex fonts, one folder for each font type. * '''formats''' contains the Mark IV format file * '''trees''' has a small set of files with hexadecimal names, one for each of the top-level constituents of TEXMF (containing the filename database for that tree), and one for each of the found texmf.cnf files (containing in preprocessed form all the variables defined by that file). The filenames are md5sums of the contained directory or filename.

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 GyreCategory:Installation]] and [[Latin Modern]].