[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash in 2.25.4

From: Jean Abou Samra
Subject: Re: Crash in 2.25.4
Date: Tue, 23 May 2023 21:15:47 +0200
User-agent: Evolution 3.48.1 (3.48.1-1.fc38)

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.

Based on the fact that we use Pango's FreeType backend, which is not the focus 
for Pango maintainers, I would not be surprised if this were an issue specific 
to this part of Pango, in the same vein as 

Our tagline is defined as

tagline = \markup {
  \pad-to-box #'(0 . 0) #'(0 . 3)
  {  \with-url

    \line {

      %% 2014 = em dash.

      #(format #f "Music engraving by LilyPond ~a~awww.lilypond.org"
         (ly:wide-char->utf-8 #x2014)

The tagline text is one string, so we're text-layouting all in one call to 
Pango. I see zero reason for Pango to split out the digits into separate items 
with different fonts, since all the glyphs are in the requested C059 font.

Unfortunately, even with the fonts-noto-color-emoji package installed, I still 
cannot reproduce this problem in an Ubuntu 23.04 VM.

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]