From: Hans Hagen <pragma@wxs.nl>
Subject: Re: no more nullfont errors in latest beta!
Date: Thu, 06 Mar 2003 09:56:16 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20030306095354.024673e0@server-1> (raw)
In-Reply-To: <87of4p5sjp.fsf_-_@gundla.ch>
At 11:59 PM 3/5/2003 +0100, you wrote:
>Just to make sure I have got a good cont-tmf.zip I have downloaded it
>again. And see: this is the beta 2003.3.4 (one day later). And this
>beta does not have the problems I described :))
>
>the files that changed meanwhile were:
>
> 120 -rw-r--r-- 1 softinst 118402 Mar 3 12:58 syst-ext.tex
> 24 -rw-r--r-- 1 softinst 23565 Mar 3 18:02 core-box.tex
> 20 -rw-r--r-- 1 softinst 19801 Mar 3 21:00 page-bck.tex
> 8 -rw-r--r-- 1 softinst 6806 Mar 3 21:31 meta-pag.tex
> 40 -rw-r--r-- 1 softinst 39796 Mar 3 23:19 supp-mpe.tex
> 12 -rw-r--r-- 1 softinst 9190 Mar 4 09:32 s-mag-01.tex
> 16 -rw-r--r-- 1 softinst 14233 Mar 4 10:44 context.tex
>
>I had a look at the differences between these files and the ones
>from 2003.3.3, but could not find any harmful macros ;-) Perhaps you
>know, but it is no problem anymore.
this is why i think that something went wrong in the unzipper or during
transfer (i once had such a problem)
>BTW: the "ConTeXt Beta Page" is lying a little bit about the beta
>version (context version and filesize). The ConTeXt link from the
>"Downloading" page is pointing to an old version.
i know, some day i will automatically upload the lot, now i do that
manually (although the html page and show-fil file are generated
automatically, i sometimes forget to upload them)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-03-06 8:56 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 ` nullfont errors in new beta Patrick Gundlach
2003-03-05 16:33 ` 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 [this message]
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=5.1.0.14.1.20030306095354.024673e0@server-1 \
--to=pragma@wxs.nl \
--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).