From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Generating smallest possible format file
Date: Mon, 09 Jan 2006 12:28:05 +0100 [thread overview]
Message-ID: <43C248C5.2090107@elvenkind.com> (raw)
In-Reply-To: <43BFDFC6.9050903@boede.nl>
Hi Willi,
Willi Egger wrote:
> Hello gurus!
>
> I want to use context as a backend-typesetting engine in a
> server-ennvironment. In order to minimize compilation time I want to
> make the format files as small as
> possible. E.g. I would like to remove all pattern files which are
> unnecessary for the purpose of the application.
That is as simple as commenting (some of) the \installlanguage
calls in the cont-XX.tex file you want to use (and don't use
the --all switch of texexec!).
Removing some of the other files can be a bit harder and require
editing core include files:
* font encodings are loaded in enco-ini.tex
\useencoding[ans,il2,ec,tbo,pdf,uc,pol,qx,t5,cyr]
* regimes are loaded in regi-ini:
\useregime[def,uni,lat,win,il1,mac]
* unicode tables are loaded in unic-ini:
\useunicodevector[0,1,2,3,4,5,30,32,33,34,39]
It would be easier if these could be moved to the cont-XX.tex
(or perhaps context.tex) file in a future release.
Also, you can gain some speed by
* dropping the memory array settings in texmf.cnf to as low as you
can get away with, based on your typical input files;
* and by pruning your texmf tree(s) of as many files as possible
(every file and directory in the tree slows down kpathsea
initialization just a little bit, and it can add up to a
noticeable delay).
* disabling kpathsea disk searches
Cheers, Taco
next prev parent reply other threads:[~2006-01-09 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 15:35 Willi Egger
2006-01-09 11:28 ` Taco Hoekwater [this message]
2006-01-09 12:23 ` Willi Egger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C248C5.2090107@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).