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

2005-12-04 Thread Arvid Grotting
[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 <[EMAIL PROTECTED]>, Mats Bengtsson <[EMAIL PROTECTED]> wrote: [...] > An even quicker hack is probably to set the left side of t

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

2005-08-02 Thread Mats Bengtsson
Han-Wen Nienhuys wrote: Mats Bengtsson wrote: It seems that there is a hiresbb option to the graphics and graphicx packages that makes it read the %%HiResBoundingBox instead of BoundingBox. However, the rounding problem is easily solved by adding \linebreak commands. Have you thought about t

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

2005-08-02 Thread Mats Bengtsson
It seems that there is a hiresbb option to the graphics and graphicx packages that makes it read the %%HiResBoundingBox instead of BoundingBox. However, the rounding problem is easily solved by adding \linebreak commands. Have you thought about the bounding boxes for the different score lines?

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

2005-08-02 Thread Han-Wen Nienhuys
Mats Bengtsson wrote: It seems that there is a hiresbb option to the graphics and graphicx packages that makes it read the %%HiResBoundingBox instead of BoundingBox. However, the rounding problem is easily solved by adding \linebreak commands. Have you thought about the bounding boxes for the di

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

2005-08-02 Thread Han-Wen Nienhuys
Mats Bengtsson wrote: Note that the same problem would have appeared even if LaTeX and PostScript had used the same definition of point, since the text width of a LaTeX document does not have to be an integer number of points, whereas the width of an eps file is rounded to the closest integer num

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

2005-08-02 Thread Mats Bengtsson
Right, this highlights that there is a round-off problem involved as well, which further illustrates that the current solution isn't really stable. The problem is that LaTeX points "pt" don't exactly correspond to PostScript points "bp". In fact 72.27pt = 72bp =1 inch. The default text width in a

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

2005-08-02 Thread Graham Percival
On 1-Aug-05, at 11:59 PM, Mats Bengtsson wrote: Please search the mailing list archives for discussions on this topic. I think that this is new information, though -- at least, I've been following this with some interest, and I didn't know that this bug was triggered by including \usepackag

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

2005-08-02 Thread Mats Bengtsson
Please search the mailing list archives for discussions on this topic. /Mats Nicholas Haggin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings, all. I have recently been experiencing problems with vertical placement of staves in lilypond-book after upgrading fr

Bad vertical placement of staves with lilypond-book-2.6.1

2005-08-01 Thread Nicholas Haggin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings, all. I have recently been experiencing problems with vertical placement of staves in lilypond-book after upgrading from 2.4.5 to 2.6.1; the odd staves of the output are in their proper place on the page, but the even staves