bug-lilypond
[Top][All Lists]
Advanced

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

Re: \divisioMaior too much largest than the older versions since 2.15.


From: David Kastrup
Subject: Re: \divisioMaior too much largest than the older versions since 2.15.
Date: Thu, 25 Oct 2012 06:55:08 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux)

Manuel Burgos <address@hidden> writes:

> divisioMaior = {
>   \once \override BreathingSign  #'stencil = #ly:breathing-sign::divisio-maior
>   \once \override BreathingSign  #'Y-offset = #0
>   \breathe
> }

> \score {
>   \relative c'' {
>     g2 a4 g
>     \divisioMaior
>   }
>   \layout {
>     \context {
>       \Staff
>       \remove Bar_engraver
>     }
>   }
> }
> #############################################################################
>
> It's right working in  2.14 versions and previous, but since 2.15 it's wrong

> 2.14 output (that's fine)
> from http://lilypond.org/doc/v2.14/Documentation/notation/chants-psalms-and-
> hymns
>
> 2.16 output (that's wrong)
> from http://lilypond.org/doc/v2.16/Documentation/notation/chants-psalms-and-
> hymns

git blame lily/breathing-sign.cc

shows

d24b0b8c (Benkő Pál         2012-07-21 09:21:06 +0200  84)   Interval ydim = 
Staff_symbol_referencer::staff_span (me);
d24b0b8c (Benkő Pál         2012-07-21 09:21:06 +0200  85)   ydim.widen (-0.25 
* ydim.delta ());

Widening ydim here by some factor involving ydim.delta () very much
looks like the wrong thing to do since it would presumably scale
quadratically with size.

commit d24b0b8c2754b44fc70784967541b640d01d9b3e
Author: Benkő Pál <address@hidden>
Date:   Sat Jul 21 09:21:06 2012 +0200

    small changes of the line_count fixing series
    
    - enhance support of non-standard staves by checking staff bounds or
    being on staff line by juggling not line_count but staff_span or on_line
    - eliminate an unnecessary call and a warning


I think that's _another_ problem in the line_count series that we would
want to see a fix for in 2.16.1 if this can be managed in time.

-- 
David Kastrup




reply via email to

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