ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: David Wooten <dw@trichotomic.net>
Subject: Re: Font memory issues ?
Date: Tue, 10 Jan 2006 16:39:29 -0800	[thread overview]
Message-ID: <95E5C116-BA8D-42CC-A101-1B83BFEFD35B@trichotomic.net> (raw)
In-Reply-To: <43C42D12.7020309@wxs.nl>


On Jan 10, 2006, at 1:54 PM, Hans Hagen wrote:

> did you remake the format after increasing the memory values?

This means texexec --make --all ?

I did try the above, but the  numbers in the log when running my file  
do not change. I can only imagine that there is another place to  
change the memory settings. In my context.cnf, the numbers are  
identical to yours below, although I did try to raise the  
font.mem.size.context as we've been discussing.

> hz lets pdftex internally generate additional font instances
>
> these are my texmf.cnf values
>
> buf_size.context         =  200000 % needed for omega bug
> extra_mem_bot.context    = 2000000
> extra_mem_top.context    = 4000000
> font_max.context         =    2000
> font_mem_size.context    = 1000000
> hash_extra.context       =   75000
> main_memory.context      = 2000000
> max_strings.context      =  250000
> nest_size.context        =     500
> obj_tab_size.context     =  300000 % 8388607
> pdf_mem_size.context     =  500000 % 524288
> dest_names_size.context  =  300000 % 131072
> param_size.context       =   10000
> pool_free.context        =   47500
> pool_size.context        = 2000000
> save_size.context        =   50000
> stack_size.context       =   10000
> string_vacancies.context =  125000
> trie_size.context        =  250000
> hyph_size.context        =    8191 % prime
>
> (texmfstart --bin youreditor kpse:texmf.cnf)
>
> Hans

  reply	other threads:[~2006-01-11  0:39 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 [this message]
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
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=95E5C116-BA8D-42CC-A101-1B83BFEFD35B@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).