You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was tracking down the source of a bug having to do with typeface preferences not getting transmitted to LilyPond. I came across #309, which seems to match up with the symptoms I'm observing with LilyPond v2.25.11 (the version I got when I installed LilyPond using brew install lilypond --HEAD to dodge another LilyPond bug in v2.24.2 having to do with GhostScript). Unfortunately, the fix supplied by @lemzwerg in that issue no longer works as of LilyPond v2.25.6 because of two changes I found:
In LilyPond v2.25.5 and above, instead of fonts.roman, it needs to be fonts.serif, according to this patch.
In LilyPond v2.25.6 and above, instead of fonts.{serif,sans,typewriter}, it probably needs to be property-defaults.fonts.{serif,sans,typewriter}, according to this patch.
I'm not a Lua expert, but if I had to guess at what the code would look like, this would be it:
I was tracking down the source of a bug having to do with typeface preferences not getting transmitted to LilyPond. I came across #309, which seems to match up with the symptoms I'm observing with LilyPond v2.25.11 (the version I got when I installed LilyPond using
brew install lilypond --HEAD
to dodge another LilyPond bug in v2.24.2 having to do with GhostScript). Unfortunately, the fix supplied by @lemzwerg in that issue no longer works as of LilyPond v2.25.6 because of two changes I found:fonts.roman
, it needs to befonts.serif
, according to this patch.fonts.{serif,sans,typewriter}
, it probably needs to beproperty-defaults.fonts.{serif,sans,typewriter}
, according to this patch.I'm not a Lua expert, but if I had to guess at what the code would look like, this would be it:
Lua code at function
Score:ly_fonts()
Workaround
It's possible to define a
\paper
block in the LilyPond code itself. For example,The text was updated successfully, but these errors were encountered: