[Top][All Lists]

[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: Tue, 21 Jun 2011 12:52:01 +0300
User-agent: Mutt/1.5.20 (2009-06-14)

On Tue 21 Jun 2011, 11:10 David Kastrup wrote:
> Graham Percival <address@hidden> writes:
> > On Tue, Jun 21, 2011 at 10:33:31AM +0200, David Kastrup wrote:
> >> 
> >> Here is the result: uh, no it isn't.  What is the preferred method for
> >> generating a two-system preview?
> >
> > Using a full --png, unfortunately:
> > http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-to-the-tracker
> > But that's not something that you need to do; the bug squad should
> > take care of this step.
> I've been told in private communication to use Windows Paint.  That's
> not a useful option for me and takes some time (one could similarly do
> this in the Gimp if one likes interactive workflows).  What I did in the
> end was
> pngtopnm kelbl.png |pnmcut -bottom -40|pnmcrop |pnmtopng >kelbl2.png
> (first cutting off the foot line, then cropping down), resulting in

In such cases I add
  \header { tagline = "" }
to a source file and then:

  lilypond --png test.ly
  convert test.png -trim test-trim.png

It is ok to me usually.

  Dmytro O. Redchuk
  Bug Squad

reply via email to

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