Re: Footnotes

On 10/29/2017 5:41 PM, Dave Hartley wrote: I'm currently typesetting some music for our school choir, SATB with a piano part and a small percussion part. I /tried/ to get some additional directions to the performers inserted as footnotes, but I don't seem to be able to get the footnotes in

Re: Footnotes

On 10/29/2017 5:41 PM, Dave Hartley wrote: I'm currently typesetting some music for our school choir, SATB with a piano part and a small percussion part. I /tried/ to get some additional directions to the performers inserted as footnotes, but I don't seem to be able to get the footnotes in

Footnotes

I'm currently typesetting some music for our school choir, SATB with a piano part and a small percussion part. I *tried* to get some additional directions to the performers inserted as footnotes, but I don't seem to be able to get the footnotes in *\markup attached to notes* working at all. MWE:

slurs between pairs of notes horizontally close and vertically distant

I'm working on a score with many pairs of notes a sixth or seventh apart slurred together. When the stem of the second note of a pair is down, the slur intersects the accidental. If I increase 'Slur.details.accidental-collision' the slur avoids the accidental, but is not as well-shaped. For

Re: order of events given to engravers

Maurits Lamers writes: > Hi all, > > I came across something peculiar in the order in which events are sent > out to the engravers. > Assuming I have listeners on notes, rests and breaks, it turns out > that a break event in special cases can be sent after other events on

order of events given to engravers

Hi all, I came across something peculiar in the order in which events are sent out to the engravers. Assuming I have listeners on notes, rests and breaks, it turns out that a break event in special cases can be sent after other events on the same moment. So, my question is: when a break happens

Re: non-triplet tuplets collide with staff

Thanks for clarifying. My score only uses triplets for unbeamed notes, and I mistakenly misattributed the number and bracket placement to the ratio rather than the presence of beams. Next time I'll test with a simpler example like the one you include. Your solution works well in 2.18.2.

Re: Cross-staff beam slope - can it be specified?

On Sat, 2017-10-28 at 08:49 -0400, Ben wrote: > On 10/27/2017 1:33 PM, David Sumbler wrote: > > In the above rather silly example, the beam between the 2 cross- > > staff > > notes slopes slightly upwards.  If I add a dynamic, say \f , after > > > g>2. in line 7, the staves are forced

Re: How to get \fromproperty to work with score headers?

That's essentially what I've been doing, but it requires making each score a bookpart unto itself. It's an okay solution, but it's nice to be able to start a new movement mid-page. Thanks anyway for the suggestion, though! On Sun, Oct 29, 2017 at 9:21 AM, Graham King

Re: dead link in http://lilypond.org/doc/v2.18/Documentation/

It's a known problem, already in the tracker Il 29 ottobre 2017 15:46:47 CET, Malte Meyn ha scritto: >Am 29.10.2017 um 15:33 schrieb bb: >> >http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion >> the link >> Schnipsel: Percussion. >>

Re: How to get \fromproperty to work with score headers?

On Sun, 2017-10-29 at 15:30 +, Graham King wrote: > On Sun, 2017-10-29 at 03:21 -0700, Shevek wrote: > > > Does anyone know if there's an updated version of > > http://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level headers? > > It's listed as "to do" in the snippet, but I

Re: Small caps not working in bookTitleMarkup?

On 10/29/2017 12:09 PM, Patrick Hubers wrote: Op 29-10-2017 om 16:48 schreef Malte Meyn: [...] I just found out that this is a know bug: https://sourceforge.net/p/testlilyissues/issues/1482/ There you can also find a workaround. Ah, thanks for that! I'll see if I can get it to work with the

Re: Small caps not working in bookTitleMarkup?

Op 29-10-2017 om 16:48 schreef Malte Meyn: [...] I just found out that this is a know bug: https://sourceforge.net/p/testlilyissues/issues/1482/ There you can also find a workaround. Ah, thanks for that! I'll see if I can get it to work with the options mentioned there. Regards, Patrick

Re: Small caps not working in bookTitleMarkup?

Op 29-10-2017 om 16:41 schreef Malte Meyn: Am 29.10.2017 um 15:50 schrieb Patrick Hubers: I'm trying to create titles in small caps by modifying the bookTitleMarkup in my stylesheet. For some reason, all font modifiers (\bold, \italic etc.) seem to work, except for \caps or \smallCaps.

Re: Small caps not working in bookTitleMarkup?

Am 29.10.2017 um 16:41 schrieb Malte Meyn: Am 29.10.2017 um 15:50 schrieb Patrick Hubers: Hi, I'm trying to create titles in small caps by modifying the bookTitleMarkup in my stylesheet. For some reason, all font modifiers (\bold, \italic etc.) seem to work, except for \caps or

Re: Small caps not working in bookTitleMarkup?

Am 29.10.2017 um 15:50 schrieb Patrick Hubers: Hi, I'm trying to create titles in small caps by modifying the bookTitleMarkup in my stylesheet. For some reason, all font modifiers (\bold, \italic etc.) seem to work, except for \caps or \smallCaps. […] Am I doing something wrong, have I

Re: How to get \fromproperty to work with score headers?

On Sun, 2017-10-29 at 03:21 -0700, Shevek wrote: > Does anyone know if there's an updated version of > http://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level headers? > It's listed as "to do" in the snippet, but I believe that dates back to > several years ago. I'd like to use

Small caps not working in bookTitleMarkup?

Hi, I'm trying to create titles in small caps by modifying the bookTitleMarkup in my stylesheet. For some reason, all font modifiers (\bold, \italic etc.) seem to work, except for \caps or \smallCaps. I have the line \bold \fontsize #6 { \fromproperty #'header:title } in my stylesheet,

Re: dead link in http://lilypond.org/doc/v2.18/Documentation/

Am 29.10.2017 um 15:33 schrieb bb: http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion the link Schnipsel: Percussion. http://lilypond.org/doc/v2.18/Documentation/snippets/schlagzeug -> not found In the english version it's active

dead link in http://lilypond.org/doc/v2.18/Documentation/

http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion the link Schnipsel: Percussion. http://lilypond.org/doc/v2.18/Documentation/snippets/schlagzeug -> not found In the english version it's active http://lilypond.org/doc/v2.18/Documentation/snippets/percussion

Re: How to get \fromproperty to work with score headers?

Am 29.10.2017 um 11:21 schrieb Shevek: Does anyone know if there's an updated version of http://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level headers? It's listed as "to do" in the snippet, but I believe that dates back to several years ago. I'd like to use \fromproperty

How to get \fromproperty to work with score headers?

Does anyone know if there's an updated version of http://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level headers? It's listed as "to do" in the snippet, but I believe that dates back to several years ago. I'd like to use \fromproperty #'header:piece to put movement titles at the top of

Re: Cannot include # in URL?

Worked like a charm, Abraham. Thank you so much. That made my night! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: non-triplet tuplets collide with staff

Hi Mason, please always state the version you use and a tiny example. Maybe you would have spotted that 2017-10-28 23:38 GMT+02:00 Mason Hock : > Lilypond by default seems to place all tuplet numbers/brackets so that they > collide with the staff, with the exception of

Re: Cannot include # in URL?

Hi, Tom! On Sun, Oct 29, 2017 at 12:51 AM Tom Campbell wrote: > Can't figure out how to include # in a URL. When I do something like this: > > \markup { > For more, see > http://lilypond.org/doc/v2.18/Documentation/notation/writing-rhythms#durations > } > > > I get the

Cannot include # in URL?

Can't figure out how to include # in a URL. When I do something like this: \markup { For more, see http://lilypond.org/doc/v2.18/Documentation/notation/ writing-rhythms#durations } I get the following message: error: GUILE signaled an error for the expression beginning here For more, see