Re: Custom colors in fret diagrams
Hi Jean, Thanks for the quick response. Putting quotes around it doesn't really help. The expression gets ignored and the dot comes with the default black color in this case. Sincerely, Nikita On Thu, May 16, 2024 at 2:18 AM Jean Abou Samra wrote: > > Quick question on coloring dots in fret-diagrams. There is an option to > use > > predefined colors from normal, CSS or X11 palettes which works perfectly > well > > in the fret-diagram-verbose with the snippet below: > > > > > (place-fret 3 6 3 dodgerblue2) > > > > For some reason I cannot get it working with custom RGB or Hex colors > like > > this: > > > > > (place-fret 3 6 3 #FF) > > > You should put quotes around it: > > (place-fret 3 6 3 "#FF") > > HTH > Jean > > >
Re: italic phrase in lyrics
I have these functions defined:
\version “2.24.0"
italic = {
\override Lyrics.LyricText.font-shape = #'italic
}
bold = {
\override Lyrics.LyricText.font-series = #'bold
}
normal = {
\revert Lyrics.LyricText.font-series
\revert Lyrics.LyricText.font-shape
}
and I use them like this:
VerseOne = \lyricmode
{
\italic "O Lord, open thou our lips;" \normal "And our mouth shall show”
\bold forth thy \normal praise.
}
Carolyn
> Date: Wed, 15 May 2024 17:05:54 -0400 (EDT)
> From: David Olson
> To: lilypond-user
> Subject: italic phrase in lyrics
> Message-ID:
> <1642762455.2851938.1715807154285.javamail.zim...@dslextreme.com>
> Content-Type: text/plain; charset="utf-8"
>
> Suppose the lyrics contain two contradictory propositions:
>
> Ma -- the -- ma -- tics is in -- vent -- ed.
> Ma -- the -- ma -- tics is dis -- cov -- ered.
>
> Is this the only way to put the second proposition in italics?
>
> \markup { \italic Ma } --
> \markup { \italic the } --
> \markup { \italic ma } --
> \markup { \italic tics }
> \markup { \italic is }
> \markup { \italic dis } --
> \markup { \italic cov } --
> \markup { \italic ered. }
Re: Custom colors in fret diagrams
> Quick question on coloring dots in fret-diagrams. There is an option to use > predefined colors from normal, CSS or X11 palettes which works perfectly well > in the fret-diagram-verbose with the snippet below: > > > (place-fret 3 6 3 dodgerblue2) > > For some reason I cannot get it working with custom RGB or Hex colors like > this: > > > (place-fret 3 6 3 #FF) You should put quotes around it: (place-fret 3 6 3 "#FF") HTH Jean signature.asc Description: This is a digitally signed message part
Custom colors in fret diagrams
Hi Everyone, Hope you are doing well. Quick question on coloring dots in fret-diagrams. There is an option to use predefined colors from normal, CSS or X11 palettes which works perfectly well in the fret-diagram-verbose with the snippet below: > (place-fret 3 6 3 dodgerblue2) For some reason I cannot get it working with custom RGB or Hex colors like this: > (place-fret 3 6 3 #FF) Is this at all possible? Sincerely, Nikita
Re: italic phrase in lyrics
Le mercredi 15 mai 2024 à 17:05 -0400, David Olson a écrit :
> Suppose the lyrics contain two contradictory propositions:
>
> Ma -- the -- ma -- tics is in -- vent -- ed.
> Ma -- the -- ma -- tics is dis -- cov -- ered.
>
> Is this the only way to put the second proposition in italics?
>
> \markup { \italic Ma } --
> \markup { \italic the } --
> \markup { \italic ma } --
> \markup { \italic tics }
> \markup { \italic is }
> \markup { \italic dis } --
> \markup { \italic cov } --
> \markup { \italic ered. }
You could do it like this:
\version "2.24.2"
\lyrics {
\override LyricText.font-shape = #'italic
Ma -- the -- ma -- tics is dis -- cov -- ered.
}
or even like this:
\version "2.24.2"
\lyrics {
\markupMap text \markup \italic \etc {
Ma -- the -- ma -- tics is dis -- cov -- ered.
}
}
HTH
Jean
signature.asc
Description: This is a digitally signed message part
italic phrase in lyrics
Suppose the lyrics contain two contradictory propositions:
Ma -- the -- ma -- tics is in -- vent -- ed.
Ma -- the -- ma -- tics is dis -- cov -- ered.
Is this the only way to put the second proposition in italics?
\markup { \italic Ma } --
\markup { \italic the } --
\markup { \italic ma } --
\markup { \italic tics }
\markup { \italic is }
\markup { \italic dis } --
\markup { \italic cov } --
\markup { \italic ered. }
Frescobaldi: missing menu bar FIXED
I'd like to record a fix, of sorts, for a missing menu bar in Frescobaldi under a rather specific combination of circumstances. It might help someone. Possibly future-me! I run Frescobaldi on an Ubuntu 22.04 system, with an Apple-Mac-OS-X- like KDE theme that puts the menus of the currently-focussed application at the top of the screen. Following a recent upgrade to KDE Plasma 6, the menus in Frescobaldi completely disappeared. You can force the menu bar to appear at the top of the application window for all apps. To do this, go to System Settings -> Session -> Background services and uncheck "Application menus daemon" It might be necessary to restart your session for this to take effect. It might be possible to create a specific exception for Frescobaldi, using the KWin rule editor, accessed by right-clicking on the title bar of the Frescobaldi window and selecting More Actions. Unfortunately I've been unable to find a specific combination of settings that work.
Re: Scoop (jazz notation)
> > -- Forwarded message -- > From: Tim Giles > To: lilypond-user@gnu.org > Date: Tue, 14 May 2024 22:34:00 +0200 > Subject: Re: Scoop (jazz notation) > Thanks for the link, Werner. I have added a comment regarding the jazz > application. Cheers, -Tim > > > On 14 May 2024, at 19:21, Werner LEMBERG wrote: > > > > > >> 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 typeset scores! – > > regarding its usage in jazz music. > > > > > >Werner > > Also, it would be good to discuss the feature here to see what people think about it. What kind of variety does it need to accommodate? What is the best way to conceptualize it, and how does it fit into the lilypond language? What are your suggestions for syntax, how you want to use it in code? >From my perspective, to start with, I would disagree that a scoop is an articulation. Conceptually, I can see how it is similar to an articulation, but I think there are bigger differences. Mainly, the space it takes on the page is prior to the note, like a glissando, not above the note, like an articulation. So it has horizontal implications that articulations do not. The scoop also describes how to approach the note, rather than what the note sounds like when you get to it. There is potentially a lot more information in a scoop, including the vertical pitch component, the horizontal duration, and to some extent the shape (linear vs convex vs concave), as well as all the engraving details about the thickness of the line. On the other hand, you could argue that many examples of scoop are not intended to convey specific shapes, so a one-size-fits-all glyph is sufficient, and it is not intended to solve the problem of expressive glissando. Which, is also a reasonable argument. There is no reason both cannot exist. However, from my perspective, I would want to be able to modify the scoop curve, so a solution that does not address spatial configuration would be disappointing. So, I am going to speak to that. My suggestion for syntax, since the scoop comes before the note, would be more along the lines of prefix \scoop c4 rather than postfix like an articulation c4-@ In terms of balancing ease of use with flexibility, there could be a more general function where you could specify the origin of the scoop One idea is to use a number pair to describe the X and Y extent of the scoop in units of staff spaces so the above examples might be \scoopFrom ( 1 . 1 ) c4 % default scoop \scoopFrom ( 4 . 1 ) c4 % long scoop \scoopFrom ( 1 . 4.5 ) c4 % octave tall scoop \scoopFrom ( 1 . -1 ) c4 % scoop from above? If we had this, then \scoop could be a shorthand for \scoopFrom ( 1 . 1 ) A similar but possibly more "musical" approach would be to have the \scoopFrom function take instead of a number pair, another note, that would suggest the location from which the scoop starts \scoopFrom a4 c4 % default scoop \scoopFrom a1 c4 % long scoop \scoopFrom c,4 c4 % octave tall scoop \scoopFrom e4 c4 % scoop from above Elaine Alt 415 . 341 .4954 "*Confusion is highly underrated*" ela...@flaminghakama.com Producer ~ Composer ~ Instrumentalist ~ Educator -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
