bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1483 in lilypond: Lyric alignment is wrong in 2.13.46


From: Carl Sorensen
Subject: Re: Issue 1483 in lilypond: Lyric alignment is wrong in 2.13.46
Date: Fri, 21 Jan 2011 18:13:20 -0700

Trevor Daniels <t.daniels <at> treda.co.uk> writes:
> 
> > Comment #14 on issue 1483 by address@hidden: Lyric
> > alignment is
> > wrong in 2.13.46
> > http://code.google.com/p/lilypond/issues/detail?id=1483

> > Second, I wonder if it might be possible to have a setting,
> > something like  make-lyrics-loose, that could be adjusted to let
> > the user select between  2.12 and 2.13 behavior.  If
> > make-lryics-loose is #t, the staves would be  placed first, then
> > filled in with the lyrics.  If make-lyrics-loose is #f,  then the
> > lyrics would be fit in as part of the sytems along with the
> > staves.
> 
> I haven't tried it, but the docs say setting
> staff-affinity to #f causes non-staff lines to
> be treated as staves.  Might this do what you
> want?

It doesn't do what I want.  I think it means that the staff-staff-spacing
variables are used instead of the staff-nonstaff spacing variables.  The
space for the lyrics is still not created unless it is manually added in the
\paper block, as part of 'system-system-spacing , 'top-system-spacing, or
'system-bottom-spacing.

> 
> > At any rate, I think that with the understanding that we need to
> > 1) use  alignAboveContext for lyrics above a staff, and 2) make
> > space for lyrics,  with top-system-spacing, system-system-spacing,
> > system-bottom-spacing, and  default-staff-staff-spacing, I think
> > we can move this bug to a  Documentation bug (still Critical), if
> > we can't fix it using the  make-lyrics-loose idea from above.
> 
> The docs certainly could be improved.  I wonder if
> the best approach is to visit the lyrics templates
> in the LM and set these up with appropriate overrides?
> One or two more to illustrate different lyric layouts
> would be helpful too.

This makes sense to me.

Thanks,

Carl




reply via email to

[Prev in Thread] Current Thread [Next in Thread]