Hello Mats, you are right, it works. Thank you very much.
Bye! Torsten >This should definitely not be necessary. I have used lilypond-book together >with MikTeX in Windows and I don't have any font problems (there are Python >problems, though). I hope you have followed the instructions on how to use >the --psfonts flag and the corresponding flag for dvips. > /Mats >Quoting Torsten BXhm <[EMAIL PROTECTED]>: >> Hello Spencer, after you have run lilypond-book you have to delete all >> lily-*-1.eps files in the output directory. Then rename all lily-*.eps >> files to lily-*-1.eps. Now you can proceed as normal. Alternatively you >> can correct the corresponding reference in all lily-*-systems.tex files. >> This bug I found also in version 2.6 Windows and Linux. Hope it helps. >> Torsten >>> After following the directions in the manual, the .dvi file that I end >>> up with is only the staff, ledger lines, and note stems. After using >>> ps2pdf, the resulting file has the staff, ledger lines, note stems, and >>> the C for common time. I installed the binary packege from the site into >>> my home directory. Lilypond files by themselves render fine, as do LaTeX >>> files. I'm running LaTeX version 2.0.2-r8 on Gentoo. Here's a >>> transcription of the session: [EMAIL PROTECTED] ~/Documents/Lilypond $ >>> ls out test.tex [EMAIL PROTECTED] ~/Documents/Lilypond $ >>> lilypond-book --output=out --psfonts t est.tex lilypond-book (GNU >>> LilyPond) 2.8.0 Reading test.tex... >> >> _______________________________________________ bug-lilypond mailing list >> bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
