|
From: | James Bailey |
Subject: | Re: Catching up on bugs |
Date: | Sun, 20 Dec 2009 18:42:47 +0100 |
Regressions: page-label.ly:line 35: \mark \markup { A (page \concat { \page-ref #'markA "0" "?" ) }} \label #'markA displayed as I would expect it in 2.12.2, 2.13.9 puts the mark too far to the left.
slur-broken-trend.ly the first example e''1( \break a,) flips the slur direction; according to the description (and the behavior in 2.12) it shouldn't
Issues:Is the difference between 2.12 and 2.13.9 on ‘page-spacing-staff- group.ly’ intentional?
page-turn-page-breaking-badturns.ly it recovers well, but is not displayed on 3 pages.
page-turn-page-breaking-repeats is the difference intentional? Personally, I think it's an improvement, but that's just from the limited example presented here.
page-turn-page-breaking.ly needs to be re-written to show the functionality.
profile-property-access.ly errors and fails when I try to compile it. Additionally, the properties shown in the output are all 0
quote-during.ly and quote.ly appear to be fundamentally identical. Additionally, quote-during references cueDuring in the explanatory text, although cueDuring isn't used in the example.
ragged-right-compressed.ly compiles correctly, but the display in the html and pdf documentation is on two lines, but the description (and the output of compiling the example) are on one line
size11-26.ly is it worth it to include allfontstyle.ily in the documentation download? I downloaded the documentation, and it isn't included. Consequently, I couldn't compile any of these examples.
On 12.12.2009, at 06:43, Graham Percival wrote:
With the release of 2.13.9, we now believe that all bugs are either fixed, or have been added to the issue tracker. If you have reported a bug and it is not in the tracker, please check the bug reporting guidelines and re-submit it. http://lilypond.org/doc/v2.13/Documentation/web/bug-reports Valentin, James: I think it's time for the annual "checking the regression tests". Instructions are in the Contributor's Guide 6.4 Checking and verifying issues. I'll let you two decide who does what. It would be nice if this was done within a week or so; it's not a huge job. After that, we'll have 2.13.10, and then you two can start checking all issues. There will be more specific guidelines about tagging and priorities. I'm going to collect my thoughts into specific proposals, and begin discussions later today or tomorrow. Cheers, - Graham
[Prev in Thread] | Current Thread | [Next in Thread] |