[EMAIL PROTECTED] writes: > > Currently, we have the funny situation that the DVI output of a > LilyPond document created with `-b tex' can be viewed with xdvi (using PS > fonts) but the result of dvips doesn't work at all, inspite of > correctly loading all fonts. > > Reason is that lilypond.map (needed for dvips) is created incorrectly. > It blindly assumes that the PS font name is identical to the file > name, but this is a wrong assumption. See the table below. I tried > to fix it, but the heck I'm not able to find the place where the > `GNU-LilyPond-' prefix is added...
IIRC, the problem is that mftrace reads system installed AFMs, (eg. from a 2.4 release in /usr) using kpsewhich, extracting foundry and font name from there. I believe I fixed that bug some time ago. What version of mftrace do you run? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
