From: Patrick Gundlach <pg@levana.de>
Subject: nullfont errors in new beta
Date: Wed, 05 Mar 2003 16:05:19 +0100 [thread overview]
Message-ID: <87heahn9ao.fsf_-_@gundla.ch> (raw)
In-Reply-To: <5.1.0.14.1.20030305102338.034451c0@server-1> (Hans Hagen's message of "Wed, 05 Mar 2003 10:25:13 +0100")
Hans Hagen <pragma@wxs.nl> writes:
> this is strange, it looks like something is wrong with your
> (preloaded) cmr fonts; how do the formats compare (format logs)
besides the version number and the line numbers from the etex
messages:
(I have substituted the version numbers with -- and the linenumbers
with (linenumber) to make the output of the diff shorter). I cannot
see any harmful messages.
1c1
< This is pdfeTeX, Version 3.14159-1.00b-pretest-20020211-2.1 (Web2C 7.3.7x) (INITEX) 4 MAR 2003 23:40
---
> This is pdfeTeX, Version 3.14159-1.00b-pretest-20020211-2.1 (Web2C 7.3.7x) (INITEX) 4 MAR 2003 23:38
125d124
< system (E-TEX) : [line (linenumber)] \ifcsname
457c456
< loading : Context Core Macros / Numbering
---
> loading : Context Core Macros (Numbering)
463,467c462,465
< loading : Context Page Macros / Backgrounds
< ) (/opt/context/--/texmf/tex/context/base/page-app.tex
< loading : Context Page Macros / Applications
< ) (/opt/context/--/texmf/tex/context/base/core-job.tex
< loading : Context Core Macros / Job Handling
---
> loading : Context Page Macros (Backgrounds)
> ) (/opt/context/--/texmf/tex/context/base/page-app.tex)
> (/opt/context/--/texmf/tex/context/base/core-job.tex
> loading : Context Core Macros (Job Handling)
692,694c690,692
< 32021 strings of total length 501741
< 385365 memory locations dumped; current usage is 113&384373
< 29986 multiletter control sequences
---
> 31931 strings of total length 500730
> 384296 memory locations dumped; current usage is 113&383598
> 29896 multiletter control sequences
Patrick
next prev parent reply other threads:[~2003-03-05 15:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 22:17 Columns in itemizations Giuseppe Bilotta
2003-02-28 8:01 ` Hans Hagen
2003-02-28 9:23 ` Re[2]: " Giuseppe Bilotta
2003-03-03 9:21 ` Hans Hagen
2003-03-03 15:24 ` Re[3]: " Giuseppe Bilotta
2003-03-03 16:50 ` Patrick Gundlach
2003-03-03 18:23 ` Giuseppe Bilotta
2003-03-03 21:02 ` Patrick Gundlach
2003-03-03 21:21 ` Giuseppe Bilotta
2003-03-04 10:39 ` Patrick Gundlach
2003-03-04 14:42 ` Giuseppe Bilotta
2003-03-04 20:42 ` Hans Hagen
2003-03-04 22:52 ` Patrick Gundlach
2003-03-05 8:27 ` Patrick Gundlach
2003-03-05 9:21 ` Hans Hagen
2003-03-05 8:43 ` Patrick Gundlach
2003-03-05 9:25 ` Hans Hagen
2003-03-05 15:05 ` Patrick Gundlach [this message]
2003-03-05 16:33 ` nullfont errors in new beta Hans Hagen
2003-03-05 20:41 ` Patrick Gundlach
2003-03-05 21:50 ` Hans Hagen
2003-03-05 22:59 ` no more nullfont errors in latest beta! Patrick Gundlach
2003-03-06 8:56 ` Hans Hagen
2003-03-05 23:55 ` Re: nullfont errors in new beta Jens-Uwe Morawski
2003-03-05 22:35 ` Giuseppe Bilotta
2003-03-03 20:16 ` Columns in itemizations Hans Hagen
2003-03-04 10:43 ` Patrick Gundlach
2003-03-04 14:43 ` Giuseppe Bilotta
2003-03-04 15:11 ` Willi Egger
2003-03-04 15:55 ` Patrick Gundlach
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=87heahn9ao.fsf_-_@gundla.ch \
--to=pg@levana.de \
--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).