From: David Wooten <dw@trichotomic.net>
Subject: Re: Font memory issues ?
Date: Tue, 17 Jan 2006 13:46:19 -0800 [thread overview]
Message-ID: <F680B022-220B-43A2-AA2D-996AF2F51502@trichotomic.net> (raw)
In-Reply-To: <7A0FD463-98FA-4DB4-AE21-C284EEF5638F@uni-bonn.de>
Thanks Thomas,
I've still no luck, but I think things are quite a bit clearer now.
I "stumbled" across an old fink installation, the existence of which
hadn't crossed my mind for quite some time. That is now gone.
I have also reinstalled my tex/context set-up via the i-Installer
just to clear the air.
Here is what I currently see: there are 3 cnf files that may be
involved:
/usr/local/teTeX/share/texmf.local/web2c/context.cnf
Which declares:
% This file is mostly the same as the one that ships with
% texlive, but adapted for multiple trees as well as
% development in a non tds tree (i.e. hh's machine). This
% file is meant for context users.
%
% This file loads before texmf/web2c/texmf.cnf; beware :
% the selfish auto parent can get in the way especially when
% the binaries are located elsewhere. In case of multiple
% trees, one can best set the following ones manually.
I believe that Hans said this was just an example file (?), but it
has the memory.context settings including:
font_max.context = 2000
font_mem_size.context = 1000000
main_memory.context = 2000000
Second, there is:
/usr/local/teTeX/share/texmf/web2c/texmf.cnf
Which is referred to in the above context.cnf, and which declares:
% original texmf.cnf -- runtime path configuration file for kpathsea.
% (If you change or delete `original' on the previous line, the
% distribution won't install its version over yours.)
% Public domain.
[Stuff skipped]
% Earlier entries (in the same or another file) override later ones,
and
% an environment variable foo overrides any texmf.cnf definition of
foo.
This file also has memory settings, such as:
% ConTeXt is a memory hog...
main_memory.context = 2000000 % Keep total within 8000000 limit
extra_mem_bot.context = 4000000
% Words of font info for TeX (total size of all TFM files,
approximately).
font_mem_size = 2000000
% Total number of fonts. Must be >= 50 and <= 2000 (without tex.ch
changes).
font_max = 2000
And finally,
/usr/local/teTeX/texmf.cnf
Which is identified by
kpsewhich texmf.cnf
and which has no memory settings.
I have tried changing the memory settings in each file (that means
adding them to /usr/local/teTeX/texmf.cnf), raising the main_memory
to 3000000 and the font_mem_size likewise to 3000000, and then
running texexec --make --all. No change in the resulting readout:
Here is how much of TeX's memory you used:
4681 strings out of 60921
74346 string characters out of 610603
4609149 words of memory out of 7114466
40727 multiletter control sequences out of 10000+50000
1927616 words of font info for 332 fonts, out of 2000000 for 2000
232 hyphenation exceptions out of 5000
62i,21n,81p,1198b,1755s stack positions out of 5000i,500n,6000p,
200000b,40000s
PDF statistics:
170 PDF objects out of 300000
0 named destinations out of 131072
109061 words of extra memory for PDF output out of 128383
At this point I would very much like to be embarrassed by a simple,
too-obvious pointer ;)
Thanks very much,
David
On Jan 17, 2006, at 10:31 AM, Thomas A. Schmitz wrote:
> 1. Don't use texconfig for context, use texexec --make --all
>
> 2. If you use texonfig, the command is texconfig-sys, or you'll end
> up having inconsistent files for different users.
>
> Best
>
> Thomas
>
> On Jan 17, 2006, at 6:35 PM, David Wooten wrote:
>
>> Hmm, interesting. I used "texconfig init". No, there seems to be
>> no change if I rename it.
>>
>> Thanks,
>> David
next prev parent reply other threads:[~2006-01-17 21:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 19:07 David Wooten
2006-01-10 19:17 ` Font memory issues ? : bib-module? David Wooten
2006-01-10 20:22 ` Taco Hoekwater
2006-01-10 21:54 ` Font memory issues ? Hans Hagen
2006-01-11 0:39 ` David Wooten
2006-01-11 8:16 ` Hans Hagen
2006-01-11 23:17 ` David Wooten
2006-01-12 7:25 ` Thomas A. Schmitz
2006-01-12 8:28 ` Hans Hagen
2006-01-12 19:04 ` David Wooten
2006-01-12 20:02 ` Taco Hoekwater
2006-01-12 22:49 ` David Wooten
2006-01-13 0:15 ` Taco Hoekwater
2006-01-12 20:05 ` Hans Hagen
2006-01-12 22:48 ` David Wooten
2006-01-16 23:18 ` David Wooten
2006-01-17 10:15 ` Thomas A. Schmitz
2006-01-17 17:35 ` David Wooten
2006-01-17 18:31 ` Thomas A. Schmitz
2006-01-17 21:46 ` David Wooten [this message]
2006-01-17 22:36 ` Hans Hagen
2006-01-17 23:15 ` David Wooten
2006-01-19 19:41 ` David Wooten
2006-01-19 20:16 ` Taco Hoekwater
2006-01-19 20:28 ` Taco Hoekwater
2006-01-19 21:44 ` Hans Hagen
2006-01-19 22:37 ` Taco Hoekwater
2006-01-19 23:47 ` David Wooten
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=F680B022-220B-43A2-AA2D-996AF2F51502@trichotomic.net \
--to=dw@trichotomic.net \
--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).