Texinfo isn't too hard to figure out, so no worries about that part. It's just a matter of time and energy to write it up. Until I'm properly settled in my new place and have my home office set up here, about all I have the bandwidth for is quick replies on the list. Hopefully it won't take too much longer before I have some attention to spare.
On Tue, Oct 8, 2024 at 11:32 PM Werner LEMBERG <w...@gnu.org> wrote: > > > 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. > > Indeed, the NR doesn't show that you can add custom 'shorthands' for > font families. Can you provide some documentation together with an > example, telling me where to insert it most appropriately in the NR? > I can then convert everything to Texinfo syntax and submit a Merge > Request. > > Or maybe it would be more simpler to add a snippet to the LSR that can > be eventually integrated to the NR. > > > 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. > > Yes, in this case the Scheme stuff is just an interface to the > hard-coded values of the Pango library. > > > Werner >
