Re: rehearsal marks, top-staff lyrics, and moved engravers

>> the snippet below demonstrates that top-staff lyrics are >> incorrectly positioned above rehearsal marks if the engraver for >> the latter is moved to another context (I need that in a full score >> with rehearsal marks printed simultaneously at three different >> vertical positions). > >

Re: rehearsal marks, top-staff lyrics, and moved engravers

> I think you likely want to move the Mark_engraver to a kind of > MarkLine context instead. Well, the problem is that such a context needs the `Axis_group_engraver`, which tries to align stuff horizontally on a line. I don't want that. Rehearsal and tempo marks should be aligned on the

rehearsal marks, top-staff lyrics, and moved engravers

Dear LilyPonders, the snippet below demonstrates that top-staff lyrics are incorrectly positioned above rehearsal marks if the engraver for the latter is moved to another context (I need that in a full score with rehearsal marks printed simultaneously at three different vertical positions).

Re: vertical half-brackets

>> * Has someone coded this already? I couldn't find code in the LSR. > > I don't know if this is still the most ideal way, but it works. > [...] Thanks a lot for all the replies! I'll analyze them and cook something up for my needs. Werner

Re: vertical half-brackets

>> For piano music it is common to indicate the use of the right hand in >> the lower staff with a 'half-bracket' [...] > > In the NR I find > > Indicating cross-staff chords with arpeggio bracket [...] > > It's not a half-bracket but it's the closest in the manual I can > find at a glance.

Re: vertical half-brackets

> * What's the right term for this 'half-bracket'? BTW, in SMuFL this symbol is called 'keyboardPlayWithRH' :-) https://w3c.github.io/smufl/latest/tables/keyboard-techniques.html Werner

vertical half-brackets

For piano music it is common to indicate the use of the right hand in the lower staff with a 'half-bracket' (and vice versa for the upper staff), see image. Two questions. * What's the right term for this 'half-bracket'? * Has someone coded this already? I couldn't find code in the LSR.

Re: Piano pedalling in (conductor) scores

> Well, just look at a Mahler score. He was one of the great > conductors, and the strings are full of bowing marks. How many of > them are followed by conductors these days I don't know. Well, just look at a Richard Strauss score :-) His scores are full of legatos in the strings which are

Re: make \breath (kind-of) ignore clef change

>>> Please have a look at the attached image. What must I do to make >>> the breathe sign 'ignore' the change clef so that the breathe sign >>> is positioned as if the change clef wasn't there? [...] > > There's always this sort of trick: [...] Excellent, thank you! > Is this canonical

Re: make \breath (kind-of) ignore clef change

> [git f326290b65351] > > Please have a look at the attached image. What must I do to make > the breathe sign 'ignore' the change clef so that the breathe sign > is positioned as if the change clef wasn't there? Well, having some code certainly helps :-) ``` { 1 \breathe | } { 1 \breathe

make \breath (kind-of) ignore clef change

[git f326290b65351] Please have a look at the attached image. What must I do to make the breathe sign 'ignore' the change clef so that the breathe sign is positioned as if the change clef wasn't there? Werner

Re: printing "a 2" at the beginning of staves automatically

>> * Contrary to Valentin's solution, the first 'a 2' text is not >> left-aligned to the left edge of the note head. This is >> especially visible with whole notes (see attached image). [...] > > See the attached file, fixing that problem and making it per-voice. Thanks, will test soon in

Re: `StaffGroup` prevents articulation shifted under time signature

> dynamicLengthOff = { > \override DynamicText.extra-spacing-width = #'(+inf.0 . -inf.0) > \override DynamicText.extra-spacing-height = #'(0 . 0) > } Nice idea, thanks! Werner

Re: `StaffGroup` prevents articulation shifted under time signature

>> The following example >> >> ``` >> << >>\new Staff { f'1 } >>\new Staff { f'1 \tweak X-offset #-5 \pp } >> \new StaffGroup << >>\new Staff { f'1 } >>\new Staff { f'1 \tweak X-offset #-5 \pp } >> ``` >> >> shows that I can't move the 'pp' to sit under the time signature if >> I

`StaffGroup` prevents articulation shifted under time signature

[LilyPond version 2.23.9] The following example ``` << \new Staff { f'1 } \new Staff { f'1 \tweak X-offset #-5 \pp } >> \new StaffGroup << \new Staff { f'1 } \new Staff { f'1 \tweak X-offset #-5 \pp } >> ``` shows that I can't move the 'pp' to sit under the time signature if I use

Re: printing "a 2" at the beginning of staves automatically

>>> Meanwhile, how about using a spanner rather than an item? See >>> attached. > > Aaand some nits :-) I forget another one. * If you look at the attached image (from 'Carmina burana') it probably makes sense to have the staff annotation engraver actually live in the Voice context. We

Re: printing "a 2" at the beginning of staves automatically

>> Meanwhile, how about using a spanner rather than an item? See >> attached. Aaand some nits :-) * Contrary to Valentin's solution, the first 'a 2' text is not left-aligned to the left edge of the note head. This is especially visible with whole notes (see attached image). It is not

Re: printing "a 2" at the beginning of staves automatically,Re: printing "a 2" at the beginning of staves automatically

> I’ve changed it up so that the a2 is always aligned to the note when > it is set. This also solves the first one not being printed. Thanks! Werner

Re: printing "a 2" at the beginning of staves automatically

> Meanwhile, how about using a spanner rather than an item? See > attached. Very nice, thanks! Besides the (hopefully) harmless warning ``` programming error: Spanner `TextSpanner' is not fully contained in parent spanner. Ignoring orphaned part continuing, cross fingers

Re: printing "a 2" at the beginning of staves automatically

> Basically, it works great, but there are two problems (tested with > 2.23.9). > > * It doesn't print 'a 2' at the very beginning. > > * Contrary to `\mark`, the 'a 2' should always be horizontally > aligned to a note column and not to prefatory matter like time or > key signatures. And

Re: printing "a 2" at the beginning of staves automatically

> The optimal solution (IMO) would be to improve the whole instrument > definition, switching, and [staff-]labelling framework such that > \addInstrumentDefinition and \instrumentSwitch would change the > appropriate texts so that the engraver(s) could present the > information automagically

Re: printing "a 2" at the beginning of staves automatically

>> while it is probably not the best way to do it, here is a >> pragmatical solution to the problem. > > Thanks a lot! Will try it soon. Basically, it works great, but there are two problems (tested with 2.23.9). * It doesn't print 'a 2' at the very beginning. * Contrary to `\mark`, the 'a

Re: printing "a 2" at the beginning of staves automatically,Re: printing "a 2" at the beginning of staves automatically

> while it is probably not the best way to do it, here is a > pragmatical solution to the problem. Thanks a lot! Will try it soon. Werner

Re: LilyPond 2.23.9 released

>> Note that the MacPorts port of LilyPond 2.22.2 already uses Guile >> 2.2 bytecode and provides a binary for Apple Silicon, too. >> >>   https://ports.macports.org/port/lilypond/details/ > > No, the 2.22.2 version uses Guile 1.8 as can be easily seen from the > dependencies. Even if it used

Re: LilyPond 2.23.9 released

>> Currently homebrew provides Lilypond 2.22.2 for Apple Silicon, >> that is what I am using. > > Did you try running the x86_64 binaries via Apple's Rosetta tool? That > might be a bit slower than native executables, but given that Homebrew > builds 2.22.2 without Guile bytecode, it might

printing "a 2" at the beginning of staves automatically

Let's assume that I have 40 bars of flute 1 and 2 in a single staff of a full score. At the very beginning of these bars I write "a 2", and I want this remark repeated at the beginning of every staff where this is still true. [Obviously I'm not using `\partCombine` :-)] Has anyone already set

Re: within \markup, how to \translate by width of another markup?

>> AFAICS, we are back to square one, needing the possibility to >> `\translate` something by the width of another markup. I will cook >> something up and see how well it works. > > > Probably > > ``` > \version "2.22.2" > > #(define-markup-command (translate-by-extent-of layout props axis

Re: within \markup, how to \translate by width of another markup?

> Sth like > > \markup \box \number \column \with-dimensions-from \right-align "0" > \right-align { 11 10 6 5 4 3 2 1 } While this is an ingenious solution – thanks! – it doesn't fit my needs, alas, since two-digit numbers stick out to the left of the box. This is exacerbated by the fact that

Re: within \markup, how to \translate by width of another markup?

>> * Single-digit numbers are left-aligned. > > Why? They have equal width. Do you rather mean that the reference > point is supposed to be on the left edge? Yes. Sorry for the sloppy wording. > What is the alignment supposed to be if there are _only_ two-digit > numbers? This situation

Re: within \markup, how to \translate by width of another markup?

> Again, I have no idea what you are trying to achieve here and how > kerning has anything to do with it. OK. Next try. Here are the assumptions. * Numbers 0, 1, 2, ..., 9 all have a width of 100 units. * Number 10, however, has a kerning of -50 units between digits 0 and 1, making a total

Re: within \markup, how to \translate by width of another markup?

The problem at hand is stacking fixed-width single-digit and two-digit numbers. Single-digit numbers should be left-aligned for various reasons: ``` 9 8 7 ``` If there is a two-digit number, it should be right-aligned at the

Re: within \markup, how to \translate by width of another markup?

> How about > > \markup \typewriter \column { 9 \general-align #X #CENTER 10 } Nope, this doesn't align properly – see my answer to David's e-mail for a longer explanation. Werner

Re: within \markup, how to \translate by width of another markup?

>> The problem at hand is stacking fixed-width single-digit and >> two-digit numbers. Single-digit numbers should be left-aligned for >> various reasons: >> >> ``` >> 9 >> 8 >> 7 >> ``` >> >> If there is a two-digit number, it should be right-aligned at the >> right edge of the left-aligned

Re: within \markup, how to \translate by width of another markup?

>> Within a markup, I want to `\translate` an object by the x-extent >> of another markup. How can I do that? >> >> While we have `\with-dimensions` and friends to adjust the size of >> an object, it seems to me that we don't have something similar for >> offsets... Would it be necessary to

within \markup, how to \translate by width of another markup?

Within a markup, I want to `\translate` an object by the x-extent of another markup. How can I do that? While we have `\with-dimensions` and friends to adjust the size of an object, it seems to me that we don't have something similar for offsets... Would it be necessary to define

Re: An issue with kerning in a defined dynamic "sfffz" solved

> Some time ago I wrote saying that I could not get the marking > "sfffz" to kern properly. Someone replied that it did for them, and > I let it sit there, waiting until I needed a solution, which point I > have now reached. I have been slow and dense in recognising where > the issue lies - I

Re: top-level markup in Scheme

>> On the other hand, a LilyPond input file containing only >> >> ``` >> #(make-italic-markup "foo") >> ``` >> >> prints nothing. I now wonder how I can modify the latter to make >> it actually work – what is the 'appropriate hook'? > > s/#/$ This did the trick, thanks! Reading the

Re: top-level markup in Scheme

>> What is the Scheme equivalent to a top-level markup like >> >> ``` >> \markup \italic "foo" >> ``` >> >> ? I can't find it in the documentation. > > I am not a fan of the markup macro, but of course > > (make-italic-markup "foo") > > will also work. Thanks. > It is not clear what you mean

top-level markup in Scheme

What is the Scheme equivalent to a top-level markup like ``` \markup \italic "foo" ``` ? I can't find it in the documentation. Werner

Re: Annotation brackets,Annotation brackets

> I’ve created some code for creating well behaved annotation brackets > for some SE question, which I want to share with you all in case > someone of you can use it. Very nice! This smells like a good snippet for the LSR :-) Werner

Re: Unwanted font ligature

> I am trying to write the dynamic "sfffz".  But when I write > \markup\dynamic"sfffz" the first sf is made a ligature, then the > last two are made another ligature - the difference in spacing of > the f's is ugly, as in the attached image - is there anything I can > do about it? A quick would

Re: bug in magnetic snapping lyrics engraver

ainly room for improvements. Attached is another version for testing without the need to patch LilyPond. Werner % magnetic-lyrics.ily % % written by % Jean Abou Samra % Werner Lemberg % % Version 2022-Apr-15 \version "2.23.7" #(define (Left_hyphen_pointer_engraver context)

Re: bug in magnetic snapping lyrics engraver

>> Attached. In the end the necessary modifications were surprisingly >> minor. Please comment, there is certainly room for improvements. > > Thanks. This is a bit what I feared: in this state, there is > potential for things going wrong with other after-line-breaking > callbacks. Those are

Re: bug in magnetic snapping lyrics engraver

> How did you do that? Sorry to rain on your parade, but I would not > want you to put a lot of work in it if it will not be of mergeable > quality. Attached. In the end the necessary modifications were surprisingly minor. Please comment, there is certainly room for improvements. Werner

Re: bug in magnetic snapping lyrics engraver

> There is a problem with ligatures at the syllable boundaries (and > kerning). [...] it is not sufficient to shift the right syllable > in a syllable pair to the left. Instead, the following should be > done. [...] Meanwhile I could implement this :-) I will submit a MR soon. Werner

Re: how to change extents of a grob?

>> Or to ask in a different way: At the time when properties are >> processed and you have to manipulate stencils, changing the stencil >> of a grob doesn't change the extents of this grob, AFAICS. > > You are not supposed to change stencils at all. They are not > entities with identity. > >

how to change extents of a grob?

Dear LilyPonders, I can get the extents of a grob with `ly:grob-extent`. What is the corresponding Scheme function to set the extents? Or to ask in a different way: At the time when properties are processed and you have to manipulate stencils, changing the stencil of a grob doesn't change

Re: bug in magnetic snapping lyrics engraver

>> This is ingenious :-) Thanks *a lot* for this solution. In my >> tests it seems to work fine > > You're welcome. I spoke too soon :-) There is a problem with ligatures at the syllable boundaries (and kerning). While this can be considered an ugliness in languages based on the latin script,

Re: bug in magnetic snapping lyrics engraver

>> Did I miss something? > > Whoops, big problem at line breaks ... This is ingenious :-) Thanks *a lot* for this solution. In my tests it seems to work fine. Two comments. * I *strongly* vote for polishing and documenting this so that it can be added to LilyPond. It's an invaluable

Re: bug in magnetic snapping lyrics engraver

> The second bug is super hard to fix: when you tell LilyPond about > spacing constraints between lyrics, before line breaking, you need > to assume a lyric syllable won't be moved to the left by > 'magnetism', because if you do, the spacer might think it can space > its right neighbor more to

Re: bug in magnetic snapping lyrics engraver

> Here is an example where it fails to position lyrics correctly (see > last system in the image). And while we are at it: Here is another bug, already reported in https://lists.gnu.org/archive/html/lilypond-user/2020-03/msg00289.html I've slightly sharpened the test to exclude the

Re: problem with extending 'magnetic snapping lyrics' engraver

>> but how about just >> changing >> >>    (let* ((hyphen-sten (ly:lyric-hyphen::print hyphen)) >> >> to >> >>    (let* ((hyphen-sten (ly:grob-property hyphen 'stencil)) >> >> >> ? Then you can do \override LyricHyphen.stencil = #what-you-want to >> get the result. > > D'oh, so simple, thanks

bug in magnetic snapping lyrics engraver

ride LyricHyphen.minimum-distance = #0 \override LyricSpace.minimum-distance = #1 } } \version "2.23.7" %% CHANGELOG %% %% 2022-04-21 Werner Lemberg %% %% * Update `add-grob-definition` to make it work with current development %% version (2.23.7). %% %% 2019-05-28 Thomas Morley %% %% *

Re: problem with extending 'magnetic snapping lyrics' engraver

> It's uncomfortable to have grob properties of procedure type, since > they are automatically resolved as callbacks. You set > LyricWord.hyphen-formatter to ly:lyric-hyphen::print. Then, when > you do > >   (ly:grob-property grob 'hyphen-formatter) > > this not only looks up

problem with extending 'magnetic snapping lyrics' engraver

I'm trying to generalize the 'magnetic snapping lyrics' engraver (the most recent version posted as https://lists.gnu.org/archive/html/lilypond-user/2019-05/msg00389.html) by providing a new property `hyphen-formatter`, to be used instead of the hard-coded `ly:lyric-hyphen::print`. Attached you

Re: Feature request: Fix cascading error messages

>> This sounds sensible; maybe this suppression of processing `\score` >> blocks can be implemented in Scheme so that LilyPond with a special >> command line option acts as a syntax checker. > > Have you actually tried? Apart from scores placed in explicit books > and bookparts, LilyPond

Re: Feature request: Fix cascading error messages

> Why make the user wait so long to make him fix a misspelled word or > make him put a curly brace? A first pass should be done without > \score blocks and abort (or at least ask if you want to continue!) > if this first pass produces errors. This sounds sensible; maybe this suppression of

Re: Feature request: Fix cascading error messages

> But shouldn't Lilypond check first if the syntax is correct instead > of spending several seconds/minutes compiling a code that's doomed > to visually fail? Sometimes I want to see the output inspite of errors. Aborting immediately if there is a syntax problem is definitely not always the

Re: Feature request: Fix cascading error messages

> In this context I could imagine a paramater that kind of highlights > the first few error messages (or only shows the first N error > messages) being very forthcoming to some people without a dev > background. Or maybe at the end of the compilation output a clearly > marked: "First (few?)

Re: 'baroque' time signatures

> May be you can use something like: > \override Staff.TimeSignature #'stencil = #ly:text-interface::print > \override Staff.TimeSignature #'text = \markup \musicglyph #"timesig.C44" > \time 4/2 Yes, I thought of that, but... > I'm pretty sure there is a simpler solution, but I don't remember

Re: 'baroque' time signatures

>> In modern transcriptions of baroque music it is custom to use time >> signatures for half the length. For example, if you have 4/2 bar, >> the time signature shows 'C'; if you have a 6/1 bar, the time >> signature shows '3/1'. >> >> Is there a simple way to get the equivalent to the following

'baroque' time signatures

In modern transcriptions of baroque music it is custom to use time signatures for half the length. For example, if you have 4/2 bar, the time signature shows 'C'; if you have a 6/1 bar, the time signature shows '3/1'. Is there a simple way to get the equivalent to the following (invalid)

Re: Should \partial accept music instead of duration?

> A convert-ly rule would probably not be possible given the > limited power of regular expressions. As such, \partial might > need to support both duration and music arguments. Initially I > thought this might not be possible, given that a naked duration > can be treated

Re: `TextSpanner` vs. `DynamicTextSpanner`

>> Sometimes, this would be very helpful, yes (see attached image from >> the last scene of 'Wozzeck'). I guess a possible work-around would >> be to (ab)use `DynamicTextSpanner` for that. > > [...] There is also this kind of code: [...] See issue #3176. Very nice, thanks! Maybe this should

Re: `TextSpanner` vs. `DynamicTextSpanner`

>> Is there a similar auxiliary grob for `TextSpanner`? > > No, since consecutive text spanners are not aligned vertically. > > { > c'1\tweak bound-details.left.text "aaa" \startTextSpan > c'1\stopTextSpan\tweak bound-details.left.text ""\startTextSpan > c'1\stopTextSpan > } > > >

`TextSpanner` vs. `DynamicTextSpanner`

For `DynamicTextSpanner` grobs there exists the auxiliary `DynamicLineSpanner` grob, providing a vertical baseline to align successive dynamic grobs within a staff. LilyPond provides other such pairs like `CenteredBarNumber` vs. `CenteredBarNumberLineSpanner`, or `SostenutoPedal` vs.

Re: skip-of-length and \unfoldRepeats

>>> Now that I know to look for it, the definition of `\skip` in >>> >>> does describe this behavior. But I would never have found this on >>> my own. >> >> OK, how did you search exactly? Where

Re: skip-of-length and \unfoldRepeats

>> In recent versions, like version 2.23.6 which you are using, you >> can use >> >> \skip \musicA >> >> which is nicer syntax-wise and plays well with \unfoldRepeats. > > Now that I know to look for it, the definition of `\skip` in >

Re: Blind and visually impaired users learning LilyPond

> I rather like the idea of there being a section in the documentation > for visually impaired users; I would even be willing to help > contribute to such a section. Excellent, and thanks for the offer. If you find time to write such a section, simply send your suggested text to this list,

Re: edition engraver problems (was: Installing Alternate Music Fonts)

>> I haven't had time to /really/ focus on this and I don't want to >> break everything so what I would like to do is eliminate the >> MacPorts install and do the official install with the 1.8 version >> of Guile (I'm guessing Guile 2.2 is what's breaking the scheme >> functions in Edition

Re: Installing Alternate Music Fonts with Frescobaldi and Homebrew Installation on M1 Mac

> Werner - I've done just that: The file compiles just fine unless I > try to change the font. [...] This very much smells like a bug in LilyPond's font handling, probably specific to the Windows platform (otherwise we would have seen from Abrahan, the author of the Beethoven fonts0. It might

Re: Installing Alternate Music Fonts with Frescobaldi and Homebrew Installation on M1 Mac

>> Werner - I've done just that: The file compiles just fine unless I >> try to change the font. [...] > > This very much smells like a bug in LilyPond's font handling, > probably specific to the Windows platform (otherwise we would have > seen from Abrahan, the author of the Beethoven fonts0.

Re: Installing Alternate Music Fonts with Frescobaldi and Homebrew Installation on M1 Mac

> Looks like it's finding the font in the folder, but then crashing > midway through the build. Here are the last few lines of the verbose > output. > > ``` > Preprocessing graphical objects... > Grob count 1289 > [/opt/local/share/lilypond/2.23.1/fonts/otf/beethoven-11.otf > CFF name for font

Re: Installing Alternate Music Fonts with Frescobaldi and Homebrew Installation on M1 Mac

> Valentin -- That's exactly the path I've been trying to no avail. I > tracked down that folder but the fonts just aren't being recognized > as having been installed. If you call the `lilypond` binary on the command line with ``` lilypond --verbose ``` You can see where LilyPond tries to

Re: Delay for list posts to arrive

>> Lately I've found myself a couple times duplicating answers already >> provided on this list by others up to almost three hours earlier >> because I had not received these replies yet. [...] > > Check the timestamps in the email headers. This tends to be what I > see: [...] There were

Re: Rendering Two Dots Above a Character,Re: Rendering Two Dots Above a Character

> Maybe something like this could work. Nice! Note, however, that Omid uses + + in his input file. This clearly indicates that he wants the dots stacked vertically, not horizontally. Your solution is perfect in case the vertical stacking is not intended – Unicode provides no means to

Re: Rendering Two Dots Above a Character

>> I am trying to create some sort of tablature for Kalimba, treating >> it like a one-string instrument with fret-labels. I want to use >> letters like c, ċ, ċ̇ (or cཉ), etc. I figured there are Unicode >> characters to do exactly that, "combining dot above" and "combining >> two dots above",

Re: Stem length of beamed notes

> \once \override Beam.positions = #'(1 . 0.5) g8 fis > > Indeed, AFAICS this is not clearly documented in the NR manual. Can you provide a patch? Werner

Re: Rendering Two Dots Above a Character

> I am trying to create some sort of tablature for Kalimba, treating > it like a one-string instrument with fret-labels. I want to use > letters like c, ċ, ċ̇ (or cཉ), etc. I figured there are Unicode > characters to do exactly that, "combining dot above" and "combining > two dots above", etc.

Re: fonts on windows

>> Yes, I managed to figure that out. It would be nice if Lilypond >> could find fonts for the current user too. > > Definitely. Looks to be an issue with fontconfig [1] and not > LilyPond. > > [1]: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/144 The issue even has a patch

Re: Tenuto marking too close to note

> I would like to have the tenuto mark a bit farther away from the > note. I had a similar issue with tuplet numbers and then "\override > TupletNumber.Y-offset = #-2.5" fixed the issue. I don't know what I > should replace "TupletNumber" by in the case of tenuto lines. Have a look at this

Re: better control of balloon positioning

>> [...] What must I do to get, for example, >> >>Balloon text >> / >> / >> grob >> >> this alignment? Please advise. > > One solution is to wait for the patch that accidentally I am >

better control of balloon positioning

A balloon's `X-offset` property results in the following three alignments for a given x value. x < 0: Balloon text \ \ grob x = 0: Balloon text | |

Iranian classical music support

Dear LilyPond community, based on Kees van den Doel's `persian.ly`, I've submitted a Merge Request to integrate support for Iranian classical music into LilyPond. https://gitlab.com/lilypond/lilypond/-/merge_requests/1060 Please comment (and ideally, revise)! You have to sign in to

Re: Crescendo after custom dynamic marking

> c): Add \dynamic know and later find a special name for Harm's > dynamic engine. (d) You add now `\dynamic` in a first MR. Eventually, Harm's stuff gets applied in another MR under the same name, extending your stuff.[*] IMHO there is no necessity to provide `convert-ly` rules

Re: Persian accidentals (koron and sori)

> One comment: When looking at Fig. 11 in your PDF, two suggestions > came to my mind. The handwritten accidentials show some less sharp > edges because the ink is flowing in the inner angles of the glyph. > As you already take the liberty to match the style of classical > accidentials, how

Re: Persian accidentals (koron and sori)

>>> https://w3c.github.io/smufl/latest/tables/persian-accidentals.html >> >> Yes, and it is soo ugly. > > It is best consulting some with traditional Persian sheet music. > But the few ones I have seen tend to be hand drawn, not of very high > quality, but similar. > > The accidentals were

Re: Persian accidentals (koron and sori)

>> In case there are experts on Persian music notation: please have a >> look here >> >> https://gitlab.com/lilypond/lilypond/-/merge_requests/1047 >> >> and comment on the design. > > Here is how they look at SMuFL. Rather thin and of equal thickness, > contrary to the standard accidentals.

Persian accidentals (koron and sori)

In case there are experts on Persian music notation: please have a look here https://gitlab.com/lilypond/lilypond/-/merge_requests/1047 and comment on the design. Werner

Re: `\textLengthOn` for `TextSpanner` grobs

>>> Does David N's text-spanner work solve this problem, I wonder? >> What are you referring to? > > https://github.com/davidnalesnik/lilypond-text-spanner-inner-texts This is veeery nice! Thanks for the link. Werner

Re: `\textLengthOn` for `TextSpanner` grobs

Hello Kieren, >>> Use >>> \override TextSpanner.minimum-length = 30 >>> \override TextSpanner.springs-and-rods = #ly:spanner::set-spacing-rods >> Thanks. Alas, doesn't work correctly for broken spanners > > Yeah, I saw that coming… as well as the fundamental > "trial-and-error" problem.

Re: `\textLengthOn` for `TextSpanner` grobs

>> please have a look at this example >> >> ``` >> { >>\set Score.skipBars = ##t >>\override TextSpanner.bound-details.left.text = "poco a poco tempo I" >>\override TextSpanner.bound-details.right.text = "Tempo I" >>R1*4\startTextSpan | >>R1\stopTextSpan >> } >> ``` >> >> What

`\textLengthOn` for `TextSpanner` grobs

Folks, please have a look at this example ``` { \set Score.skipBars = ##t \override TextSpanner.bound-details.left.text = "poco a poco tempo I" \override TextSpanner.bound-details.right.text = "Tempo I" R1*4\startTextSpan | R1\stopTextSpan } ``` What is the equivalent of

\tag and \tweak

This time a syntax question: Is it possible to combine `\tag` with `\tweak`? I have tried the following: g-\tag #'score \tweak X-offset #-3 _\markup { "foo" } | However, this makes the `\markup` disappear if `\keepWithTag` doesn't contain `#'score` (which is kind-of

Re: quoted tuplet bracket within staff

>> Well, you got the wrong property here. outside-staff-priority >> tells how to stack outside-staff objects with one another. What >> you need here is >> >> \override CueVoice.TupletBracket.staff-padding = ##f Aah, I only tried `padding` to no avail. Thanks a lot! > So, Werner, this

Re: quoted tuplet bracket within staff

>> For a general solution, one could probably write a callback for the >> positions property. > > I was hoping to use #'outside-staff-priority to try to allow the > tuplet to float into the staff automatically, [...] Me too. Werner

Re: quoted tuplet bracket within staff

>>\override CueVoice.TupletBracket.direction = #DOWN >>\override CueVoice.TupletBracket.edge-height = #'(-0.7 . -0.7) >>\override CueVoice.TupletBracket.extra-offset = #'(0 . 4.75) >>\override CueVoice.TupletNumber.extra-offset = #'(0 . 4.75) > > Hold the heavy machinery :-). You

Re: quoted tuplet bracket within staff

>> What must I do to make the tuplet bracket be positioned within the >> staff, that is, below the rest? > > There's surely a more elegant way… but if you're stuck, you can > always hack it: [...] Thanks a lot! Of course I would like to have a solution that avoids `extra-offset` :-) > x = {

quoted tuplet bracket within staff

Folks, plesae consider the following example. x = { r2 \tuplet 3/2 { g4 a b } } \addQuote "qx" \x { r2 \cueDuring #"qx" #DOWN { \override CueVoice.TupletBracket.direction = #UP r2 } } What must I do to make the tuplet bracket be positioned

Re: Help

> Nevetheless, in my modest opinion, the easiness of modern notation > in LilyPond would be greatly upgraded if one might take the book of > Edgard Karkoschka on the XX century notation and check out most > common features used by all composers discussed in this very > informative book This is

<    1   2   3   4   5   6   7   8   9   10   >