-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Montag, 2. Februar 2009 07:12:59 Joe Neeman wrote:
> > > Right, but it only uses the 10% buffer to decide how much to stretch
> > > the systems. The actual layout of the systems, once they've been
> > > stretched, is done in space-systems, which use
On Sun, 2009-02-01 at 20:00 +0100, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sonntag, 1. Februar 2009 19:49:05 Joe Neeman wrote:
> > On Sat, 2009-01-31 at 12:13 +0100, Reinhold Kainhofer wrote:
> > > On Samstag, 31. Januar 2009 02:06:38 Joe Neeman wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sonntag, 1. Februar 2009 19:49:05 Joe Neeman wrote:
> On Sat, 2009-01-31 at 12:13 +0100, Reinhold Kainhofer wrote:
> > On Samstag, 31. Januar 2009 02:06:38 Joe Neeman wrote:
> > > On Sat, 2009-01-31 at 00:53 +0100, Reinhold Kainhofer wrote:
> > > >
On Sat, 2009-01-31 at 12:13 +0100, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Samstag, 31. Januar 2009 02:06:38 Joe Neeman wrote:
> > On Sat, 2009-01-31 at 00:53 +0100, Reinhold Kainhofer wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
Anthony W. Youngman wrote:
Yes, currently the vertical page layouting algorithm of lilypond is sub-
optimal. Lilypond reserves 10% of the total space to make sure it does
not
overprint staves. This means that 10% of the page will always be
wasted...
Unfortunately, there is no easy way around t
In message <200901310053.32352.reinh...@kainhofer.com>, Reinhold
Kainhofer writes
On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote:
It doesn't work. I set the page-count as 2 and Lilypond still uses 3
pages. I think it is because somehow Lilypond thinks these lines don't
fit in 2 pages but i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Samstag, 31. Januar 2009 02:06:38 Joe Neeman wrote:
> On Sat, 2009-01-31 at 00:53 +0100, Reinhold Kainhofer wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote:
> > > It doesn't wo
On Sat, 2009-01-31 at 00:53 +0100, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote:
> > It doesn't work. I set the page-count as 2 and Lilypond still uses 3
> > pages. I think it is because somehow Lilypond thinks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote:
> It doesn't work. I set the page-count as 2 and Lilypond still uses 3
> pages. I think it is because somehow Lilypond thinks these lines don't
> fit in 2 pages but in fact there is a lot of space le
Tim Yang wrote:
2009/1/30 Jonathan Kulp :
Tim Yang wrote:
You can set the page count explicitly in your \paper block like this:
\paper {
page-count = 3
}
You can also set page breaks manually following directions here:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Page-breakin
2009/1/30 Jonathan Kulp :
> Tim Yang wrote:
>>
>> I have a single staff music that spans two or three pages using font
>> size 15. If I use between-system-padding=#4 and
>> between-system-spacing=#4, it will use 3 pages with 12 lines for first
>> 2 pages and a single line on 3rd page. if the number
Tim Yang wrote:
I have a single staff music that spans two or three pages using font
size 15. If I use between-system-padding=#4 and
between-system-spacing=#4, it will use 3 pages with 12 lines for first
2 pages and a single line on 3rd page. if the numbers are both #3,
then it uses 2 pages. Bu
I have a single staff music that spans two or three pages using font
size 15. If I use between-system-padding=#4 and
between-system-spacing=#4, it will use 3 pages with 12 lines for first
2 pages and a single line on 3rd page. if the numbers are both #3,
then it uses 2 pages. But I notice there i
13 matches
Mail list logo
