Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> When building scores >>20 pages (some of my scores have more than 150),
> the time and amount of memory used by the ly:optimal-page-breaking
> function is crippling (it also used to be the case with the original
> optimal page breaking function).
>
> [.
> > There are some other spacing problems with the Gregorian stuff --
> > are you in the mood to handle this too?
>
> Always happy to fix bugs, particularly if I'm already working on
> that code. But I'm not really familiar with pre-Baroque notation so
> I would need to be told exactly what needs
Le 10.07.2007 23:00, Jean-Charles Malahieude disait :
Hi all !
John being away until end of July, please apply this before generating a
new release.
Jean-Charles
---
Orange vous informe que cet e-mail a et
Hi,
A regression was introduced a few days ago regarding the spacing of
lines when next-space is set to 0 (this used to be fixed). On
ragged-bottom pages, the spacing is fine in spite of the programming
errors ("insane blocking force"), but otherwise it is wrong.
Example illustrating the problem:
On Wednesday 11 July 2007 17:18, Werner LEMBERG wrote:
> Joe,
>
>
> your latest changes break the \augmentum stuff in Gregorian notation.
> (Do a search for `augmentum' and compare the example on the web page
> created from the current git with the one in
> http://lilypond.org/doc/v2.11/Documentati
Joe Neeman <[EMAIL PROTECTED]> writes:
> On Wednesday 11 July 2007 00:09, Nicolas Sceaux wrote:
>> I'd like to write something like that using the new infrastructure.
>>
>> 1) compute the line breaks in the most straightforward way, that is
>> without considering page breaks or the number of
Joe,
your latest changes break the \augmentum stuff in Gregorian notation.
(Do a search for `augmentum' and compare the example on the web page
created from the current git with the one in
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-big-page
There are some other spacing problems w
