Re: Titles italic format ignored
Thank you all.
Il giorno ven 14 feb 2020 alle 15:44 Noeck ha
scritto:
> Hi,
>
> as others said, font-name overwrites all of font-family, font-series and
> font-shape. You can set the font family like this:
>
> \version "2.19.84"
>
> \paper {
> % define a font ‘arial’ from the font called ‘Arial’
> #(add-pango-fonts fonts 'arial "Arial"
> (/ (* staff-height pt) 2.5))
> }
>
> % use the font family ‘arial’ in your markup or header markup
> \markup \override #'(font-family . arial) \line {
> \bold "Bold" \italic "italic" "regular"
> }
>
> HTH
> Joram
>
>
Re: MultiMeasureRest length
Looks like there is a typo. s2 -> R2
\version "2.19.84"
{
\compressFullBarRests
R1 * 11
\override MultiMeasureRest.minimum-length = #30
R1 * 12
\time 2/4
R2 % not s2
}
---
Knute Snortum
(via Gmail)
On Tue, Feb 11, 2020 at 11:18 PM Kevin Barry wrote:
> On Wed, Feb 12, 2020 at 07:46:54AM +0100, Marco Bagolin wrote:
> > Hello all,
> > how is possible to set or modify the length of a MultiMeasureRest ?
>
> You can change its minimum-length. Does the below code do what you want?
>
> {
> \compressFullBarRests
> R1 * 11
> \override MultiMeasureRest.minimum-length = #30
> R1 * 12
> \time 2/4
> s2
> }
>
>
Re: Titles italic format ignored
Hi,
as others said, font-name overwrites all of font-family, font-series and
font-shape. You can set the font family like this:
\version "2.19.84"
\paper {
% define a font ‘arial’ from the font called ‘Arial’
#(add-pango-fonts fonts 'arial "Arial"
(/ (* staff-height pt) 2.5))
}
% use the font family ‘arial’ in your markup or header markup
\markup \override #'(font-family . arial) \line {
\bold "Bold" \italic "italic" "regular"
}
HTH
Joram
Re: Titles italic format ignored
Hi Curt, > Overriding font-name also overrides the font slant and weight in a sticky > way. Perhaps LilyPond ought to have a font-face property. You can override the entire font family, and then just use \italic, \bold, etc. as expected. Search the archives for Abraham ’s posts on how. Hope that helps, Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info
Re: Bug in \chords in latest developer version?
SK writes:
> Hello,
>
> I found very strange behaviour of \chords when used together with
> \numericTimeSignature. Check the following code:
>
> \new Score {
> <<
> \chords { c1 g c g }
> \relative c' { \numericTimeSignature c4-1 c c2 d4 d d2 e4 e e c e2 d \bar
> "|." }
>>>
> }
>
> When running it on LilyBin, it compiles correctly with the latest stable
> version, but with latest unstable, it shows no notes or staff, but only a
> line of chords.
That is expected. You never create any context but a Chords context,
and Chords have become aliased to Staff (in order to avoid spurious
creation of Staffs where not desired) and thus a sufficient target for
\numericTimeSignature.
> I tried to move the \numericTimeSignature to different places, but
> neither worked: Sometimes I got the chords below my staff, sometimes I
> got an extra staff with just the timeSignature - I think the place
> where I have it should work. Are there any changes in the unstable
> version to this part, or is it simply a bug?
If you want a Staff, write \new Staff . It is as simple as that. Like
\new Staff \relative c' { \numericTimeSignature ...
--
David Kastrup
My replies have a tendency to cause friction. To help mitigating
damage, feel free to forward problematic posts to me adding a subject
like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
Bug in \chords in latest developer version?
Hello,
I found very strange behaviour of \chords when used together with
\numericTimeSignature. Check the following code:
\new Score {
<<
\chords { c1 g c g }
\relative c' { \numericTimeSignature c4-1 c c2 d4 d d2 e4 e e c e2 d \bar
"|." }
>>
}
When running it on LilyBin, it compiles correctly with the latest stable
version, but with latest unstable, it shows no notes or staff, but only a
line of chords. I tried to move the \numericTimeSignature to different
places, but neither worked: Sometimes I got the chords below my staff,
sometimes I got an extra staff with just the timeSignature - I think the
place where I have it should work.
Are there any changes in the unstable version to this part, or is it simply
a bug?
Kind regards,
SK
Re: Titles italic format ignored
Overriding font-name also overrides the font slant and weight in a sticky way. Perhaps LilyPond ought to have a font-face property. The slant and weight can be specified along with the font name: subtitle = \markup \raise #1.0 \fontsize #-3 \override #'(font-name . "Arial Italic") "A Medley for Orchestra" or subtitle = \markup \raise #1.0 \fontsize #-3 \override #'(font-name . "Arial Black Italic") "A Medley for Orchestra" Regards, Curt McDowell
Re: [OT] Identification of a bagpipe embellishment?
On Tue, 11 Feb 2020 at 20:16, Guo Brian wrote:
>
> Hello all,
>
> Thanks for the info, but I know that I could just \include “bagpipe.ly”
> and use the command defined there \pgrace{g32[ f d]}; I was wondering if
> there was a conventional name for the embellishment (even if it is not
> defined in bagpipe.ly), for example, gracenotes HighGDE (followed by the
> main note D) is a doubling on D, gracenotes LowGDC is a throw on D, GDG is
> a grip/leumluath, GDGE is a taorluath, and so on.
>
Hello,
Piper and the creator of "bagpipe.ly" here. Without listening to the music
and some more notational context I'd say that is a misprint. It looks like
a slur on f followed by a g melody note which is incorrect. A slur should
start with a gracenote higher than the melody note (either g or high a),
then the melody note, then a gracenote lower than the melody note (either
one step lower or several steps depending on the finger position). In this
case it should be "\slurg g4" which should expand to "\pgrace{A32[ g f]}".
It looks like the definition in "bagpipe.ly" is wrong here though.
--
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.
Re: Titles italic format ignored
On 2020-02-13 11:22 pm, Marco Bagolin wrote: Why “italic” format is ignored ? Because you effectively told LilyPond to ignore it. font-name trumps font-family, font-series and font-shape. Please review this post for more details: https://lists.gnu.org/archive/html/lilypond-user/2019-01/msg00723.html -- Aaron Hill
