1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. See TRANSLATION for details.
11 @node typography-features
13 @unnumberedsec Font design
15 A large factor that makes LilyPond output look traditional lies in the
16 blackness of the page. By using heavy stafflines, and a font design to
17 match that, the overall impression is much stronger. This is also very
18 clear from the following blowups:
20 @multitable @columnfractions .3 .3 .3
23 @sourceimage{henle-flat-gray,,,.png}
27 @sourceimage{baer-flat-gray,,,.png}
31 @sourceimage{lily-flat-bw,,,.png}
47 Another typical aspect of hand-engraved scores is the general look of
48 the symbols. They almost never have sharp corners. This is because
49 sharp corners of the punching dies are fragile and quickly wear out
50 when stamping in metal. The general rounded shape of music symbols is
51 also present in all glyphs of our "Feta" font.
56 @c @unnumberedsec Spacing
59 One of the problems that the Bach piece above inspired us to attack
60 is the spacing engine. One of its features is optical spacing.
61 It is demonstrated in the fragment below.
63 @divClass{float-center}
64 @sourceimage{spacing-with-corr,,,.png}
67 @divClass{float-center}
68 @sourceimage{spacing-no-corr,,,.png}
71 This fragment only uses quarter notes: notes that are played in a
72 constant rhythm. The spacing should reflect that. Unfortunately, the
73 eye deceives us a little: not only does it notice the distance between
74 note heads, it also takes into account the distance between
75 consecutive stems. As a result, the notes of an up-stem/down-stem
76 combination should be put farther apart, and the notes of a down-up
77 combination should be put closer together, all depending on the
78 combined vertical positions of the notes. The top fragment is printed
79 with this correction, the bottom one without. In the last case, the
80 down-stem/up-stems combinations form clumps of notes.
83 @c @unnumberedsec Ledger lines
86 Ledger lines are typographically difficult. They can easily blot
87 together with other signs, such as ledger lines or
88 accidentals. Other software prevents these collisions by spacing the
89 lines wider (thus taking up more space), or shortening ledger lines
90 (which hampers readability.)
92 @multitable @columnfractions .3 .3 .3
95 @sourceimage{henle-ledger,,,.png}
99 @sourceimage{baer-ledger,,,.png}
105 @sourceimage{lily-ledger,,,.png}
121 Traditional engravers would adjust the size of a ledger line,
122 depending on what symbols were in the neighborhood. LilyPond does the
123 same. Ledgers are shortened so they never collide with neighboring
124 lines, and they are shortened when there is an accidental.
126 @divClass{float-right}
127 Next: @ref{input-format,Use the Source Luke}, or: what