From: David Wooten <dw@trichotomic.net>
Subject: Font memory issues ?
Date: Tue, 10 Jan 2006 11:07:51 -0800 [thread overview]
Message-ID: <35AB8A55-351B-4B53-81D7-ED26F4652A69@trichotomic.net> (raw)
Greetings ConTeXters,
Just recently (after updating to the most recent i-Installer ConTeXt
version / but also after writing/tweaking a little more), I am
apparently running into some font memory issues.*
I have tried to increase the available memory in web2c/texmf.cnf to
no avail. One curiosity is the pdfTeX error further down: "<argument>
hz,normal". I am using hz,hanging in this document.
Any clues?
Many thanks,
David
*
[27.27]
! Font \*12ptrmtf*=texnansi-LIGA-KERN-ONUM-PNUM-MinionPro-Regular at
12.0pt not
loaded: Not enough room left.
<to be read again>
\relax
\xxdododefinefont ...tspec {#4}\newfontidentifier
\let
\localrelativefontsiz...
\fontstrategy ...ame #1\csname #2#3#4#5\endcsname
\tryingfontfalse \fi
<inserted text> ...yle \fontalternative \fontsize
\fi \iftryingfont
\fontstr...
\synchronizefont ...strategy \the \fontstrategies
\relax \fi
\ifskipfontchar...
<argument> \getvalue {\@style@ \globalfontstyle }
\edef \fontstyle
{\globalfo...
...
l.27 \stopbackmatter
! pdfTeX error (font expansion): invalid font identifier.
\dosetfontadjusting ...pdffontexpand \handledfont
\csname \@fha@
\@fha@ #1\c...
<inserted text> ...ntadjusting \askedfonthandling
\setprotrudingfactor \aske...
\dofastenablehandling ...\everyenablefonthandling
\edef
\fonthandling {\csna...
\rawprocesscommaitem ...commalevel \endcsname {#1}
\expandafter
\rawprocessco...
<argument> hz,n
ormal
\rawprocesscommalist ...er \rawprocesscommaitem #1
,],\global
\advance \comma...
...
l.27 \stopbackmatter
! ==> Fatal error occurred, the output PDF file is not finished!
next reply other threads:[~2006-01-10 19:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 19:07 David Wooten [this message]
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
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=35AB8A55-351B-4B53-81D7-ED26F4652A69@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).