Re: Jazz chords layout question

Thomas Morley wrote: meanwhile a snippet arrived at LSR caring about indenting individual lines, reflecting the discussion in this thread. Now approved as http://lsr.di.unimi.it/LSR/Item?id=1098 Thanks to the author, You're welcome. Also, feedback welcome! Cheers, Robin

Re: lyluatex and HarfBuzz (was: Complex/Large Lilypond projects and build automation)

Sorry, I didn't receive your replies, maybe because I seem to have lost my subscription to this list, but I am back on now... Here's my environment: I am on an up-to-date (08-12-1919) texlive system installed on a Mac running High Sierra. My LilyPond tells me that it is GNU LilyPond 2.19.83. "C

Re: lyluatex and HarfBuzz (was: Complex/Large Lilypond projects and build automation)

Am 8. Dezember 2019 12:57:38 MEZ schrieb Rembrandt Wolpert : >Sorry, I didn't receive your replies, maybe because I seem to have lost >my >subscription to this list, but I am back on now... > >Here's my environment: > >I am on an up-to-date (08-12-1919) texlive system installed on a Mac >runnin

Re: Place a markup string at the right of a notehead

On Sun, Dec 8, 2019 at 1:37 PM Thomas Morley wrote: > Am So., 8. Dez. 2019 um 11:51 Uhr schrieb Paolo Pr : > > > 2) Is there a way to place the markup exactly on the top or on the > bottom of the notehead as well? > > Not sure what you mean, could you provide an image? > > I would like the same b

Re: Place a markup string at the right of a notehead

Am So., 8. Dez. 2019 um 18:38 Uhr schrieb Paolo Pr : > > > > On Sun, Dec 8, 2019 at 1:37 PM Thomas Morley wrote: >> >> Am So., 8. Dez. 2019 um 11:51 Uhr schrieb Paolo Pr : >> >> > 2) Is there a way to place the markup exactly on the top or on the bottom >> > of the notehead as well? >> >> Not sur

alignAboveContext for alto

Dear Lilyponders, Suppose I have a ChoirStaff with four voices, and stanzas are sung by everybody, but distributed between the voices (less cluttered). << \new Voice = "one" { \sopranoMusic } \new Lyrics \lyricsto "one" \stanzaOne \new Voice = "two" { \altoMusic } \new Lyrics \lyricsto "

Two or more accidentals per note.

How do you wright two (or more) accidentals to modify the same note? Where is this written?And is there more than one way to do this? For example how would I write 3 #; 2 double sharps; 2 or more microtonal accidentals; or microtonal accidentals with #'s or b's.Please keep the explanati

Collision between ottava bracket and stems in cross-staff systems

Hello, in cross-staff systems, I see that the ottava bracket can produce an unwanted collision between the "8va" string and the stems. Please, look at: http://lilybin.com/vf4vaj/1 Is there a way to automatically avoid that, without using the trial-and-error method for adjusting the offset of the

Re: Collision between ottava bracket and stems in cross-staff systems

On 2019-12-08 3:40 pm, Paolo Pr wrote: Hello, in cross-staff systems, I see that the ottava bracket can produce an unwanted collision between the "8va" string and the stems. Please, look at: http://lilybin.com/vf4vaj/1 Is there a way to automatically avoid that, without using the trial-and-e

Re: Collision between ottava bracket and stems in cross-staff systems

Hi Paolo, I think you’d want a callback that tweaks shorten-pair? Look at for an idea of what the final result might be. Hope that helps! Kieren. > -- Original Message -- > From: Paolo Pr > Date: December 8, 2019 at 6:40 PM > > > Hello, >   > in

RE: Complex/Large Lilypond projects and build automation

David, Thanks for your response. I'm looking into using Gradle - and I think I'll be happiest if I invest the time to develop one or more Gradle plugins to define the notion of a Lilypond project. I have a steep learning curve in front of me since I'm not familiar with Gradle. So part of my

Re: Collision between ottava bracket and stems in cross-staff systems

Hello Kieren, unfortunately this method is trial and error as well. In fact, I can't use the same shorten-pair value if the stem is up or down, and (maybe) if the notehead has different sizes... I think that the problem with the bracket I just described is a bug or a feature that should be enhanc

Re: Collision between ottava bracket and stems in cross-staff systems

Hi Paolo, > unfortunately this method is trial and error as well. Not if it’s a callback function. ;) You need to write code that determines how much to shorten/extend (by referencing the width of noteheads, etc.), and automatically applies the tweak. That’s how you make it not trial-and-error.

RE: Collision between ottava bracket and stems in cross-staff systems

Paolo, Why not place the entire chord in the treble? Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Paolo Pr Sent: Sunday, December 08, 2019 4:28 PM To: kieren_macmillan kieren_macmillan Cc: lilypond-user Subject: Re: Collision betwe

Re: Collision between ottava bracket and stems in cross-staff systems

> I think that the problem with the bracket I just described is a bug > or a feature that should be enhanced... Vertical alignment of cross-staff material is partially broken, yes, from the very beginning. Search for cross AND staff AND status:Accepted in the issue tracker. Werner

Re: Complex/Large Lilypond projects and build automation

Hi Jacques, Is this of any use? https://www.ctan.org/pkg/lualatex-doc Andrew On Sun, 8 Dec 2019 at 18:46, Jacques Menu wrote: > > Urs, who is the creator/maintainer of LuaLaTeX? There seems to be a mist > cloud around it...

Re: Complex/Large Lilypond projects and build automation

Am 08.12.19 um 08:44 schrieb Jacques Menu: Urs, who is the creator/maintainer of LuaLaTeX? There seems to be a mist cloud around it... I'm not completely sure about the relation between LuaTeX and LuaLaTeX. The LuaTeX homepage is http://www.luatex.org/, and the LuaTeX manual is basically w

Re: Complex/Large Lilypond projects and build automation

On 12/8/19 07:43, Urs Liska wrote: > > > Am 8. Dezember 2019 06:22:22 MEZ schrieb Jacques Menu : >> Hello folks, >> >> I’ll look into those alternative build systems. >> >> Urs, where can I find a MWE of LuaLaTeX use for LilyPond? Didn't find >> any when I seached the web recently. >> I have MacT

lyluatex and HarfBuzz (was: Complex/Large Lilypond projects and build automation)

Am 08.12.19 um 09:04 schrieb Rembrandt Wolpert: Here's the hickup (probably easily fixed, Urs?) that interrupts compilation in a small examples: Well, I had replied to you two times, asking for further information. Since that didn't come I didn't look into it so far ... > However, we hit a s

Re: lyluatex and HarfBuzz (was: Complex/Large Lilypond projects and build automation)

Thanks Urs, I don’t think I’ll give LuaTex/LuaLaTex a try then. A nice day! JM > Le 8 déc. 2019 à 09:49, Urs Liska a écrit : > > > Am 08.12.19 um 09:04 schrieb Rembrandt Wolpert: >> Here's the hickup (probably easily fixed, Urs?) that interrupts >> compilation in a small examples: > > > Wel

Re: Place a markup string at the right of a notehead

Hi Thomas, I think that your solution should be posted in the snippet repository as well. It's very useful for very complex scores, when you have to manage lot of markups, because the trial-and-error method is time consuming. In addition: 1) How can I set the font's attributes of this tweak to th

Re: Jazz chords layout question

Am So., 14. Juli 2019 um 17:46 Uhr schrieb Jacques Menu : > > Thnks Robin and Harm. > > Here: > > % \showLeftEdge > \pseudoIndent #'(-8 . 0) #55 > > works fine, I attach the results. > > JM > > > Le 14 juil. 2019 à 16:39, Robin Bannister a écrit : > > Oh dear, that recommendation was fo

harmonyli.ly stable release 1.0 published

Dear Friends; A few weeks ago, I promised to write a tutorial for harmonyli.ly. As you might remember, harmonyli.ly is a library for embedding harmony analysis symbols into LilyPond encoded scores. Today, I released the complete version 1.0 which now can create symbols of the functional harmony t

Re: Place a markup string at the right of a notehead

Am So., 8. Dez. 2019 um 11:51 Uhr schrieb Paolo Pr : > > Hi Thomas, > > I think that your solution should be posted in the snippet repository as > well. It's very useful for very complex scores, when you have to manage lot > of markups, because the trial-and-error method is time consuming. > In a