Werner LEMBERG writes: > 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...
Have you rebuilt the fonts lately (I can hardly imagine you haven't with all your work on mf sources)? Han-Wen removed all the name juggling (from mf-to-table.py) a while ago, IIRC, so using the file name as fontname should work now. > > > Werner > > > ====================================================================== > > > file name font name > ------------------------------------------------------------ > > feta-alphabet* feta-alphabet* [*] > > feta-braces-a GNU-LilyPond-feta-braces-a-15 > ... > feta-braces-i GNU-LilyPond-feta-braces-i-135 > > feta11 GNU-LilyPond-feta-11.22 > ... > feta26 GNU-LilyPond-feta-25.2 > > parmesan11 GNU-LilyPond-parmesan-11.22 > ... > parmesan26 GNU-LilyPond-parmesan-25.2 > > > [*] For orthogonality this should also have the `GNU-LilyPond-...' > prefix. > > > _______________________________________________ > lilypond-devel mailing list > lilypond-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-devel > > -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
