[tex-k] fonts for dvips
Tomas G. Rokicki
rokicki@CS.Stanford.EDU
Fri, 18 Oct 2002 13:00:53 -0700
Okay, here's a patch that should get you over the hump, temporarily.
TeXK guys, should bad penpos be as nonfatal as badpos?
What is it about this font/mode combination that is causing bad errors
at this high resolution?
The change is to `which mktexpk`:
*** omktexpk Fri Oct 18 12:57:08 2002
--- mktexpk Fri Oct 18 12:58:17 2002
***************
*** 204,215 ****
grep '^!' $NAME.log | sort >$$.errs 2>/dev/null
grep '^! Strange path' $$.errs >$$.strange 2>/dev/null
grep '^! bad pos.' $$.errs >$$.badpos 2>/dev/null
! cat $$.badpos $$.strange | sort > $$.errs_accept
if cmp $$.errs $$.errs_accept >/dev/null 2>&1; then
test -s $$.strange >/dev/null 2>&1 \
&& echo "$progname: warning: \`$cmd' caused strange path errors." >&2
test -s $$.badpos >/dev/null 2>&1 \
&& echo "$progname: warning: \`$cmd' caused bad pos errors." >&2
else
echo "$progname: \`$cmd' failed." >&2
test -s $NAME.log && mv -f $NAME.log "$KPSE_DOT"
--- 204,218 ----
grep '^!' $NAME.log | sort >$$.errs 2>/dev/null
grep '^! Strange path' $$.errs >$$.strange 2>/dev/null
grep '^! bad pos.' $$.errs >$$.badpos 2>/dev/null
! grep '^! bad penpos.' $$.errs >$$.badpenpos 2>/dev/null
! cat $$.badpenpos $$.badpos $$.strange | sort > $$.errs_accept
if cmp $$.errs $$.errs_accept >/dev/null 2>&1; then
test -s $$.strange >/dev/null 2>&1 \
&& echo "$progname: warning: \`$cmd' caused strange path errors." >&2
test -s $$.badpos >/dev/null 2>&1 \
&& echo "$progname: warning: \`$cmd' caused bad pos errors." >&2
+ test -s $$.badpenpos >/dev/null 2>&1 \
+ && echo "$progname: warning: \`$cmd' caused bad penpos errors." >&2
else
echo "$progname: \`$cmd' failed." >&2
test -s $NAME.log && mv -f $NAME.log "$KPSE_DOT"