gardener, Interface administrators, Administrators
3,893
edits
Changes
Jump to navigation
Jump to search
→Install the new typescript definition
[[File:result_of_test_with_noto-serif.png]]
= Install the and use your new typescript definition =
You will probably want to use the same customized typescript definition across different documents, so you have to install them in the distribution
;1. Copy the typescript files into Save your file as <texcodecode>tex/texmftype-fonts/(fontname|foundry).tex/context/user/</texcodecode> Installing typescripts consists in the following: 1. Copy the typescript files into either , for example here <texcodecode>tex/texmftype-fonts/mynotoserif.tex/context/user/</texcodecode>. ;2. Run <code>context --generateCopy the typescript files into </code> <texcode>$TEXMF/tex/texmf-fonts/tex/context/user$TEXMF/tex/texmf-project/tex/context/user</texcodecode>2;3. Run <code>context --generate</code> By convention, typescript files are named like <code>type-(fontname|foundry).tex</code>. It may happen that some <code>type-xx.tex</code> typescript file depends on mkiv-specific code located in a matching <code>type-xx.mkiv</code> to update ConTeXt file. In this case, both files need to be installed.database === Loading typescripts === A typescript file named <code>type-xx;4.tex</code> should be loaded using add \usetypescriptfile[type-xx] An alternative way is \usetypefile[xxmynotoserif]where ConTeXt prepends <code>type-</code> when it loads at the beginning of your input file; but <cmd>usetypescriptfile</cmd> is the preferred command because it takes care of the<cmd>starttypescriptcollection</cmd>/<cmd>stoptypescriptcollection</cmd> environments., before \starttext
