lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Trouble with notation fonts when resizing


From: Torsten Hämmerle
Subject: Re: Trouble with notation fonts when resizing
Date: Sat, 12 May 2018 03:45:25 -0700 (MST)

David Sumbler wrote
> set-global-staff-size seems to be very buggy, and the newer magnify-
> staff (see Notation Ref. section 4.2.2) is recommended

Hi David,

I wouldn't call set-global-staff-size buggy, it's still the way to go if you
want to change the global stave size.

\magnifyStaff is inteded to be used for scaling single staves within a score
and spacing will behave accordingly.

The problem Brent ran into is neither new nor does it come unexpected: When
using custom fonts (no difference between text and music fonts here), you'll
have to tell LilyPond which size to use, and consequently you always had to
scaling factors.

Examples:
When changing a document's default fonts by using pango-make-font-tree,
there should alway be a scaling factor such as
(/ staff-height pt 20)
if you want to use non-standard stave-sizes (i.e. stave-sizes other than 20
pt)

The same holds true for music fonts.

Therefore, Andrew's approach is the way to go.
There is a nice  essay on alternative notations fonts
<http://lilypondblog.org/2015/03/managing-alternative-fonts-with-lilypond/>  
by Urs Liska, giving an example:

\paper {
  #(define fonts
    (set-global-fonts
      #:music "emmentaler"
      #:brace "emmentaler"
      #:roman "Century Schoolbook L"
      #:sans "sans-serif"
      #:typewriter "monospace"
      #:factor (/ staff-height pt 20)
  ))
}

In Brent's original post, this #:factor entry was missing and that's the
reason why the gonville font wasn't properly sized.

All the best,
Torsten



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html



reply via email to

[Prev in Thread] Current Thread [Next in Thread]