From: Taco Hoekwater <taco@elvenkind.com>
Cc: tex-k@tug.org
Subject: Re: Font memory issues ?
Date: Thu, 19 Jan 2006 23:37:26 +0100 [thread overview]
Message-ID: <43D014A6.8030901@elvenkind.com> (raw)
In-Reply-To: <43D0082D.50103@wxs.nl>
Hans Hagen wrote:
> Taco Hoekwater wrote:
>
>> Oh, d**mn.
>> I just had a brainwave.
>>
>> From Web2c's tex.ch comes the following:
>>
>> @!inf_font_mem_size = 20000;
>> @!sup_font_mem_size = 2000000;
>>
>> So font_memory cannot be set larger than 2000000 and not smaller
>> than 20000. Out-of-bounds sizes are silently folded back in line,
>> but that happens after the variable expansion is complete. That's
>> why the debug switch still reports the values from texmf.cnf.
>>
>> So the actual problem here is the web2c runtime code inside TeX.
>>
>> You can recompile with a larger sup_font_mem_size, I guess. But
>> otherwise you are out of luck.
>
> so, is it possible to increase the upper limit in the code?
I guess so. I don't see any special reason for 2mln upper limit.
font mem pointers are integers with rather straightforward usage,
AFAIK.
(CC to the tex-k list)
Cheers, taco
next prev parent reply other threads:[~2006-01-19 22:37 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
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 [this message]
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=43D014A6.8030901@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
--cc=tex-k@tug.org \
/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).