Re: MIDI Marker feature request

Hello, On 04/08/2021 02:17, Keith Smith wrote: > It would be very useful if lilypond had the ability to add MIDI markers > to the MIDI output. Currently, the structure of a song is difficult to > produce in MIDI as only \unfoldrepeats is available and constructs like > D.S. al coda, are not

Re: Possible documentation error in 2.7.2

Hello Ben, On 29/02/2020 08:46, Ben Eichler wrote: HI there, I read at "2.7.2 Displaying Chords" in the docs: "*Chord names can be displayed only at the start of lines and when the chord changes.*" This is a little bit misleading. By default, each chord in the content is printed by Lilypond.

Re: glyph-path-regexp in SVG output is overly strict

Jonas, On 21/02/2020 11:54, Jonas Hahnfeld wrote: Am Freitag, den 21.02.2020, 11:50 + schrieb pkx166h: Jonas On 21/02/2020 11:33, Simon Tatham wrote: Jonas Hahnfeld < hah...@hahnjo.de wrote: looking at https://sourceforge.net/p/testlilyissues/issues/5779/ and the grammar you linked

Re: glyph-path-regexp in SVG output is overly strict

Jonas On 21/02/2020 11:33, Simon Tatham wrote: Jonas Hahnfeld wrote: looking at https://sourceforge.net/p/testlilyissues/issues/5779/ and the grammar you linked, I think the regular expression is also missing '+Aa,'. Does it make sense to fuse attached patch? The idea looks sensible to me,

Re: glyph-path-regexp in SVG output is overly strict

Hello Simon, On 20/02/2020 18:33, Simon Tatham wrote: A user of my notation font Gonville reported to me this week that they had tried to use the Lilypond SVG backend with Gonville, and had found that everything worked fine except that the sharp signs were mysteriously missing from the output.

Re: layout doesn't work as I expected

hello fcorvi This sounds like a question for the 'user' list not the 'bug' list. I suggest you try there first. This 'bug-lilypond' list is specifically for problems with the lilypond code/ incorrect/ugly output than for questions about how to do X or why something might not do what you

Re: french beaming incorrectly makes stems longer

Hello, On 25/01/2020 09:43, Malte Meyn wrote: Am 25.01.20 um 08:12 schrieb Werner LEMBERG: Before adding it to the bug tracker I want to check this group's knowledge whether there is a reason that French beams are longer than normal:    \relative c'' { r16 f d f \override

Re: regression: assertion

Hello, On 27/12/2019 19:19, lilyp...@de-wolff.org wrote: > Code below works fine when run under windows in lilypond 2.18.2 > However when running in 2.19.83, or in 2.21.0 (version end November) an > assertion is thrown: > > File: >

Re: Unable to generate output

Hello David, I didn't notice any reply to you on this: On 03/12/2019 09:51, David Honour wrote: Hi, Since I did a system update I've been unable to get a PDF out of lilypond, the smallest example I've found to trigger is: {c} It would appear the ghostscript is unhappy with the postscript in

Re: MacOS 64bit support

Hello Yassine, On 15/12/2019 15:08, Yassine Chbani wrote: Hi all, Lilypond does not currently offer 64bit binaries for MacOS on its download page . These 64bit binaries are however necessary to run Lilypond on the latest macOS Catalina

RE: Windows: XML import problems due to strange blanks in LilyPond 2.19.82 (Win)

Hello, -Original Message- From: bug-lilypond On Behalf Of Urs Liska Sent: 15 January 2019 09:38 To: bug-lilypond@gnu.org Subject: Re: Windows: XML import problems due to strange blanks in LilyPond 2.19.82 (Win) Am 15.01.19 um 10:34 schrieb samaru...@aim.com: > Thank you, Carl, for all

Re: Incorrect example in Vocal Music documentation

On 24/10/14 13:10, Greg Swinford wrote: There is an error in the example given on the following documentation page: http://lilypond.org/doc/v2.18/Documentation/notation/opera-and-stage-musicals#dialogue-over-music \override LyricText.self-alignment-X = #LEFT should read \override LyricText