|
From: | Urs Liska |
Subject: | Re: Format of -dshow-available-fonts output |
Date: | Wed, 25 Jul 2018 15:47:42 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 |
Am 25.07.2018 um 15:04 schrieb Torsten Hämmerle:
Urs Liska-3 wroteWhat makes me wonder even more is that in a LilyPond file the following two are possible (i.e. call the right font): \override TextScript.font-name = "TeX Gyre Adventor Bold Italic" \override TextScript.font-name = "TeXGyreAdventor Bold Italic" but not this: \override TextScript.font-name = "TeX Gyre Adventor BoldItalic" \override TextScript.font-name = "TeXGyreAdventor BoldItalic"Hi Urs, You could even write "T EXGY Read vento R"
OK, I now see, there is also a reference to "ignore spaces" somewhere in the verbose log output.
The styles, however, have to be separated by space(s) and they also have to be separated from the font family name.
Then why is LilyPond (in the output of -dshow-available-fots) reporting "BoldItalic" and not "Bold Italic"?
Urs Liska-3 wrote[texgyreadventor_bold_italic_3.8662109375] [tex_gyre_adventor_bold_italic_3.8662109375]These are the keys used for the font buffering hash table built from the font-name specified and the Pango font size (this is an absolute font size not depending on the current LilyPond output scale). Spaces will be transformed into _ and everything will be converted to lower case. Physically, it's the same font in both cases. In the extreme example with "T EXGY Read vento R", the internally used font key will be: [t_exgy___read_vento_r_3.8662109375] When using 12pt instead of the standard 11pt font size, the generated key name will be: [t_exgy___read_vento_r_4.2177734375]
Thanks for the explanation. Urs
Torsten -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html _______________________________________________ lilypond-user mailing list address@hidden https://lists.gnu.org/mailman/listinfo/lilypond-user
[Prev in Thread] | Current Thread | [Next in Thread] |