bug-lilypond
[Top][All Lists]
Advanced

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

Re: Bad vertical placement of staves with lilypond-book-2.6.1


From: Arvid Grotting
Subject: Re: Bad vertical placement of staves with lilypond-book-2.6.1
Date: Sun, 04 Dec 2005 12:50:33 +0100
User-agent: MT-NewsWatcher/3.4 (PPC Mac OS X)

[I know I'm posting a late reply, but I stumbled upon a horisontal staff 
placement problem myself and found this posting with a little help from 
Google.]

In article <address@hidden>,
 Mats Bengtsson <address@hidden> wrote:

[...]
> An even quicker hack is probably to set the left side of the bbox to
> zero and I'm not fully convinced that that's a worse solution than
> what you propose. With your solution, the full score will extend
> into the right hand margin of the document if you happen to have
> an instrument name. Setting the left edge of BBox to 0, on the other
> hand, will print the score with the left edge of the score lines
> aligned with the left margin of the document and any instrument
> names or long bar numbers will extend into the left margin.

Note that "10" is a long bar number.  Even "4" is a long bar number if one 
chooses to add some padding to the bar numbers.

This means that any score I write will have all bars after the first offset 
slightly to the right.  This looks ugly.

But your suggestion got me a solution!  A GNU sed one-liner in the Makefile, 
which now contains the following (of which the "sed" line is the interesting 
bit):

rodhefte.fake: rodhefte.tex
   /sw/bin/sed -i 's/%%BoundingBox: -[1-9][0-9]*/%%BoundingBox: 0/' lily*eps
   touch rodhefte.fake

rodhefte.dvi: rodhefte.fake
   latex rodhefte.tex
   makeindex rodhefte.idx
   latex rodhefte.tex

(It also containts other rules.)

> Hmm, the situation is different for documents where you want to
> include short music snippet in the middle of a text line or
> LaTeX table or whatever, where you do want the bounding box to
> include all the LilyPond output, which is an argument for your
> solution. On the other hand, for such snippets it's probably not
> that common to have anything appearing to the left of the left
> edge of the score line.

Anyway, the above is a workaround.  It works nicely for me, but it seems at 
first to break indents.  After a second look, it seems indents are broken 
anyway, and that the following line fixes indents too:

/sw/bin/sed -i 's/%%BoundingBox: -*[1-9][0-9]*/%%BoundingBox: 0/' lily*eps 

Thought you might like to know this.

Cheers,

-- 

Arvid





reply via email to

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