Installation of modules ======================= Basics –––––– The installation of extra files in TeX (called modules in ConTeXt) can be hard for people how are new in TeX or aren't interested in TeX programming themselve. According to the TDS (TeX directory structure) and the ConTeXt developers user written files reside under the path $TEXMF/tex/context/third/<modulename>/<files> in the private TeX directory ($TEXMF), private directories can have the names • texmf-local • texmf-extra • texmf-project but there existence depend on the TeX distribution and texmf-local is the most common one. Installation by hand –––––––––––––––––––– When you want to install a new module which is available as file only create the subdirectories in the way described above and place the file there, for modules which are available as zip files with precreated subdorectories you can unzip the archive in the top-level directory (e.g. texmf-local/) and all files are on the correct place. After the files are placed at the right place you have to update TeX's database to let it know where it can find the files, this is done for MkII with mktexlsr (command name depends on the TeX distribution) and for MkIV with context --generate ConTeXt minimals –––––––––––––––– Users of the ConTeXt minimals dont't have to download the module files and unzip them in the local directory because they can use the 'first-setup' for this. To install for example the simpleslides modules you write first-setup.sh --extras="t-simpleslides" To install more modules at the same time write first-setup.sh --extras="t-simpleslides,t-french" The complete list of availables modules in minimals is: • f-urwgaramond • f-urwgothic • t-account • t-algorithmic • t-bib • t-bnf • t-chromato • t-cmscbf • t-cmttbf • t-construction-plan • t-degrade • t-fixme • t-french • t-games • t-gnuplot • t-layout • t-letter • t-lettrine • t-lilypond • t-mathsets • t-simplefonts • t-simpleslides • t-taspresent • t-tikz • t-typearea • t-typescripts • t-vim TeX Live –––––––– # description required The following modules are available: • context-account • context-bnf • context-chromato • context-construction-plan • context-degrade • context-french • context-games • context-gnuplot • context-letter • context-lettrine • context-lilypond • context-mathsets • context-simpleslides • context-taspresent • context-typearea • context-vim
Wolfgang Schuster wrote:
in the private TeX directory ($TEXMF), private directories can have the names
• texmf-local • texmf-extra • texmf-project
but there existence depend on the TeX distribution and texmf-local is the most common one.
also texmf-fonts (for shared commercial fonts) at bachotek we discussed this with norbert and he will try to get the texmf-fonts and texmf-project trees in the standard texmf.cnf setup another issue discussed was texmx*/fonts/data/* as path for installing fonts as they are shipped (packaged) by vendors - makes sense now that we move towards all-opentype ----------------------------------------------------------------- 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 -----------------------------------------------------------------
Am 03.07.2009 um 21:18 schrieb Hans Hagen:
Wolfgang Schuster wrote:
in the private TeX directory ($TEXMF), private directories can have the names • texmf-local • texmf-extra • texmf-project but there existence depend on the TeX distribution and texmf-local is the most common one.
also texmf-fonts (for shared commercial fonts)
The guide was for modules only and there are not so many which needs fonts to work, for fonts separate instructions are better when you want to mention also type 1 fonts, tfm and map files etc. Wolfgang
Wolfgang Schuster wrote:
Am 03.07.2009 um 21:18 schrieb Hans Hagen:
Wolfgang Schuster wrote:
in the private TeX directory ($TEXMF), private directories can have the names • texmf-local • texmf-extra • texmf-project but there existence depend on the TeX distribution and texmf-local is the most common one.
also texmf-fonts (for shared commercial fonts)
The guide was for modules only and there are not so many which needs fonts to work, for fonts separate instructions are better when you want to mention also type 1 fonts, tfm and map files etc.
ok, but in mkiv type1's use afm/pfb only, no more map and tfm (the type1 is turned into wide font internally so one has all chars) Hans ----------------------------------------------------------------- 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 -----------------------------------------------------------------
ok, but in mkiv type1's use afm/pfb only, no more map and tfm (the type1 is turned into wide font internally so one has all chars)
Is it possible the reverse runtime ? I mean, given an opentype that wrap a type1-like font and given an encoding, make a pdf with that type1 font and encoding -- luigi
luigi scarso wrote:
ok, but in mkiv type1's use afm/pfb only, no more map and tfm (the type1 is turned into wide font internally so one has all chars)
Is it possible the reverse runtime ? I mean, given an opentype that wrap a type1-like font and given an encoding,
make a pdf with that type1 font and encoding
i'm not sure what you mean but you can force types by adding .tfm or .afm etc (more low level control os possible but not adviced) anyhow, encodings make no sense any more, so when readign a type 1 i read the amf file and remap to unicode ... the luatex backend itself will create subfonts when the number of used chars is > 256 Hans ----------------------------------------------------------------- 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 -----------------------------------------------------------------
participants (3)
-
Hans Hagen
-
luigi scarso
-
Wolfgang Schuster