From: David Wooten <dw@trichotomic.net>
Subject: Re: Font memory issues ?
Date: Thu, 12 Jan 2006 11:04:11 -0800 [thread overview]
Message-ID: <CFB5CB4B-E3D3-4820-8D4B-CE86EFDACC46@trichotomic.net> (raw)
In-Reply-To: <43C61319.3000104@wxs.nl>
On Jan 11, 2006, at 11:25 PM, Thomas A. Schmitz wrote:
> Find out which is the main texmf.cnf file:
>
> kpsewhich texmf.cnf
>
> on my system, this resolves to
>
> /usr/local/teTeX/texmf.cnf
>
> Then modify this file and regenerate the formats.
>
> HTH
>
> Thomas
Indeed, that is the case also for me.
> maybe you have duplicate formats (texconfig does not support engine
> paths)
>
> do the reported mem values change?
>
> Hans
The reported values do not change, and afaik the formats are all
listed here:
> locate .fmt
/usr/local/teTeX/share/texmf.local/web2c/amstex.fmt
/usr/local/teTeX/share/texmf.local/web2c/cont-en.fmt
/usr/local/teTeX/share/texmf.local/web2c/cont-nl.fmt
/usr/local/teTeX/share/texmf.local/web2c/eplain.fmt
/usr/local/teTeX/share/texmf.local/web2c/etex.fmt
/usr/local/teTeX/share/texmf.local/web2c/jadetex.fmt
/usr/local/teTeX/share/texmf.local/web2c/latex.fmt
/usr/local/teTeX/share/texmf.local/web2c/mptopdf.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdfetex/cont-en.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdfetex/cont-nl.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdfetex/mptopdf.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdfetex.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdfjadetex.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdflatex.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdftex.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdftexinfo.fmt
/usr/local/teTeX/share/texmf.local/web2c/pdfxmltex.fmt
/usr/local/teTeX/share/texmf.local/web2c/tex.fmt
/usr/local/teTeX/share/texmf.local/web2c/texinfo.fmt
/usr/local/teTeX/share/texmf.local/web2c/xmltex.fmt
next prev parent reply other threads:[~2006-01-12 19:04 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 [this message]
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=CFB5CB4B-E3D3-4820-8D4B-CE86EFDACC46@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).