[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: paper spacing variables not being respected for a score inside marku
Re: paper spacing variables not being respected for a score inside markup
Sat, 9 Jun 2018 21:11:29 -0400
On Sat, Jun 9, 2018 at 5:21 AM Thomas Morley <address@hidden> wrote:
> > I'm doing some chords+lyrics song sheets, and trying to achieve a two
> > column layout.
> If all you want is to write chords+lyrics, LilyPond may not be the
> best tool for this purpose.
I tried to keep my example simple. The real sheets will also include
things like fret diagrams and tabs of riffs, which lilypond is useful
> > From what I've read, the way to accomplish this is by
> > putting scores within a markup block.
> > This works to get the two columns, but as soon as I do it, the \paper
> > variables that are controlling the vertical spacing seem to be
> > ignored.
> As soon as you put a score in a markup, you are in markup-mode.
> Vertical spacing of multi-line-markups is controlled by 'baseline-skip
> and in general not by paper-settings.
> \score in \markup is a markup-command, internally calling the
> markup-list-command \score-lines, which outputs a list of stencils
> (here each stencil contains one line of chords/lyrics). They are
> stacked vertically by \score using 'baseline-skip.
> So all as expected, no bug.
When I include \override #'(baseline-skip . 0.5) inside the markup
block, only the space between the lyrics and the next chord line is
reduced. The space between the chords and the lyrics above them is
still very large. Is there some other way to reduce the space between
the two systems? Can you make it so that the scores inside the columns
of my simple example have the same spacing as the score above?
Alternatively, is there some other way to create a two column layout
without resorting to putting \scores inside \markups?
Although some might consider \scores being laid out completely
differently inside of \markups vs.outside of \markups a feature, it
also seems reasonable that some might call that a bug, or at the very
least, a very unfortunate feature. :)
As a programmer, I absolutely love being able to make scores, lead
sheets, etc. with simple text files that can be manipulated like code,
diffed, and tracked in source control. Lilypond does have some very
unintuitive ways of doing things, though.
Still better than trying to get MuseScore to do what I want...