I’m experiencing some strange behaviour with Pango on Windows. Some standard Windows fonts fail to open with Pango while others work. For example, there’s no problem using Bauhaus 93, Calibri or Segoe UI with Pango. When trying to open Brush Script MT, however, I get the following error:
(process:928): Pango-WARNING **: 16:43:17.129: couldn't load font "Brush Script MT 144px", falling b
ack to "Sans 144px", expect ugly output.
The same happens with Algerian:
(process:928): Pango-WARNING **: 16:44:23.103: couldn't load font "Algerian 144px", falling b
ack to "Sans 144px", expect ugly output.
Why do some fonts work while others don’t? Doesn’t make sense to me. I use the Pango build provided by MSYS2 for MINGW64.
Ah, ok, so I have to use “Brush Script MT Italic” instead of “Brush Script MT” and “Algerian Extra-Condensed” instead of “Algerian”. Then Pango opens the fonts.
Still I find it a bit strange that Pango’s font matching falls back to “Sans” when passing “Brush Script MT”. Wouldn’t it make much more sense to fall back to “Brush Script MT Italic” in that case? The family name surely is Brush Script MT. Also, “Algerian” falls back to “Sans” as well. But I think it would be much more reasonable to fall back to “Algerian Extra-Condensed” then…
Ok, so looks like it’s the Windows font mapper which is a bit pedantic and doesn’t accept “Brush Script MT” but only “Brush Script MT Italic”. When using the FT2 backend, which probably uses fontconfig, “Brush Script MT” works as well.