bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)


From: Dmytro O. Redchuk
Subject: Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
Date: Thu, 23 Jun 2011 16:09:20 +0300
User-agent: Mutt/1.5.20 (2009-06-14)

On Thu 23 Jun 2011, 06:48 Colin Campbell wrote:
> A problem arises when, as I suspect, the default behaviour is
> tagline = ##t, even when not explicitly stated in the \header block.
> IOW, the absence of "tagline = " doesn't mean absence of a tagline.
> The presence of the tagline means convert must include the entire
> page in the trimmed area, which defeats the purpose of the trim.
No, there is no problem, i guess.

If ly file does not contain tagline, lilypond inserts default tagline --
this one can be overriden by the script. And should be, for the tracker.

If ly file does contain tagline -- it either should not be overriden
("fortunately enough" that script can not override existing tagline)
or should be removed (for a particular test.ly, let's say).

-- 
  Dmytro O. Redchuk
  Bug Squad



reply via email to

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