From: David Wooten <dw@trichotomic.net>
Subject: Re: Font memory issues ? : bib-module?
Date: Tue, 10 Jan 2006 13:13:20 -0800 [thread overview]
Message-ID: <93050b0e99f3462f80fca1bd282eac93@localhost> (raw)
In-Reply-To: 43C41776.4020203@elvenkind.com
Here are the stats, after removing placepublications:
Here is how much of TeX's memory you used:
4760 strings out of 60999
76752 string characters out of 611011
32604822 words of memory out of 34111765
40674 multiletter control sequences out of 10000+50000
1974579 words of font info for 355 fonts, out of 2000000 for 2000
232 hyphenation exceptions out of 5000
62i,21n,81p,1198b,1736s stack positions out of 5000i,500n,6000p,200000b,40000s
PDF statistics:
209 PDF objects out of 300000
0 named destinations out of 131072
115969 words of extra memory for PDF output out of 128383
On Tue, 10 Jan 2006 21:22:14 +0100, Taco Hoekwater <taco@elvenkind.com> wrote:
> David Wooten wrote:
>> Excuse me for replying to myself, but it is also curious that ConTeXt
>> is trying to call a 12pt font. I have called 11pt in the environment.
>>
>> It looks like these errors are appearing at the Bibliography. Might
>> this be due to something in the the beta bib-module?
>
> Not knowingly, but it could be the last drop.
>
> Can remove the placepublications for a test run, and post the tail end
> of the log of that (hopefully succesful) run? The bit that contains
> the statistics, I mean.
>
> Cheers, taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2006-01-10 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 21:13 David Wooten [this message]
2006-01-10 21:53 ` Taco Hoekwater
2006-01-10 22:01 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2006-01-10 19:07 Font memory issues ? David Wooten
2006-01-10 19:17 ` Font memory issues ? : bib-module? David Wooten
2006-01-10 20:22 ` Taco Hoekwater
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=93050b0e99f3462f80fca1bd282eac93@localhost \
--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).