Re: Automatically adding extender lines in lyrics

> Often, multiple voices in a score have the same lyrics, or the > lyrics have repeating components (such as lines from a poem). Is > there a way to automatically add extender lines to melismata in the > lyrics? Examples, please, both a scan from a real-world example, and ideally some LilyPond

Re: horizontal spacing issue with `keyCancellation`

Some days ago I wrote: > Consider this snippet. > > ```tex > cancellationFirst = > \override Score.BreakAlignment.break-align-orders = > #(grob-transformer 'break-align-orders > (lambda (grob orig) >(let ((vec (vector-copy orig)) >

Re: Forcing custodes to be always placed at the right-hand margin?

> I wanted a more natural text spacing for some chant in modern > notation I am typesetting, using the setting *ragged-right = ##t*. > However, the custodes also moves along with the line, and I would > like it to always be in the same place, at the right-hand margin. > That is, custodes is alway

Re: Cascade Chords

> Is there a special notation for cascade chords (chords played by > adding successive notes )? I could do it by adding a new voice for > each note, but that seems unwieldly and cluttered. https://lsr.di.unimi.it/LSR/Item?id=408 Werner

Re: Collision between accidental and tuplet

> while typing down the score from an old scan, I discovered a > collision between an accidental and a tuplet spanner, or rather the > number in it: > > > \version "2.24" > \language "deutsch" > > \relative c' { > \tupletUp > \times 2/3 { g'=''8 b4 } des8 h~ h4 r4 > } > > > Perhaps this is wo

Re: how to install lilypond version on linux (ubuntu 22.04)

> I managed to build a specific stable lilypond version for my linux > distro (Ubuntu 22.04). Because I can not find the wright > documentation on this subject, I like to know how can I install the > generated build files from my build directory on my linux distro. > When I try to install my buil

Re: Question about \include options

> See for example http://lilypond.org/notation.html, which you reach > by clicking on "details of Notation" at > http://lilypond.org/manuals.html. Could anyone please come up with > a better formulation than "details of ...", since it's far from > intuitive what such a link might contain. Perha

Re: Question about \include options

> It's true that special characters can cause inconsistent results in > almost anything but if you're searching Documentation for a command > that includes them, you expect the search to be 'complete'; i.e., > encompassing all possibities. The thing is that `#f` and `#t` are nothing special; the

Re: Tempo marking doesn't avoid cross-staff slur

> I found a weird behavior -- I don't know if it's worthy of an issue > or not, but here it is: > > The tempo marking will not avoid a slur that goes from staff to > staff. Here is a snippet that shows the problem, and I've attached > an image of it: [...] This issue belongs into the group of

Re: Tempo marking doesn't avoid cross-staff slur

>> This issue belongs into the group of the many cross-staff problems. >> AFAICS, we don't have this particular case covered, so please file >> an issue in the LilyPond tracker. > > For reference, it's : https://gitlab.com/lilypond/lilypond/-/issues/6688 Thanks! Werner

Re: Setting the emoji font

> I want to use emoji within markup, and I can see in the output log > that Lilypond can't find a character in its default emoji font > (Symbola). I can't figure out how to override the default font. LilyPond does *not* have a default emoji font! It is Pango and FontConfig which choose the font.

Re: { } not sounding right.

> Try this with and without the \new Voice commented. > > \version "2.25.12" > > \language "english" > > \score { > %\new Voice > << > {bf bqf bf} > {g gqs g} > >> > \layout {} > \midi {} > } > > Obviously you would need to listen to the MIDI output. This is a limitation of MID

Re: { } not sounding right.

> I have a branch (from a few years ago) where I changed LilyPond's MIDI > microtonality from using Pitch Bends (which is a bad idea when using > chords) to using MIDI 1.0 tuning information. This works fine IIRC as > long as you don't construct chords containing really close notes > (e.g. c and

Re: { } not sounding right.

> I rather thought about Lilypond being able to "look ahead|behind" > like (I imagine is working) the "Melody_Engraver" to harmonise (no > pun intended) the pitch shift up or down decision. > > \language "english" > > In my use case : > - the gqs is the note g pitched upward. > - the bqf is the

Re: Footnote separator line

>> Simply removing \fill-line will shift the line to the left margin, >> leaving the length the same. > > To my eye that looks a lot better. It's really a matter of style. For example, https://tex.stackexchange.com/questions/214644/how-to-add-a-footnote-separator-rule shows a footnote rule exac

Re: Incipit with default noteheads possible?

>> This works for the note heads, but if there happen to be >> accidentals around (in my project this is the case), they remain >> mensural style. Is there another override for this, too? > > How about this? Nice! David, what do you think about converting this code into a proper MR? Wern

Re: slur to middle of triplet causes warning

> I am trying to slur to the middle of a triplet, which engraves > correclty , but gives a warning. I'd like to get rid of the warning > for a clean build. > > Any solution? > >(e4 d e d | > \tuplet 3/2 {e8 d) b~} b4 r2 | Wrong syntax: Not `(e4` but `e4(`. Werner

Re: bookOutputName seems broken in 2.25.12

> I've tried both of the methods of naming an output file in the book > environment. \bookOutputSuffix works fine. Please give complete examples – I can't reproduce the issue (with current git). I've tried ``` \book { \bookOutputName "Comin-Home-Baby_Tenor-1" { c'4 } } ``` and ``` \book

Re: Make D.S. and Coda objects RED

> I found how to color certain objects, such as with: > > \override Staff.TimeSignature.color = #(rgb-color 1 0 0) > > but I have yet to find the names of the objects I'm hoping to change. Have a look at https://lilypond.org/doc/v2.25/Documentation/ly-examples/visualindex.pdf Werner

Re: tied sharps after line break

> 2. LilyPond's default behaviour in this situation is (in my opinion) > sub-optimal. It's a bug known since 15 years... https://gitlab.com/lilypond/lilypond/-/issues/649 Werner

Re: Using old definition of bass figures for 6\\, 7\\, 9\\ ...

> The special font figures introduced with 2.24 breaks old typesets > using fonts provided by https://github.com/OpenLilyPondFonts > > Is there a way to switch to the old behaviour? Please provide a (small, working) example of the problem you encounter. Werner

Re: Using old definition of bass figures for 6\\, 7\\, 9\\ ...

> adapted sample from > https://lilypond.org/doc/v2.24/Documentation/bd/lily-a6a3b6ba.ly: > > \paper{ > #(define fonts > (set-global-fonts > #:music "paganini" > )) > } > \figures { > \set figuredBassPlusDirection = #RIGHT > <7\\ 6 4 2\+> <4\+ _-> <3 5\+ 3 > <6\\ 4 3> <9\\>

Re: Best way to center beam between upper/lower staff?

> I'm trying to have some notes cross from the lower staff to the > upper staff but want the beam to automatically center. In my > example this is accomplished in measure 3 with much manual work. Is > there a better way? No, there isn't – in general, how shall LilyPond know which note belongs t

Re: Control breaks in staff that I get from a variable?

>> The classic fix is >> >> << >> \new Devnull { s1*5 \break } >> \staffIGot > > This was exactly what I was after. It’s nice and simple and works > well. Thank you. > > I might wish for it being better documented. I see Devnull > documented well in the Internals Reference, but I didn’t readi

Re: Compress Long Rest in Jianpu.

> I want to display both staff and jianpu, but if I enable > \compressMMRests function, the long rests are not compressed when > engraving with jianpu. > > Jianpu support for Lilypond is from file jiapu10a.ly on > https://github.com/nybbs2003/lilypond-Jianpu . Is there any way to > patch the fil

Re: Compress Long Rest in Jianpu.

[Please always reply to the list!] > Sure, it looks like this > [image: image.png] > and this > [image: image.png] > > seems like it just copies the staff style and removes staff lines. OK, thanks. The un-compression of MM rests is an intentional feature of `jianpu10a.ly`. You should contact

Fw: Compress Long Rest in Jianpu.

[Forwarding private message to have the whole conversation in the archive.] --- Begin Message --- Sure, it looks like this [image: image.png] and this [image: image.png] seems like it just copies the staff style and removes staff lines. Windy Werner LEMBERG 于2024年3月24日周日 01:23写道： > &g

nested \set ?

LilyPond provides `\temporary` and `\revert` to set a grob property temporarily, and afterwards the value of the grob property is the same as before. Is there a similar possiblity for `\set` (or something usable in Scheme)? I guess not, but I couldn't find this documented somewhere... Wer

Re: nested \set ?

>> LilyPond provides `\temporary` and `\revert` to set a grob property >> temporarily, and afterwards the value of the grob property is the >> same as before. >> >> Is there a similar possiblity for `\set` (or something usable in >> Scheme)? I guess not, but I couldn't find this documented >> so

Re: nested \set ?

> > Yes, thanks, but this is not what I'm looking after: At the start > > of my function (created with `define-music-function`), > > `\autoBeamOff` gets called (i.e., the `autoBeaming` context > > variable is set to `##t`), and after the function returns the > > previous value of `autoBeaming` shou

Re: nested \set ?

>> LilyPond provides `\temporary` and `\revert` to set a grob property >> temporarily, and afterwards the value of the grob property is the >> same as before. >> >> Is there a similar possiblity for `\set` (or something usable in >> Scheme)?  I guess not, but I couldn't find this documented >> s

Re: nested \set ?

Dear Valentin and Aaron, > properties handle this by having internally not a single value, but > a list of values, and temporary overriding simply means adding to > that list. Context properties do currently not allow for this > mechanic, but we could simulate it ourselves: [...] Both of your

Re: a small correction in arithmetic expressions

> Here is a small correction in the documentation which does not affect > the use of Lilypond, just for the sake of correctness of the > formulas... [...] Thanks, this is now part of a merge request, see https://gitlab.com/lilypond/lilypond/-/merge_requests/2291 Werner

tremoli under beam

Please have a look at the attached image (from the full score of Stravinsky's Firebird, after rehearsal number 32). How do I correctly notate this in LilyPond? AFAICS, there is no real support for that – at least the 'most natural' way to notate it fails with warnings. I could only manage to wr

Re: tremoli under beam

>>> \repeat tremolo 4 { e32[ c! } >> >> >> Don't you want "\repeat tremolo 2" instead of 4? Thanks, yes, of course, but the result is still not correct, as you've found out. Werner

Re: tremoli under beam

Don't you want "\repeat tremolo 2" instead of 4? >> >> Thanks, yes, of course, but the result is still not correct, as >> you've found out. > > Very much not correct! This seems like a bug, no? Let's say it's not supported right now. Filed as https://gitlab.com/lilypond/lilypond/-/iss

Re: Installing 2.24.1

>> There is a web page that deals with command-line installation, if >> that's what you want: >> >> https://lilypond.org/doc/v2.24/Documentation/learning/command-line-setup >> > Thanks. So basically "yes", I guessed as much. > > I just need to re-associate the new version of lilypond with .ly >

Re: Overriding default text of \f, \p, etc.

> However, trying to define f = #(make-dynamic-script ...) doesn't work > because Lilypond interprets f as a note-name. Try ``` "f" = #(make-dynamic-script ...) ``` Werner

Re: PianoPedalBracket.to-barline doesn't always work as expected

> Might I suggest that “to-barline” is potentially > misleading/confusing…? > > On the other hand: > > end-at-barline, for a pedal coded for release on a note **just > after** a barline, might be more clearly descriptive of the > current behaviour; and > > extend-to-barline, for a

Re: Transparent box around notes

> [...] the snippet is _very_ useful, and certainly much easier to use > than the lsr snippet. Please submit the example as a new LSR snippet. Note that we already have a (slightly different) issue for that: https://gitlab.com/lilypond/lilypond/-/issues/833 It would certainly help if you co

Re: Frescobaldi ... panic alternatives?

> With not too much work, you could get emacs to do all of that I > think. Well, it would be great if someone could convert the LilyPond mode of Emacs so that it uses the new 'tree-sitter' interface: https://tree-sitter.github.io/tree-sitter/ (look at the 'Playground' link to get a feeling w

Re: Frescobaldi... panic alternatives?

> Yes, I also use that combo. It's fantastic, but you'd have to be > willing to invest some time to climb the admittedly steep learning > curve of (neo)vim. However, it's a time investment that pays off > massively, so I recommend it heartily! Maybe one of you two can provide some text for ht

Re: Frescobaldi... panic alternatives?

>> Maybe one of you two can provide some text for >> >>https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > > It happens that my first contribution to the Lilypond documentation > was a rewrite of the Easier Editing section, some 14 years ago or > so. Aaah :-) > If either or b

Re: how difficult would it be to have “auto-correct spacing” (even for just a single measure)?

> If you look at the first measure of the third system, you can see > that the note spacing is distorted by various things (lyrics, > accidentals, etc.). But clearly there’s more than enough horizontal > room to make those eighth notes absolutely even — in fact, that kind > of thing is what the ma

Re: how difficult would it be to have “auto-correct spacing” (even for just a single measure)?

>> You are aware of https://lsr.di.unimi.it/LSR/Item?id=1154 ? > > Oh! I vaguely recall that. Thanks for the reminder. > > I believe I applied it to my score, but it didn‘t make a change in > m7. It might be because of the accidentals…? (See modified snippet > acting as MWE, below.) Unfortunatel

Re: Tie between staves of a PianoStaff

> Thanks for your contributions. They inspired me to an easy bypass: > ties may not work between staves, but slurs do, and the difference > is not really conspicuous. [...] By the way, the original problem is an ooold bug: https://gitlab.com/lilypond/lilypond/-/issues/555 Werner

strange chord

I tried the following ``` \version "2.25.16" chord = \chordmode { c4:6-^1 } << \new ChordNames \chord \chordmode { \chord } >> ``` and got the attached result. The displayed chord name looks weird to me, but I'm no expert for Jazz chords... Is it correct? If not, how should it be displ

Re: strange chord

> I tried the following > > ``` > \version "2.25.16" > > chord = \chordmode { c4:6-^1 } > > << > \new ChordNames \chord > \chordmode { \chord } > >> > ``` > > and got the attached result. The displayed chord name looks weird > to me, but I'm no expert for Jazz chords... Is it correct? If no

Re: strange chord

> I mean… technically, it’s correct… Thanks. > but yuck. :-) > If I were customizing the name, I would probably have it say > Em(addb4). At the very least it should say Emsusb4. As chord names noob I have no opinion to that. I just wanted to ensure that MR !2335 produces correct results, e

Re: Scoop (jazz notation)

> I agree with Tim. It's one of those frequently used jazz-isms that > lilypond doesn't handle very elegantly. What's the procedure for > submitting a feature request like this? You might expand https://gitlab.com/lilypond/lilypond/-/issues/529 with comments – and images of professionally t

Re: Moving dynamics onto the staff

>> > So why would overriding the dynamic line spanner's >> > outside-staff-priority change where the forte goes? Isn't it >> > DynamicText? If anyone can clear this up for me, I would be very >> > appreciative. >> >> When there are consecutive dynamics like \p \< ... \f \> ... \pp, >> they need

Re: Moving dynamics onto the staff

> Interestingly, the following does *not* work, [...] It's not clear to me how the end result should look like. > The dynamics context doesn't know that there's a staff above it > and/ot the piano staff forbids the dynamics from encroaching on the > staff above. You want to position the 'f' si

Re: vertical spacing between systems for only part of a score

> I would like to increase the vertical distance between systems for a > specific area in a score. > > I know how to change vertical distance by using the \paper > {system-system etc... route, but that governs the entire score. Here, > I want to make 7 lines spread out to fill the entire last p

Re: vertical spacing between systems for only part of a score

>> Here, I want to make 7 lines spread out to fill the entire last >> page, but leave the other pages alone. Ah, I missed 'last page'. Perhaps all you need is ``` \paper { ragged-last-bottom = ##f } ``` Werner

Re: Stem disappearing

> I am typesetting a piece and the stem in the first e quarter note > disappears when I add \slurUp upper notes. Is this a bug? This is the default behaviour of LilyPond: unify stems. What you need to do is to tell LilyPond not to use `\voiceOne` (up) and `\voiceTwo` (down) but rather `\voiceTw

Re: Stem disappearing

>> I am typesetting a piece and the stem in the first e quarter note >> disappears when I add \slurUp upper notes. Is this a bug? > > This is the default behaviour of LilyPond: unify stems. What you need > to do is to tell LilyPond not to use `\voiceOne` (up) and `\voiceTwo` > (down) but rather

Re: vertical spacing between systems for only part of a score

[Please always use 'reply to all'; I've now CCed the mailing list again.] > >>> Here, I want to make 7 lines spread out to fill the entire last > >>> page, but leave the other pages alone. > > > > Ah, I missed 'last page'. Perhaps all you need is > > > > ``` > > \paper { > > ragged-last-botto

Re: Removing the change clef in a first ending (volta 1)

> > is there a way to get rid of the bass change clef indicator in the > > first ending? > > \once \set Staff.explicitClefVisibility = #end-of-line-invisible > before your \break at the end of volta 1. This information should probably be added to the NR, together with an example. Can you prepa

Re: Removing the change clef in a first ending (volta 1)

>> This information should probably be added to the NR, together with >> an example. Can you prepare a patch (or even an MR) or formulate >> something that I can then massage accordingly? > > Actually this is already in NR 1.1.3 Clef (not specific to volta, > but actually Lily's default kind of

Re: Graphical markup between objects?

> > Before you go create something yourself, have you looked at what > > LilyPond supports [1]? There are built-in options to change the > > style of the FingerGlideSpanner. Your "V"-bend shape probably > > could be added as a new style. > > This is exactly what I was looking for! I was unaware

Re: Graphical markup between objects?

> I was looking for something like "shift line" or "line between > fingerings", the latter of which seems to point to the correct page. https://gitlab.com/lilypond/lilypond/-/merge_requests/2357 Werner

Re: how to draw lines independent from the notes

> How can I draw a vertical (or even diagonal) line independently > positioned from the notes in the score, that can span across staves, > as shown in the figure? The question is formulated in a very broad way. Assuming that you want to draw something completely independent of the score, you mi

Re: Position of nested tuplet brackets

> It seems that the positions of nested tuplet brackets can only be changed > separately if the inner n-tuplet brackets do not start on the downbeat. > > Take this as an example: > > \version "2.25.2" > > { > \once \override TupletBracket.positions = #'(6 . 6) > \tuplet 5/4 { c'4 c' c' c' c'

Re: Regular Polygons

> I was playing around with drawing regular polygons, which led to > creating a new markup command with several configurable options. > (Some of these options are inherited via the built-in \polygon > command.) > > There might be a few things to tighten up, but I believe it is in a > pretty work

Re: Regular Polygons

> Thankfully, it should be trivial to make the changes. The question > now is what reference glyph is the best? If you have an argument, the shape should enclose it symmetrically (more or less) – it is up to you how sophisticated the algorithm is to do that in the visually most pleasing way (i.

Re: color text in markup

> Tell me how to make the first letter in the \markup department red. > > d4^\markup { "Tell me how to make" } d4 Try ``` { d'4^\markup \concat { \with-color #red T ell " me how to make" } d'4 } ``` Werner

Re: color text in markup

> I really need to be able to make the first syllable of a word, the > beginning of a sentence of a song or a romance or a psalm in red or > any other color for my next sets of notes. It is very much requested > that you teach me how to do this. As the specificity of my set will > often meet with

Re: search term

> Which term in the notation index would take me to instructions for > > Cresc. - - -- -- ff Have you *really* tried to search in the index of the Notation Reference? There is an entry for a keyword called `\cresc` (properly sorted as 'cresc'). If you follow that link, y

Re: hairpin over bar line and over end of line

>> How would I have found that in the documentation? > > It's in the "expressive marks" snippets, though I admit I couldn't > have found it myself without searching the docs source code. Could you suggest index entries that I can add to the NR? Werner

Re: hairpin over bar line and over end of line

> >> It's in the "expressive marks" snippets, though I admit I > >> couldn't have found it myself without searching the docs source > >> code. > > > > Could you suggest index entries that I can add to the NR? > > Thank you for following up on this. Paul, the question is addressed to you, too :-

Re: Spanner start and end in different voices or hack

> I’d like for the bracket to extend to the end of the bar. [...] If you use `<< { } // { } >>`, the voices are using names '0', '1', etc. However, if you use `<< { } \new Voice { } >>`, the name of the first voice in `<<>>` doesn't change. This might lead to the following solution. ``` \vers

accessing markup properties via \tweak?

Folks, is it possible to access markup properties like `baseline-skip` via \tweak? It is often necessary to define a markup command that gets in turn wrapped into a music function, and for such situations a tweak-like command would be quite handy. In the example below, I want to set the markup

Re: accessing markup properties via \tweak?

Hello David, >> is it possible to access markup properties like `baseline-skip` via >> \tweak? > > Have you tried? Well, yes, but ... > Check out the following example where I just add a few lines in > front of what you wrote: ... it didn't occur to me to go this route. Thanks a lot! Rega

Re: accessing markup properties via \tweak?

>> In the example below, I want to set the markup property `bar` as a >> tweak to influence `\foo`. > > you could of course do something like > > %%% > #(define-markup-command (foo-markup layout props) () >#:properties ((bar #f) (details '())) >(interpret-markup > layout props > #

Re: accessing markup properties via \tweak?

>> Ah, yes, I forgot that it is possible to extend the `props` alist. >> Thanks a lot! > > This is not exactly extending the probs, but passing additional > parameters in details. Yep, I answered too quickly and was too lazy to correct myself :-) > It would be great to generally have a grob pr

markup function accepting either markup or markup list as argument

Folks, I would like to write a markup function that can either accept a markup or a markup list as an argument. The code below works fine, reporting ``` bar: (#) baz: 1 bar: ((#) (#)) baz: 1 ``` as expected. (The `baz` argument is inserted in the demo code to avoid interference with L

Re: markup function accepting either markup or markup list as argument

> The documentation clearly states: > > > >Arguments are distinguished according to their type: >• a markup, corresponding to type predicate ‘markup?’; >• a list of markups, corresponding to type

Re: markup function accepting either markup or markup list as argument

>> I want to write a user-friendly markup command that can accept either >> a markup or a markup list as arguments. Example: >> >> ``` >> % \ornament >> \markup \ornament \number ♭ >> \musicglyph "scripts.turn" >> \number ♮ >> \markup \ornament { \number ♭ \

Re: LSR down?

> The LSR looks like it's down. I don't know who is responsible for > it so I thought I'd just post here. Thanks. I've written an e-mail to Sebastiano. Werner

Re: LSR down?

>> The LSR looks like it's down. I don't know who is responsible for >> it so I thought I'd just post here. > > Thanks. I've written an e-mail to Sebastiano. And its online again. Werner

Re: Vertically align objects of same class?

> I have a bunch of objects of the same type that I’d like to all be > aligned to the same Y-level on a per staff basis. Increase the `staff-padding` property. Werner

Re: Vertically align objects of same class?

> Knute, to your point I think that the Dynamics context, while > slightly better than lyricMode for this use case still has a similar > issue given that the project I'm working on is of considerable size > and would require a significant refactor. Feasible but I'd like to > avoid doing this if at

beam subdivision problem

Folks, how can I easily create a beam subdivision as shown in the attached image using the current development version 2.25.18? The solution I came up with is extremely ugly... Werner ``` { \once \set subdivideBeams = ##t \once \set minimumBeamSubdivisionInterval = \musicLength 8

Re: beam subdivision problem

Hello Jason, > > ``` > > { > > \once \set subdivideBeams = ##t > > \once \set minimumBeamSubdivisionInterval = \musicLength 8 > > f'16 f'32 > > \set stemRightBeamCount = 2 > > f' > > \set stemLeftBeamCount = 2 > >f' f' f' f' > > } > > ``` > > Looks

Re: beam subdivision problem

> My reading would be > > \version "2.24.3" > \relative c'' { > d4 r16 f d b g'4~ g16 a c a64 (g fis g) | > } > > It corrects only one beaming "error", is more rhythmically > consistent, and might be more in keeping with the context. Thanks, but I'm not typesetting the sonata :-) It would be

Re: beam subdivision problem

> This may be slightly less ugly, but it still requires a function > call every place you want a beam subdivision: Thanks! Werner

Re: beam subdivision problem

> I have thought of a probably better solution. Currently, if > `minimumBeamSubdivisionInterval` > `maximumBeamSubdivisionInterval`, > the algorithm basically pretends that `subdivideBeams` is false. > What if I change the behavior of that case such that you can add > `maximumBeamSubdivisionInterv

Re: French lyrics and accented characters

> Anyhow, I persist in my opinion that facilitating the input of > accented characters is best done at a level different than LilyPond. +1 Werner

Re: French lyrics and accented characters

> And so while I do agree that if the problem can be solved before > Lilypond actually matter, then great. But if this does not work out > to you, then nothings wrong with getting Lilypond to help you out. Certainly! However, this shouldn't become part of LilyPond IMHO; it's opening a can of wor

Re: French lyrics and accented characters

>> Certainly! However, this shouldn't become part of LilyPond IMHO; >> it's opening a can of worms since all those sets are essentially >> open-ended – "why is character 'fronz with grmpf above' not part of >> this or that set?" > > Yes, but here the extensibility comes into play. If you want to

Re: beam subdivision problem

>> The Alain and Rachmaninov only have one fewer beam, so the beam >> count between the groups is not appropriate for the lengths of the >> subdivided groups, according to the Gould rules.  Personally, I >> think the Gould rules are correct, but two of the music publishers >> in your example do no

Re: French lyrics and accented characters

>> As you mention 'snippet': The right place for this is the LSR, I >> believe. > > Definitely, yes. But I don’t dislike the idea of having some more or > less standard LSR snippets for people who want something like this. Having a 'standard LSR snippet' is certainly a good thing since we then c

Re: Suggestion for LSR #304

> I came across LSR #304 https://lsr.di.unimi.it/LSR/Item?id=304 and I > think we should suggest a coding with variables there, like this: > [...] Yes, LilyPond should be both more supportive and more 'user friendly' here; this is tracked as https://gitlab.com/lilypond/lilypond/-/issues/6525

Re: Changes in notation font in 2.25

> The reason is, it appears that old notation fonts have become > slightly broken, especially glyphs relating to numbers (time > signatures, multi-measure rests, figured bass). The attached files > are rendered in 2.25.2 and .16 using > https://github.com/OpenLilyPondFonts/cadence . I've just tri

Re: Changes in notation font in 2.25

> In this example, I cloned the directory of the git repository, then > included the /otf directory like this: > > ~/lilypond-2.25.17/bin/lilypond -I /path/to/cadence/otf/ -dcrop -o > cad_new cad.ly > > Does this look correct? No, it is not correct. Option `-I` is for LilyPond input files and

'cloning' Voice properties

Folks, consider the following snippet. ``` \version "2.25.18" foo = #(define-music-function () () #{ << c'4 \new Voice { g''4 } >> #}) { \override Staff.NoteColumn.ignore-collision = ##t c'4 \foo \stemUp \foo \stemDown \foo } ``` As can be seen, the `\new Voice` d

Re: Matching Lilypond and Word font sizes

> Tell me where you can find out or see how the font sizes in > lilypond and Word correspond. For example, \SetFontSize = #1, What is `\SetFontSize`? > \abs-font size #1, how do they match the font size in Word? If you use `\abs-fontsize`, you get a font size (in markups) in points regardl

Re: Suggestion for LSR #304

> Also, I’m sure you didn’t mean it that way, but the improvement to > the LSR snippet is worthwile regardless, I think. Yep. > Going to greater lengths though—while reading your code I wondered > whether it wouldn’t make sense to go the step of not taking strings > as arguments (specifying the

get interval size of chord in music function

I want to find the interval size of a two-note chord in a music function, and I came up with the following solution. ```tex showInterval = #(define-music-function (ev-chord) (ly:music?) (define (interval-string a b) (number->string (1+ (ly:pitch-steps (- b a) (let* ((notes (ex

Re: 'cloning' Voice properties

> ``` > \version "2.25.18" > > foo = > #(define-music-function () () > #{ > << > c'4 > \new Voice { g''4 } > >> > #}) > > { > \override Staff.NoteColumn.ignore-collision = ##t > c'4 \foo \stemUp \foo \stemDown \foo > } > ``` > > As can be seen, the `\new Voice` doesn't

<    3   4   5   6   7   8   9   10   11   12   >