Re: Strange behavior with unfound text font

2022-12-13 Thread Werner LEMBERG
> Well, somehow I failed to make the obvious test: this also triggers > the issue: > > \version "2.25.0" > > \markup \override #'(font-name . "Noto Sans Bold") "ABC" > > > > Does that reproduce it for you (after installing the Noto fonts if > not already installed)? > `lilypond

Re: Strange behavior with unfound text font,Strange behavior with unfound text font

2022-12-13 Thread Jean Abou Samra
Le 12/12/2022 à 11:25, Werner LEMBERG a écrit : Hmm. Using FreeType 2.12.1 (self-compiled) and FontConfig 2.13.1 (as provided by my openSUSE box), running `lilypond --verbose` (from current git) on the above input gives ``` ... [nonexistent_bold_3.8662109375] Finding the ideal number of pages...

Re: Strange behavior with unfound text font,Strange behavior with unfound text font

2022-12-12 Thread Werner LEMBERG
> \markup \override #'(font-name . "Nonexistent Bold") "ABC" > > With 2.22, this compiles without warning, and the resulting PDF > contains the font "DejaVuSans-Bold" (according to pdffonts). > > With 2.23.82, it gives me > > GNU LilyPond 2.23.82 (running Guile 2.2) > Processing

Strange behavior with unfound text font

2022-12-11 Thread Jean Abou Samra
Folks, Coincidentally, at the same time as Lukas, I found another font-related glitch, although I don't think it's the same: \markup \override #'(font-name . "Nonexistent Bold") "ABC" With 2.22, this compiles without warning, and the resulting PDF contains the font "DejaVuSans-Bold"