Re: chordname suffixes not superscript?
Hi Christian, > My question is this: is there a way to set chordnames so that the chord > suffix, no matter what it is, is not superscript? This can probably be done "in one swell foop" by modifying the .scm file that generates ChordNames. The more straight-forward and flexible (if tedious) way is to create your own custom chord markup list. I've given you a head start with the attached file(s): simply continue adding the markup after the remaining chords in chord-name-custom.ly, and see customChords_list.ly for an example of how to \include the file in your "real" Lilypond files. Hope this helps! Kieren. chord-name-custom.ly Description: Binary data customChords_list.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: chordname suffixes not superscript?
Hello, -Original Message- From: lilypond-user-bounces+james.lowe=datacore@gnu.org on behalf of Christian McConnell Sent: Sat 29/05/2010 17:55 My question is this: is there a way to set chordnames so that the chord suffix, no matter what it is, is not superscript? In other words, can I make it so that "sus4" or "7" has the same baseline and size as the chord root, just like "m" does? -- While not as 'elegant' I guess, my chord notation needs are simple, so I simply define a 'markup' variable which will make the baselines all the same. Cm7 = \markup { \null \raise #0.5 {\sans \small \general-align #X #CENTER Cm7 } } Then I simply add '\Cm7' thus: { c4^\Cm7 } The other variables \null \raise #0.5 and \general-align #X #CENTER are what I find works for me in my compositions, so these might not be apt for you, but I hope you can get my point. James ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
chordname suffixes not superscript?
Hello everyone, I've been a lurker, and I'm still something of a newbie, but I'm enjoying using Lilypond and I appreciate the help this list has been. My question is this: is there a way to set chordnames so that the chord suffix, no matter what it is, is not superscript? In other words, can I make it so that "sus4" or "7" has the same baseline and size as the chord root, just like "m" does? Thanks, Chris McConnell ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user