Thanks. I just figured out how to use my own otf font. You're saying, that once I have my font finished, I can use it as \markup OR as ChordName? But wouldn't ChordName mess with my font then? Like forcing its own spacing and such?
Or lies that within the used font in ChordName? So, if I use my own font - that's just that? That would be awesome. *** www.marcobaumgartner.com On Wed, Jul 3, 2019 at 11:54 PM Aaron Hill <lilyp...@hillvisions.com> wrote: > On 2019-07-03 10:40 am, Marco Baumgartner wrote: > > One thought though: As far as I understand it: displaying chords within > > Lilypond is not done with/by a "normal" font but rather a special > > chord-mechanism. I fear, that this mechanism (as far I've seen) does a > > good > > job, but can also be seen as a limitation. How wrong would it be to > > create > > a normal font (with tons of ligatures) which I could use as > > info/comments/expression - NOT in Chord-mode to display chords? I feel > > like > > that would be the only way that leads to perfect chord symbols. Or am I > > completely out? :-) > > A ChordName is nothing more than markup at the end of the day. Since > the default stencil is ly:text-interface::print, anything you can do in > \markup you can do in a ChordName. That gives you nearly all the > freedom you would ever need, so there should be nothing to worry. > > > -- Aaron Hill > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
