Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the Italian team of translators. The file is available at:
http://translationproject.org/latest/lilypond/it.po
(We can arrange things so tha
Frédéric Bron m4x.org> writes:
>
> >> The following snippet does not give 1/32 notes grouped together as
> >> expected with 2.15.39:
> >> 2.15.42 works as expected.
This was an un-related side effect to fixing the problems with the rules
for ending beams mid-measure in 3/4. Any exceptions no
Keith OHara writes:
> Phil Holmes philholmes.net> writes:
>
>> Please look at it and see if these are intended changes.
>>
> The changes to slurs across line-breaks are intended.
>
> I don't know what caused the changes to slurs, probably the Stem/Flag
> work, but
> I've updated issue 1327.
>
>
Phil Holmes philholmes.net> writes:
> Please look at it and see if these are intended changes.
>
The changes to slurs across line-breaks are intended.
I don't know what caused the changes to slurs, probably the Stem/Flag work, but
I've updated issue 1327.
The stem failing to meet the triangle
On Mon, Jul 09, 2012 at 11:47:46PM +0100, Trevor Daniels wrote:
> It seems like my attempts to forward this and my replies to the bug
> list failed to get through, so here they are again.
Thanks for fowarding the report, Trevor.
>
> Here's the original bug report:
>
> - Original Message
My second reply, identifying a possible source of the bug.
Trevor
- Original Message -
From: "Trevor Daniels"
To: "Trevor Daniels" ; "David Stocker"
;
Sent: Sunday, July 08, 2012 12:52 PM
Subject: Re: Repeat Dots and Staff Size in 2.15.41
>
> Trevor Daniels wrote Sunday, July 08, 2
My first reply, identifying this bug as a regression ...
- Original Message -
From: "Trevor Daniels"
To: "David Stocker" ;
Sent: Sunday, July 08, 2012 12:48 PM
Subject: Re: Repeat Dots and Staff Size in 2.15.41
> Damn! Another regression. (Sorry, David, I'm not
> swearing at you - in
I don't think all these functions should be in
ly/music-functions-init.ly, but I don't know the best place for them.
Someone more familiar with the layout of code may advise. The one
function that should be here is the one you asked about in your earlier
mail - crossStaff.
Trevor
http://codere
Reviewers: ,
Message:
note that the newly added regtest shows some cases I'm not really sure
about: e.g. beaming/breaking of six eigth (or a4 a8 a8 a4) may have to
depend on whether it's a triplet or sextuplet.
Description:
make beams in 6/4, 9/4 and 12/4 behave like those in 3/4
Please review
On Mon, Jul 9, 2012 at 9:12 PM, Benkő Pál wrote:
> hi Janek and all,
>
>> There's a much easier way: set staff-size to something really big.
>>
>> I suggest that we adopt this as an official policy: fixes for
>> easy-to-overlook things should be documented by regtests using
>> big/enormous font-si
hi Janek and all,
> There's a much easier way: set staff-size to something really big.
>
> I suggest that we adopt this as an official policy: fixes for
> easy-to-overlook things should be documented by regtests using
> big/enormous font-size (e.g. between 30 and 100, depending on issue).
note th
>> The following snippet does not give 1/32 notes grouped together as
>> expected with 2.15.39:
>>
>> \new Staff {
>> \clef treble \key bf \major \time 3/4
>> \set Score.beamExceptions = #'(
>> ( end .
>> (
>> ( (1 .
> I suggest that we adopt this as an official policy: fixes for
> easy-to-overlook things should be documented by regtests using
> big/enormous font-size (e.g. between 30 and 100, depending on
> issue). So, everyone checking regtests should pay extra attention
> to details when he sees a big-font
- Original Message -
From: "Janek Warchol"
To: "Phil Holmes"
Cc: "LilyPond User Group" ; "Devel"
Sent: Monday, July 09, 2012 5:09 PM
Subject: Re: Regression test rater
On Sat, Jun 30, 2012 at 3:33 PM, Phil Holmes wrote:
First of all, thanks to those who have spent time and energ
Hi all,
i've just got enlightened about this very old thread:
On Tue, Sep 20, 2011 at 10:17 PM, Janek Warchoł
wrote:
> I want to fix an issue where a note is misplaced by about 0.07
> staffspace. I'll add a regtest for this, but how will we make sure
> that it won't be overlooked in the future?
On Sat, Jun 30, 2012 at 3:33 PM, Phil Holmes wrote:
> First of all, thanks to those who have spent time and energy rating the
> regression test at http://www.philholmes.net/lilypond/regtests/ - we're very
> close to having a rating for all the tests.
[...]
"LilyPond Regression Test Rater
Well - b
On Sun, Jul 8, 2012 at 4:56 PM, Phil Holmes wrote:
> http://www.philholmes.net/lilypond/regtestresults/
>
> Please look at it and see if these are intended changes.
beam-beat-grouping - no idea if its intended, but new version looks
better than old one to me
changed forte seems ok
collision-head-
Reviewers: ,
Message:
Please review.
Description:
As discussed on -devel, I've taken the functions Pavel developed to
support cross-staff-stems and put them into music-functions-init.ly.
This allows any user to use the functions to generate automatically
sized cross-staff-stems.
Please review t
Il giorno lun, 09/07/2012 alle 13.20 +0100, Phil Holmes ha scritto:
> I sent a compressed logfile direct to you at 14:04 UTC on 2nd July. Could
> you check - it might have been classed as spam? I could put it on a website
> for you to grab if you want.
I had Gmail filters set up in a wrong way
- Original Message -
From: "John Mandereau"
To: "Phil Holmes"
Cc: "David Kastrup" ;
Sent: Monday, July 09, 2012 1:07 PM
Subject: Re: screech-and-boink.ly
Il giorno lun, 02/07/2012 alle 13.28 +0100, Phil Holmes ha scritto:
From: "John Mandereau"
> It succeeds (see attached log), an
Il giorno lun, 02/07/2012 alle 13.28 +0100, Phil Holmes ha scritto:
> From: "John Mandereau"
> > It succeeds (see attached log), and failure reports don't provide enough
> > details for me to investigate, so I'm stuck at this issue. Mike, David,
> > could you please try the same and send the outp
wrote Monday, July 09, 2012 5:55 AM
> Ignore my other message that talked about using git-cl to upload
> an edited patch; I hadn't noticed that you did that here.
OK. It was not worth the effort for a two-word change.
I uploaded a new patch-set here as the changes were more
extensive. git-c
I actually only wanted to get rid of the whitespace errors plagueing
every test of this patch, but one programming error jumped out so badly
at me that I had to flag it as well.
http://codereview.appspot.com/5626052/diff/79059/lily/axis-group-interface.cc
File lily/axis-group-interface.cc (right
23 matches
Mail list logo
