[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    Re: set-global-staff-size undoes define fonts
From:       Michael Gerdau <mgd () qata ! de>
Date:       2019-01-28 7:10:56
Message-ID: BD74810D-7DA3-4D6A-B795-17470400B496 () qata ! de
[Download RAW message or body]


> > > On 27/01/2019 04:52, David F. wrote:
> > > I can specify the font for my score to use with #(define fonts … ), but \
> > > calling #(set-global-staff-size) undoes the font definition.

I seem to recall that's documented somewhere but I can't find where.

> > Why do you insist on the order, anyway? If you don't, I think the
> > solution would be quite obvious.
> 
> Because I engrave hymns in several different styles, e.g. 4:3 slides, 16:9 slides, \
> hymnal-style, etc.  I have a .ly file with all the base or common styles and then I \
> override whatever is appropriate for specific styles.  In this case, I want the \
> font to be the same for all styles (so it gets declared first).  But slides have a \
> larger text size, so I want to override the font size specifically for engraving \
> slides, so it gets declared later.

That does not make sense in the general meaning of things. There's no reason other \
than your preferred order of definitions that prevents you from setting size first \
and do the font definitions afterwards.

> As a workaround to the trouble I'm having (because there is a bug in either \
> Lilypond or my understanding)

It is my understanding there's a bug in your understanding 😊

Kind regards,
Michael
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


[prev in list] [next in list] [prev in thread] [next in thread]