Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Am 11.01.2018 um 05:38 schrieb Vaughan McAlley: On 8 Jan 2018 12:35 p.m., "Andrew Bernard" > wrote: Hi Urs and All, A totally successful install on a new Ubuntu 17.10 pristine image. All works fine as per the source

Re: Non-standard ledger lines and articulations collisions

On 01/10/2018 10:57 AM, David Kastrup wrote: You are missing the difference between ly:side-position-interface::y-aligned-side and side-position-interface::y-aligned-side . The latter is defined in scm/output-lib.scm as (define-public side-position-interface::y-aligned-side

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

On 8 Jan 2018 12:35 p.m., "Andrew Bernard" wrote: Hi Urs and All, A totally successful install on a new Ubuntu 17.10 pristine image. All works fine as per the source installations now updated. A large vote of thanks to all who untangled this ball of wool. Despite a

Re: CueVoice and tagging

Thanks for your patience and explanation ;) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: CueVoice and tagging

Johannes Roeßler writes: > thx David, got it. Changed the voice, so that it doesn't start with > the \cue. (See attached file) Which doesn't compile due to missing \language declaration. > What I still don't get, is what happens when I start voiceB with > > \clef "bass" \clef

Re: CueVoice and tagging

thx David, got it. Changed the voice, so that it doesn't start with the \cue. (See attached file) What I still don't get, is what happens when I start voiceB with \clef "bass" Joei Johannes Roeßler writes: Hi Guys, sort of an didactic question. Maybe I was tired or just

Re: CueVoice and tagging

Johannes Roeßler writes: > Hi Guys, > > sort of an didactic question. Maybe I was tired or just stupid - I > forgot about the \killCues command and tried to build this on my own. > So - that means I know (now) the correct way to get rid of the cues - > but I'd still like to know

CueVoice and tagging

Hi Guys, sort of an didactic question. Maybe I was tired or just stupid - I forgot about the \killCues command and tried to build this on my own. So - that means I know (now) the correct way to get rid of the cues - but I'd still like to know where I was wrong with my idea: \version

Re: optional Dynamics with tag#?

thx Kieren - I will check it out! Sound promising... ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Generate Random Pitches and Accidentals?

David, This looks fantastic. I'll play with it. Thank you so much! -- Josh On Mon, Jan 8, 2018 at 6:19 PM, David Nalesnik wrote: > Hi Josh, > > On Mon, Jan 8, 2018 at 4:34 PM, Joshua Nichols > wrote: > > Hi! This is for education! > > > >

Re: optional Dynamics with tag#?

Hi Johannes, While the tagging mechanism works in this use-case — and others in the thread have shown you how to accomplish what you need — I strongly encourage you to look at the edition engraver. Especially given your statement > I try to make optional dynamics for a critical edition [!!]

Re: optional Dynamics with tag#?

thx David... it can be so simple *facepalm* - and regarding "says who": me :) Joei ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: optional Dynamics with tag#?

thx Michael, works as desired :) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Transposition

Tom van der Hoeven writes: > Kieren and Noeck, > Thanks for the answers. > I worked already with the function \transpose and that works excellent. > My question concerned the use of the tag \transposition. > I wondered why it was used for two specific cases and not for the

Re: optional Dynamics with tag#?

> Johannes Roeßler hat am 10. Januar 2018 um 16:50 geschrieben: > > > Dear Lilypondians ;) > > another day another question - I try to make optional dynamics for a critical > edition, > is it possible, that just dynmaics signs can't be toggled with tags? Hi Johannes, >

Re: optional Dynamics with tag#?

Johannes Roeßler writes: > Dear Lilypondians ;) > > another day another question - I try to make optional dynamics for a > critical edition, > is it possible, that just dynmaics signs can't be toggled with tags? > > 8< > > \version "2.19.58" > > music = \relative { >  

Re: Non-standard ledger lines and articulations collisions

Paul Morris writes: > Here's my specific question.  The docs say this for the Y-offset > property of the Script object: > > |Y-offset| (number): > >|#ly:side-position-interface::y-aligned-side> #ly:side-position-interface::pure-y-aligned-side> >| > >The

Re: Transposition

Kieren and Noeck, Thanks for the answers. I worked already with the function \transpose and that works excellent. My question concerned the use of the tag \transposition. I wondered why it was used for two specific cases and not for the general case. Given both answers it seems that I haven't

optional Dynamics with tag#?

Dear Lilypondians ;) another day another question - I try to make optional dynamics for a critical edition, is it possible, that just dynmaics signs can't be toggled with tags? 8< \version "2.19.58" music = \relative {   g'8. c32 d \tag #'dyn {\p } c32 d  } \score {  

Re: SVG output - Group multiple grobs together

On 01/10/2018 06:51 AM, James Opstad wrote: How would I include multiple grobs within the same group e.g. all the grobs associated with a single note (NoteHead, Stem, Accidental etc.)? Hi, I don't think there is currently a way to do that.  You could give each grob you want to group together

Non-standard ledger lines and articulations collisions

Hi all,  I'm working on a work-around for a collision between ledger lines and articulations, for Clairnote an alternative notation system: http://clairnote.org/sn/  LilyPond does not currently take non-standard 'extra' ledger lines into account when positioning articulations.  Here's a

Re: SVG output - Group multiple grobs together

Hi James, On Wed, Jan 10, 2018 at 5:51 AM, James Opstad wrote: > Hello, > > > I have been experimenting with the new output-attributes grob property for > SVG output. For example, the following code creates a group with id="noteC" > around the C notehead. > > > \version

SVG output - Group multiple grobs together

Hello, I have been experimenting with the new output-attributes grob property for SVG output. For example, the following code creates a group with id="noteC" around the C notehead. \version "2.19.80" \pointAndClickOff \relative c' { \once \override NoteHead.output-attributes = #'((id .