On Thursday, 23 March 2000, "James Hammons" writes:
> > lilypond -f ps foo.ly
> > export GS_FONTPATH=/Cygnus/usr/lilypond-x.y.x/share/lilypond/pfa
> > gv foo.ps
>
> If only it were this easy. Apparently ghostscript (at least the Win32
> version) doesn't know about any of the feta .pfa fonts until you put them
> all into the FONTMAP file...
Hmm, I find it hard to believe they would have broken that feature
especially for windows. Maybe it wants backslashes in FONTPATH, or
it reads from the registry or whatnot. It would be nice if somebody
figured this one out.
> And even then, it knows nothing about the
> MiKTeX PS fonts...
No, but there should(!:-) be little use for ps output, if you have miktex.
> Anyway, after going through a bunch of contortions, I finally got MiKTeX
Anything worth sharing/worth of updating our stale .html docs about windows?
> installed on the Winbox and latex seems to choke on the wtk1-fugue2.tex file
> that lilypond produced (the PS file that lily makes is nice, except for the
> fact that there's no text and the flat signs are filled in). Here is an
> excerpt from wtk1-fugue2.tex:
>
> %created by: GNU LilyPond 1.3.38.jcn2, at Thu Mar 23 18:03:22 2000
> \def\{Lily was here, 1.3.38.jcn2}
Uh, the 'key' is missing: this should read
\def\mudelatagline{Lily was here, 1.3.38.jcn3}
Ah, but this is the lily.scm version you edited yourself? When you
removed the
(regexp-substitute/global #f "_"
(output-tex-string key) 'pre "X" 'post)
function, the plain old
(output-tex-string key)
function, should have been uncommented/activated again.
Anyway, no editing should be necessary with .jcn3 or .39.
> If you keep pressing return, eventually it keeps going until it chokes and
> dies complaining about a missing \hbox. Is this normal? The partial .dvi
Not quite, but almost there.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
