Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

Comment #3 on issue 1752 by mts...@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 I'll give you my first impression, which is entirely raw and un-over-intellectualized. I like the height of the new clef, but it seems too stout given

Re: midi2ly fails on OSX 10.6.8

Please cc the list, so that others can engage in the issue. Hans On 10 Jul 2011, at 10:55, Floris van Manen wrote: On Jul 10, 2011, at 00:20, Hans Aberg wrote: On 9 Jul 2011, at 22:19, Floris van Manen wrote: L.S. While trying to launch the midi2ly app, it will fail to start:

Re: Issue 1754 in lilypond: bug when slur incorporate acciaccatura

Updates: Status: Verified Mergedinto: Comment #4 on issue 1754 by philehol...@googlemail.com: bug when slur incorporate acciaccatura http://code.google.com/p/lilypond/issues/detail?id=1754 (No comment was entered for this change.)

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

Comment #4 on issue 1752 by bordage@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 I like the new height, but the top loop is too bent to the right. In the file attached, you can see A, B and C aren't aligned, contrary to the

Issue 1755 in lilypond: Add Baroque ornaments

Status: Accepted Owner: Labels: Type-Enhancement Priority-Medium New issue 1755 by philehol...@googlemail.com: Add Baroque ornaments http://code.google.com/p/lilypond/issues/detail?id=1755 A request for baroque ornaments like the attached image gained this response from Carl: The most

Re: how to create baroque ornaments

Carl Sorensen c_soren...@byu.edu wrote in message news:ca2e46fc.1ee99%c_soren...@byu.edu... -- Forwarded Message From: Giso Grimm gg3...@vegri.net Date: Mon, 27 Jun 2011 13:23:54 -0600 To: lilypond-u...@gnu.org Conversation: how to create baroque ornaments Subject: how to create baroque

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

Comment #5 on issue 1752 by pkx1...@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 Hello, I'd just like to raise a hand here and ask Why are we doing this again? To me this is a pretty fundamental change in the look of the Feta Font,

Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty

On 11-07-09 05:27 PM, lilyp...@googlecode.com wrote: Comment #1 on issue 1482 by elliot.w...@gmail.com: \caps and \smallCaps don't work with \fromproperty http://code.google.com/p/lilypond/issues/detail?id=1482 I just ran into this bug. Until it gets fixed, is there a workaround (other than

Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning

Updates: Status: Started Owner: reinhold...@gmail.com Comment #1 on issue 1581 by reinhold...@gmail.com: Pitched trill between tied notes causes `unterminated tie' warning http://code.google.com/p/lilypond/issues/detail?id=1581 Patch is up for review at:

Re: Issue 770 in lilypond: Lyrics behave differently when associated to a Voice-derived context

Updates: Status: Fixed Labels: -Patch-review fixed_2_15_5 backport Comment #4 on issue 770 by reinhold...@gmail.com: Lyrics behave differently when associated to a Voice-derived context http://code.google.com/p/lilypond/issues/detail?id=770 Pushed to git as commit

Issue 1756 in lilypond: architecture diagram image is missing

Status: New Owner: Labels: Type-Documentation Priority-High New issue 1756 by lemniska...@gmail.com: architecture diagram image is missing http://code.google.com/p/lilypond/issues/detail?id=1756 image architecture-diagram.png in CG 10.1 is missing in split-html version and it's too

Re: Issue 1751 in lilypond: Most analysis brackets get incorrect event-cause info, breaking point-and-click \tweak

Updates: Status: Fixed Labels: fixed_2_15_5 backport Comment #1 on issue 1751 by n.putt...@gmail.com: Most analysis brackets get incorrect event-cause info, breaking point-and-click \tweak http://code.google.com/p/lilypond/issues/detail?id=1751

Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning

Updates: Labels: Patch-new Comment #2 on issue 1581 by reinhold...@gmail.com: Pitched trill between tied notes causes `unterminated tie' warning http://code.google.com/p/lilypond/issues/detail?id=1581 (No comment was entered for this change.)

Re: Issue 1390 in lilypond: Tied acciaccaturas should not be printed with a slur

Updates: Status: Started Owner: reinhold...@gmail.com Labels: Patch-new Comment #2 on issue 1390 by reinhold...@gmail.com: Tied acciaccaturas should not be printed with a slur http://code.google.com/p/lilypond/issues/detail?id=1390 Patch is up for review at:

Re: Issue 1676 in lilypond: Tremolo with change staff produces false dotted note

Updates: Status: Started Owner: reinhold...@gmail.com Labels: Patch-new Comment #1 on issue 1676 by reinhold...@gmail.com: Tremolo with change staff produces false dotted note http://code.google.com/p/lilypond/issues/detail?id=1676 Patch up for review at:

Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty

Comment #3 on issue 1482 by mts...@gmail.com: \caps and \smallCaps don't work with \fromproperty http://code.google.com/p/lilypond/issues/detail?id=1482 This problem comes from the font you are using in your markups. There are currently no native small-caps capabilities in the default

Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes

Updates: Labels: -Patch-review Patch-needs_work Comment #1 on issue 1735 by lemniska...@gmail.com: modifying default behaviour of tremolo slashes http://code.google.com/p/lilypond/issues/detail?id=1735 (No comment was entered for this change.)

Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty

Comment #4 on issue 1482 by n.putt...@gmail.com: \caps and \smallCaps don't work with \fromproperty http://code.google.com/p/lilypond/issues/detail?id=1482 Here's a possible workaround using redefined \fromproperty and \caps commands: #(define-markup-command (fromproperty layout props

Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty

Comment #5 on issue 1482 by n.putt...@gmail.com: \caps and \smallCaps don't work with \fromproperty http://code.google.com/p/lilypond/issues/detail?id=1482 This problem comes from the font you are using in your markups. It's nothing to do with this, since \caps and \smallCaps are poor

Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2)

Comment #10 on issue 1014 by n.putt...@gmail.com: Full/multi measure rests should be semibreve (for any but 4/2) http://code.google.com/p/lilypond/issues/detail?id=1014 So, let's assign _even lower_ prio to this issue, but why we consider it as _fixed_? Gardner Read is out of step here.

Re: Issue 1751 in lilypond: Most analysis brackets get incorrect event-cause info, breaking point-and-click \tweak

Updates: Labels: -backport backported fixed_2_14_2 Comment #2 on issue 1751 by carl.d.s...@gmail.com: Most analysis brackets get incorrect event-cause info, breaking point-and-click \tweak http://code.google.com/p/lilypond/issues/detail?id=1751 Backported, with commits