Le mardi 23 mai 2023 à 21:15 +0200, Jean Abou Samra a écrit : > Le lundi 22 mai 2023 à 08:07 +0000, Werner LEMBERG a écrit : > > > Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it > > is a LilyPond or a Pango issue). > > I'm rather sure it's a Pango or Fontconfig issue.
Colin: it's really hard to debug this remotely (we might have to resort to VNC
or such, I'm afraid...) but there is one simple thing I would be interested in:
if you apply this patch, recompile LilyPond and redo the test, what happens?
```
diff --git a/lily/pango-font.cc b/lily/pango-font.cc
index 7fc7c35207..8f0750c463 100644
--- a/lily/pango-font.cc
+++ b/lily/pango-font.cc
@@ -523,7 +523,7 @@ Pango_font::text_stencil (Output_def * /* state */, const
std::string &str,
= pango_attr_font_features_new (features_str.c_str ());
pango_attr_list_insert (list, features_attr);
}
- if (music_string)
+ if (true)
{
// For music fonts, falling back to text fonts is surprising.
PangoAttribute *fallback_attr = pango_attr_fallback_new (false);
```
signature.asc
Description: This is a digitally signed message part
