summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWerner Lemberg <wl@gnu.org>2011-01-17 03:50:18 +0100
committerWerner Lemberg <wl@gnu.org>2011-01-17 17:26:44 +0100
commit9a17ff7c0ffc31ef9000e6c0ecbee1d225baae10 (patch)
tree31b7d16886988f2bcaf0c551aadba2ac96aa3c99
parent3c00bd3295cf8542f610a4975b5e11d26cf6e009 (diff)
[font-name-font-size.ly]: Use Emmentaler font.
This change ensures that lilypond doesn't rely on an external font while compiling; for non-GUB builds it might happen that FontConfig selects a non-scalable font otherwise.
-rw-r--r--input/regression/font-name-font-size.ly11
1 files changed, 8 insertions, 3 deletions
diff --git a/input/regression/font-name-font-size.ly b/input/regression/font-name-font-size.ly
index a0ba3a2e20..28c32c3bd9 100644
--- a/input/regression/font-name-font-size.ly
+++ b/input/regression/font-name-font-size.ly
@@ -5,11 +5,16 @@
Setting the @code{font-name} property does not change the font
size. The two strings below should be concatenated and have the
same font size.
+
+Note that `the same font size' is related to what lilypond reports
+on the console if in verbose mode (3.865234375 units for this
+regression test). If you actually look at the two fonts the
+optical size differs enormously.
"
}
\markup \concat {
- "string"
- \override #'(font-name . "New Century Schoolbook")
- "string"
+ "pfsm"
+ \override #'(font-name . "Emmentaler-20")
+ "pfsm"
}