Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:

> If seems that you do not have the wasy fonts installed, or that MikTeX
> cannot find them.

I did have the fonts properly installed. This definitely seems
to be a MiKTeX bug though, it looks like the METAFONT conversion 
executable stopped working in the latest MiKTeX update (I
didn't seem to have this problem before July since I had some
old tfm files dated before July in my local texmf tree):

This is e-TeX, Version 3.141592-2.2 (MiKTeX 2.4)
entering extended mode
(wasytest.tex
LaTeX2e <2003/12/01>
Babel <v3.8g> and hyphenation patterns for english, french, german, ngerman, se
rbocroat, ukenglish, dumylang, nohyphenation, loaded.
(D:\texmf\tex\latex\base\article.cls
Document Class: article 2004/02/16 v1.4f Standard LaTeX document class
(D:\texmf\tex\latex\base\size10.clo)) (D:\texmf\tex\latex\wasysym\wasysym.sty)
(wasytest.aux) (D:\texmf\tex\latex\wasysym\uwasy.fd)Making "wasy10.tfm" from "D:
\texmf\fonts\source\public\wasy2\wasy10.mf"...
"mf" \mode:=cx;nonstopmode;input wasy10
This is METAFONT, Version 2.71828 (MiKTeX 2.4)

(D:\texmf\fonts\source\public\wasy2\wasy10.mf
(D:\texmf\fonts\source\public\cm\cmbase.mf)
! Missing `:' has been inserted
! This can't happen (copy).
mode_param->if.unknown.mode_guard_(EXPR5000)
                                            :(EXPR5000):=(EXPR1);mode_guard_...

cx_->mode_param(pixels_per_inch,300)
                                    ;mode_param(blacker,0);mode_param(fillin...
<scantokens> cx_

<to be read again>
                   ;
mode_setup->...nput "&mode)else:mode_name[mode]fi;
                                                  if.unknown.mag:mag=1;fi.if...
l.86 mode_setup
               ; font_setup;
Transcript written on wasy10.log.
METAFONT failed for some reason
maketfm: METAFONT failed on "wasy10".
 
I guess I'll take this up with the MiKTeX people, would be nice 
if someone could confirm it though...

> We have reverted this change in 1.3.7cvs, because people complained
> that this changes the appearance of integral signs in a bad way. So
> now wasysym is not loaded anymore when you use symbols that require
> it.

So wasysym has to then be inserted manually in the preamble if
someone really wants it? This seems like a better idea, thanks.

Regards,
Milos

Reply via email to