[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Custom fonts
From: |
Malte Meyn |
Subject: |
Re: Custom fonts |
Date: |
Thu, 11 Aug 2016 13:16:33 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
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.