Typo in the Contributor's Guide
Hello folks, ‘sortly’ instead of ‘shortly’. JM -- 14.7 Grand LilyPond Input Syntax Standardization (GLISS) Summary • Start: sortly after 2.14 comes out, which is currently estimated to happen in January 2011. • Length: 6-12 months. We’re not going to rush this. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Typo in the Contributor's Guide
Am 13.01.2016 um 13:55 schrieb Menu Jacques: > Hello folks, > > ‘sortly’ instead of ‘shortly’. Well, I think this is more a conceptual conflict than a typo :-/ > > JM > > -- > > 14.7 Grand LilyPond Input Syntax Standardization (GLISS) > > Summary > > • Start: sortly after 2.14 comes out, which is currently estimated to > happen in January 2011. > > • Length: 6-12 months. We’re not going to rush this. > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Typo in the Contributor's Guide
Urs Liska writes: >> Am 13.01.2016 um 13:55 schrieb: >>> Hello folks, >>> >>> ‘sortly’ instead of ‘shortly’. >> >> Well, I think this is more a conceptual conflict than a typo :-/ >>> >>> 14.7 Grand LilyPond Input Syntax Standardization (GLISS) >>> >>> Summary >>> >>> • Start: sortly after 2.14 comes out, which is currently >>> estimated to happen in January 2011. >>> >>> • Length: 6-12 months. We’re not going to rush this. Well, we were not rushing this indeed. But it turned out more like a Gradual LilyPond Input Syntax Streamlining. I think our main problem, both with regard to syntax/input as well as typesetting, remains piano music and piano extracts and similarly musically dense material. LilyPond's slur/stem/beam/notehead/duration relations with the context hierarchy are too rigid to do quite a bit of musical information justice. And where stuff can be done, the input required for doing so is awful. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)
Reviewers: , Message: Please review, thanks. -Paul Description: Add ly:one-line-auto-height-breaking Includes 4 commits: Changes entry for ly:one-line-auto-height-breaking Doc: NR 4.3.2 add ly:one-line-auto-height-breaking Includes a few related edits to NR 4.3.2 mainly for ly:one-line-breaking Add regtest for ly:one-line-auto-height-breaking Add ly:one-line-auto-height-breaking Please review this at https://codereview.appspot.com/284240043/ Affected files (+90, -33 lines): M Documentation/changes.tely M Documentation/notation/spacing.itely A input/regression/one-line-auto-height-breaking.ly A + lily/include/one-line-auto-height-breaking.hh A + lily/one-line-auto-height-breaking.cc M lily/one-line-page-breaking.cc M lily/page-breaking-scheme.cc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)
LGTM https://codereview.appspot.com/284240043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel