1. dvips bringt folgenden Output:
This is dvips(k) 5.86e Copyright 2001 Radical Eye Software (www.radicaleye.com)
' TeX output 2003.04.23:2117' -> guide.ps
<tex.pro><alt-rule.pro><texc.pro><texps.pro><special.pro>. <cmti7.pfb>
<cmr5.pfb><cmsy10.pfb><cmssi10.pfb><cmti12.pfb><cmss9.pfb><cmsl8.pfb>
<cmitt10.pfb><cmtt12.pfb><cmbxti10.pfb><cmsl12.pfb><cmr12.pfb><cmss8.pfb>
<cmsl9.pfb><cmmi10.pfb><cmtt9.pfb><cmbx8.pfb><cmtt8.pfb><cmti8.pfb><cmr8.pfb>
<cmr6.pfb><cmr7.pfb><cmbx12.pfb><lasy10.pfb>
Warning: module writet1 of dvips (file lasy10.pfb): character 0 is mapped to .notdef
<snip>
<cmsl10.pfb><cmti10.pfb>
<cmbx10.pfb><cmtt10.pfb><cmcsc10.pfb><cmss10.pfb><cmr10.pfb><cmss17.pfb>[0]
[0] [1] [2<ps-files/xlogo.ps><ps-files/caution.ps>] [3] [4] [5] [6] [7] [8]
<snip>
lt. google ein Bug in dvips. Ist der inzwischen gefixt und mit
welchen Seiteneffekten hab ich zu rechnen, wenn ich die Warnings
ignoriere? pdflatex läuft fehlerfrei durch. Wie kann ich überprüfen,
ob angesprochenes character verwendet wird?
2. Output von mf
This is METAFONT, Version 2.7182 (Web2C 7.3.7) (base=mf 2003.2.17) 5 APR 2003 02:12
**\mode:=ljfour; mag:=1; nonstopmode; input wasyb5
(/var/spool/texmf/source/jknappen/sauter/wasyb5.mf
(/usr/share/texmf/fonts/source/jknappen/sauter/b-wasyb.mf
(/usr/share/texmf/fonts/source/public/cm/cmbase.mf)
(/usr/share/texmf/fonts/source/jknappen/sauter/c-cmbx.mf)
(/usr/share/texmf/fonts/source/jknappen/sauter/c-bmath.mf)
(/usr/share/texmf/fonts/source/jknappen/sauter/wasy.mf
(/usr/share/texmf/fonts/source/public/wasy/rsym.mf [5] [9] [18] [24] [23]
[93] [94] [100] [102] [96] [98] [95] [97] [101] [46] [8] [10] [11] [12]
[13] [14] [15] [25] [38] [90] [91] [39] [26] [99] [86] [87] [6] [27] [28]
[44] [47] [45] [29] [30] [21] [31] [33] [34] [35] [68] [22] [69] [32] [71]
[72] [73] [74] [36] [37] [88] [89] [92] [19] [20] [50] [0] [70] [52] [53]
[54] [64] [127] [112] [113] [110] [111] [126] [125] [55] [57] [65] [66]
[67] [62] [63] [124] [56] [80] [81] [82] [7] [114] [117] [115] [118] [116]
[119] [122] [120] [123] [121] [109]
(/usr/share/texmf/fonts/source/public/wasy/wasychr.mf [103]
! The paths don't intersect.
<to be read again>
;
intersectionpoint->...The paths don't intersect");
origin.else:0.5[point.x_.o...
<to be read again>
)
<for(l)> ...(SUFFIX0)))intersectionpoint.testpath)
; ENDFOR
l.70 ...,y0$)) intersectionpoint testpath); endfor
This error message was generated by an `errmessage'
command, so I can't give any explicit help.
Pretend that you're Miss Marple: Examine all clues,
and deduce the truth by inspired guesses.
! The paths don't intersect.
<to be read again>
;
intersectionpoint->...The paths don't intersect");
origin.else:0.5[point.x_.o...
<to be read again>
)
<for(r)> ...(SUFFIX0)))intersectionpoint.testpath)
; ENDFOR
l.70 ...,y0$)) intersectionpoint testpath); endfor
(That was another `errmessage'.)
<snip>
Bei Verwendung von ljfive tut alles -- beide 600dpi. Welche
Möglichkeiten gibt es, außer das System per Default auf ljfive
umzustellen oder modes.mf zu hacken?
H.
--
Signaturen sind wie Frauen: Hat man einmal eine Vernuenftige gefunden
gibt man sie nicht wieder her. -- Hubert Partl
http://rudi.urz.tu-dresden.de/~hille/
http://charon.wh10.tu-dresden.de/~lego/textreff.html
> 1. dvips bringt folgenden Output:
> This is dvips(k) 5.86e Copyright 2001 Radical Eye Software (www.radicaleye.com)
> ' TeX output 2003.04.23:2117' -> guide.ps
<snip>
> Warning: module writet1 of dvips (file lasy10.pfb): character 0 is mapped to .notdef
> <snip>
> [0] [1] [2<ps-files/xlogo.ps><ps-files/caution.ps>] [3] [4] [5] [6] [7] [8]
> <snip>
>
OK, scheint in 5.92b gefixt zu sein. Zumindest tritt das Warning nicht
mehr auf. Sorry!
H.
--
Gib einem Hungrigen einen Fisch, und er ist fuer einen Tag satt. Zeig
ihm, wie man angelt, und er poebelt Dich an, dass er besseres zu tun
haette, als Schnuere ins Wasser haengen zu lassen.
-- David Kastrup in de.comp.text.tex