lilypond-devel
[Top][All Lists]
Advanced

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

Re: make web fails


From: Erik Sandberg
Subject: Re: make web fails
Date: Sat, 3 Jun 2006 13:54:30 +0200
User-agent: KMail/1.9.1

On Thursday 01 June 2006 22:09, Han-Wen Nienhuys wrote:
> Han-Wen Nienhuys schreef:
> > Erik Sandberg schreef:
> >> [forgot to cc list]
> >>
> >> OK, I could try to make GUB work locally here. What's the first step?
> >>
> >> Hm, I guess that will take some time though. Is it OK if I commit
> >> stuff before I make it work?
> >
> > Don't commit stuff that doesn't work. However if there is one file that
> > has a GS issue, just comment that out and check if the rest woks.
> >
> > However, there is already a backlog of open issues, seemingly related to
> > some of your patches. Can you review
> >
> >   http://muurbloem.xs4all.nl:8081/~lilytest/webdoc/v2.9.7/v2.8.4.html
>
> actually, never mind that; this thing has apparently been overwritten
> with a newer but broken version. Can you review
>
> - numbering of percent repeats
fixed
> - lily-1888277513.ly
fixed (I'll send you a patch soon)
> - auto-beam-tuplets.ly
> - lily-822145481.ly
hm.. this one is about tupletSpannerDuration. I can see two alternatives to 
solve this:
* re-add time-keeping to tuplet-engraver to insert starts/stops correctly.
* make time-scaled iterator check for tupletSpannerDuration, and generate 
something like
<<
{\tuplet-start \skip 4 \tuplet-stop \tuplet-start \skip 4 ... }
music
>>
if the property is set. I think this is the cleanest way I can find, but there 
are problems:
 - grace notes: (in {c8 c c \grace c c c c}, the grace should be under the 
second bracket). Can be worked around by adding \grace \skip 1*50 after each 
tuplet start, that works in practise until we have a better way of handling 
grace notes in the iterators.
 - nested tuplets together with tupletSpannerDuration will give strange 
results, but nobody should do that anyways.

I'll go on implementing (2) if you don't have any better ideas.

> - vertical spacing  tweaks (already reported this earlier)
> - alignment-vertical-spacing.ly
will look into

-- 
Erik




reply via email to

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