Re: Custom fonts

[Malte Meyn]

Am 11.08.2016 um 13:11 schrieb Erik Ronström:
> However, for some reason it doesn’t work: #(define fonts …) seems to have no 
> effect at all in my document. Any tips for why?

Which version of LilyPond are you using?

You should test whether LilyPond “sees” the CM fonts and how they are 
named. This can be done by

lilypond -dshow-available-fonts

in the command line. If you’re using Linux (this probably works with Mac 
too) you can search this list using grep (-i for case insensitive):

lilypond -dshow-available-fonts 2>&1 | grep -i cm
lilypond -dshow-available-fonts 2>&1 | grep -i modern
lilypond -dshow-available-fonts 2>&1 | grep -i lm

The last is because some TeX distributions have Latin Modern fonts 
instead of Computer Modern.