I just meant that it might not be obvious that the syntax given for changing the value of pre-existing alist keys also works to add arbitrary new keys to the alist. It also might not be obvious that in this case, custom key-value pairs added to property-defaults.fonts will function properly as text font-families. There are other examples of property values, such as font variants, where Lilypond hard codes a specific schema of expected symbols or strings, and ignores anything other than those.
On Tue, Oct 8, 2024 at 10:25 PM Werner LEMBERG <w...@gnu.org> wrote: > > > One additional tip that isn't explicit in the documentation: > > property-defaults.fonts is just an alist, so you can use the same > > syntax in the \paper block to define custom font families in > > addition to the standard 'serif 'sans and 'typewriter. > > Are you missing something in the documentation? If yes, where and > what? > > In the NR, Appendix section 'Paper variables', you can find > > ‘property-defaults’ (association list (list of pairs)) > > This variable holds some settings that are used for top-level > markups and as fallback values if nothing else is specified, for > example, the standard fonts or the baseline skip. The default > value is defined in file ‘paper-defaults-init.ly’. > > In the IR, chapter 'Graphical Object Interfaces', section > 'font-interface', you can find > > ‘fonts’ (alist, with symbols as keys) > > An alist mapping font families to font names. The standard font > families are ‘music’, ‘serif’, ‘sans’ and ‘typewriter’. > > > Werner >
