On Thursday, 22 October 1998, Mats Bengtsson writes:
> I wanted to try the Postscript output but failed on the first step,
> namely make -C mf pfa
Make sure that the exit code of metapost is ignored (metapost-rules.make),
this was probably not the case in pl17 due to a 'look and fix' bugfix.
> First of all, I didn't have any mfplain.mem on my system, so I tried to
> manufacture one, using lilypond-xxx/mf/mfmp.ini and variations of the
> same theme.
The postscript output is very experimental, more precisely, the
lilyponddefs.ps needs quite some hacking, and the output mechanism
is being redone to use guile.
Having said that, i now see that the mpmf.ini i distributed was not
really helping, it'll be fixed in the next release (1.1/0.18)
Anyway, this is what a session could look like:
15:22:21 appel ~/usr/src/lilypond/mf$ cat mfplain.ini
\input plain.mf
\input modes.mf
\dump mfplain
15:22:37 appel ~/usr/src/lilypond/mf$ inimp mfplain.ini
This is MetaPost, Version 0.631 (C version 6.1) (INIMP)
(mfplain.ini (/usr/lib/texmf/texmf/metafont/base/plain.mf
Preloading the plain base, version 2.71: preliminaries,
basic constants and mathematical macros,
macros for converting from device-independent units to pixels,
macros and tables for various modes of operation,
macros for drawing and filling,
macros for proof labels and rules,
macros for character and font administration,
and a few last-minute items.) (/usr/lib/texmf/texmf/metafont/misc/modes.mf) )
Beginning to dump on file mfplain.mem
(mem=mfplain 98.10.22)
at most 2231 strings of total length 30040
10909 memory locations dumped; current usage is 3246&7313
976 symbolic tokens
Transcript written on mfplain.log.
15:22:43 appel ~/usr/src/lilypond/mf$ l mfplain.mem
-rw-r--r-- 1 jantien fred 149824 Oct 22 15:22 mfplain.mem
15:22:48 appel ~/usr/src/lilypond/mf$ cat ../stepmake/stepmake/metapost-rules.make
$(outdir)/%.pfa: %.mf
# urg
# i've got no idea what this scaling could be for, on both sides...
# it seems that 'low_res', which should be all we ever need according
# to the metapost mfplain guru, really does 200dpi, iso 600dpi (minimun)
-$(METAPOST) "&mfplain \mode=lowres; \mag=100.0; batchmode; input $<"
# -$(METAPOST) "&mfmp \mode=ljfour; \mag=100.0; batchmode; input $<"
$(PYTHON) $(depth)/buildscripts/ps-to-pfa.py $<
rm -f $(basename $(@F)).[0-9]*
rm -f $(basename $<).log $(basename $<).tfm
15:26:36 appel ~/usr/src/lilypond/mf$ make out/feta20.pfa
mp "&mfplain \mode=lowres; \mag=100.0; batchmode; input feta20.mf"
This is MetaPost, Version 0.631 (C version 6.1)
make: [out/feta20.pfa] Error 1 (ignored)
/usr/bin/python ../buildscripts/ps-to-pfa.py feta20.mf
ps-to-pfa version 0.2
Font: feta20
[[feta20.0][feta20.1][feta20.10][feta20.11][feta20.12][feta20.13][feta20.14][feta20.15][feta20.16][feta20.17][feta20.18][feta20.19][feta20.2][feta20.20][feta20.21][feta20.22][feta20.23][feta20.24][feta20.25][feta20.26][feta20.27][feta20.28][feta20.29][feta20.3][feta20.30][feta20.31][feta20.32][feta20.33][feta20.34][feta20.35][feta20.36][feta20.37][feta20.38][feta20.39][feta20.4][feta20.40][feta20.41][feta20.42][feta20.43][feta20.44][feta20.45][feta20.46][feta20.47][feta20.48][feta20.49][feta20.5][feta20.50][feta20.51][feta20.52][feta20.53][feta20.54][feta20.55][feta20.56][feta20.57][feta20.58][feta20.59][feta20.6][feta20.60][feta20.61][feta20.62][feta20.63][feta20.64][feta20.65][feta20.66][feta20.67][feta20.68][feta20.69][feta20.7][feta20.70][feta20.71][feta20.72][feta20.73][feta20.74][feta20.75][feta20.76][feta20.77][feta20.8][feta20.9]]
Wrote PostScript font: out/feta20.pfa
rm -f feta20.[0-9]*
rm -f feta20.log feta20.tfm
15:27:06 appel ~/usr/src/lilypond/mf$ `grep export ../NEWS`
15:28:34 appel ~/usr/src/lilypond/mf$ export
GS_LIB=$HOME/usr/src/lilypond/tex
15:28:43 appel ~/usr/src/lilypond/mf$ export
GS_FONTPATH=$HOME/usr/src/lilypond/mf/out
15:28:43 appel ~/usr/src/lilypond/mf$ gv x.ps
> Whatever I did, Metapost complained about variables getting out of
> range.
Yes, urg, i don't know about that either. That's why metapost in run in
batchmode, and the exit status is ignored (metapost-rules.make).
There's a lot i don't quite understand of the metapost/postscript font
stuff, we'll have to figure that out some time. Currently i'm learing
and debugging guile...
Greetings,
Jan.
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.xs4all.nl/~jantien/lilypond
