2.18

Ok, nobody including myself bothered reverting commit 88d306d9c5666b5ade4a136df29cca19c5ff5ed7 Author: Mike Solomon Date: Sat Apr 6 09:54:58 2013 +0200 Break slurs between alternative endings in repeats; issue 1698. Create new event-types BreakPhrasingSlurEvent BreakSlurEvent,

Re: 2.18

David Kastrup writes: > We should have at least two more development releases for the > fine-polishing before forking stable. That gives us four weeks, and > most things of some substance should be done in the first half of > that. Two things I consider important for 2.17.17 are the > strokeadj

patch: add some italian words in the Music Glossary

This is a trivial patch: may I just push it? To staging or master? 0001-Doc-add-some-missing-italian-translations-in-Music-G.patch Description: Binary data ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lil

Re: patch: add some italian words in the Music Glossary

Federico Bruni writes: > This is a trivial patch: may I just push it? > To staging or master? Never push anything to master: that breaks our system. Push to staging, and it will arrive in due time in master. Or not, depending on whether it actually passes all tests. -- David Kastrup __

Re: patch: add some italian words in the Music Glossary

2013/4/14 David Kastrup > Never push anything to master: that breaks our system. Push to staging, > and it will arrive in due time in master. Or not, depending on whether > it actually passes all tests. > ok, done ___ lilypond-devel mailing list lily

Doc: add missing engraver to example of a user-defined context (3195) (issue 8538046)

LGTM Cheers, Ian https://codereview.appspot.com/8538046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Time signature before repeat bars at beginning of line; issue 828 (issue 8508043)

On Sat, 13 Apr 2013 07:21:17 -0700, wrote: What if a non-repeat barline is placed after a break? Do i understand correctly that this patch will also place it after time sig, and is this what we want? Yes it would place the bar-line after the time signature. The only bar-lines at the begin

Re: Time signature before repeat bars at beginning of line; issue 828 (issue 8508043)

LGTM then. thanks, Janek https://codereview.appspot.com/8508043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Time signature before repeat bars at beginning of line; issue 828 (issue 8508043)

On 2013/04/14 17:08:58, janek wrote: LGTM then. thanks, Janek PS it may be worth changing commit message so that it's obvious that not only repeat bars behaviour should change. https://codereview.appspot.com/8508043/ ___ lilypond-devel mailing list

PATCHES: Countdown for April 17th - 19:00 GMT

*Countdown – April 17th 2013 – 19:00 GMT* * * * * * * * * 3301 Documentation Trevor Daniels Push Remove remaining use

Re: Doc: Error message: unexpected \new (3285) (issue 8581044)

LGTM https://codereview.appspot.com/8581044/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.18

David Kastrup gnu.org> writes: > Ok, nobody including myself bothered reverting > Break slurs between alternative endings in repeats; issue 1698. > in time for 2.17.16 and it is clearly unfit for releasing in 2.18 (new > functionality, new interfaces, change of behavior without significant >

Re: Doc: add missing engraver to example of a user-defined context (3195) (issue 8538046)

LGTM https://codereview.appspot.com/8538046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: rename section in LM (3280) (issue 8575044)

LGTM https://codereview.appspot.com/8575044/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Be serious about setstrokeadjust in PostScript primitives (issue 8663044)

David, i'm sorry, but i don't understand what the code does. Obviously, it would help if i knew Postscript ;) but unfortunately i don't have time to learn it now. Since i suppose that quite a few devs may be in a similar situation, i think that adding some comments would be a good idea, even if

Re: Be serious about setstrokeadjust in PostScript primitives (issue 8663044)

On 2013/04/14 20:38:12, janek wrote: David, i'm sorry, but i don't understand what the code does. Obviously, it would help if i knew Postscript ;) but unfortunately i don't have time to learn it now. The most important resource is PLRM.pdf (available on Adobe's website, though the locatio

Re: 2.18

Keith OHara writes: > David Kastrup gnu.org> writes: > >> Ok, nobody including myself bothered reverting >> Break slurs between alternative endings in repeats; issue 1698. >> in time for 2.17.16 and it is clearly unfit for releasing in 2.18 (new >> functionality, new interfaces, change of be

Re: Be serious about setstrokeadjust in PostScript primitives (issue 8663044)

2013/4/14 : > On 2013/04/14 20:38:12, janek wrote: >> i'm sorry, but i don't understand what the code does. >> Obviously, it would help if i knew Postscript ;) but >> unfortunately i don't have time to learn it now. > > The most important resource is PLRM.pdf (available on Adobe's website, > thoug

Re: Remove remaining uses of \times (3301) (issue 8509043)

Pushed to staging as bb994e1c15cd048c12ab3d777e90b447bbf37b16 but with a commit message (Doc: use @dots{} rather than "...") that does not match the original issue. Closing ... https://codereview.appspot.com/8509043/ ___ lilypond-devel mailing list lil

Re: 2.18

Hi, 2013/4/14 David Kastrup : > > Ok, nobody including myself bothered reverting > > commit 88d306d9c5666b5ade4a136df29cca19c5ff5ed7 > Author: Mike Solomon > Date: Sat Apr 6 09:54:58 2013 +0200 > > Break slurs between alternative endings in repeats; issue 1698. > > Create new event-type

Re: [Lilypond-auto] Issue 1698 in lilypond: Slurs and ties are notcorrect over repeats

> Comment #65 on issue 1698 by m...@mikesolomon.org: Slurs and ties are not > correct over repeats > http://code.google.com/p/lilypond/issues/detail?id=1698 > > These are all good observations. If the patch gets reverted, I'll wait > till 2.19 is out before tackling all this. Otherwise, I'l

Re: 2.18

Janek Warchoł writes: >>> Two things I consider important for 2.17.17 are the strokeadjust >>> changes for PostScript output, and the vertical rest positioning. >> >> Is this parody? April Fools Day was two weeks ago, David. > > Indeed, i consider strokeadjust changes as definitely inappropriate

Re: Be serious about setstrokeadjust in PostScript primitives (issue 8663044)

On 2013/04/14 21:43:36, janek wrote: 2013/4/14 : > On 2013/04/14 20:38:12, janek wrote: >> i'm sorry, but i don't understand what the code does. >> Obviously, it would help if i knew Postscript ;) but >> unfortunately i don't have time to learn it now. > > The most important resource is PLRM.pdf

busy developer's summary 7: stable or not stable? that is the question

The most important topic in this week's discussions seems to be: "does this patch deserve a 'stable' label or not?" The latest discussion about stable release is here: http://lists.gnu.org/archive/html/lilypond-devel/2013-04/msg00225.html And here are the problematic issues: Allow slurs to break

Re: 2.18

David, 2013/4/15 David Kastrup : > Janek Warchoł writes: > Two things I consider important for 2.17.17 are the strokeadjust changes for PostScript output, and the vertical rest positioning. >>> >>> Is this parody? April Fools Day was two weeks ago, David. >> >> Indeed, i consider strok

Re: Doc: add missing engraver to example of a user-defined context (3195) (issue 8538046)

LGTM https://codereview.appspot.com/8538046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: rename section in LM (3280) (issue 8575044)

On Fri, Apr 12, 2013 at 11:36:40AM +, janek.lilyp...@gmail.com wrote: > For me "adjustments" would be probably best. Adjustments can be big or > small, and - as far as i understand this word - can mean both adjusting > something that's wrong so that it'll be correct, and changing something > a