[Top][All Lists]

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

Re: Crash in 2.25.4 Solved

From: Colin Campbell
Subject: Re: Crash in 2.25.4 Solved
Date: Mon, 22 May 2023 16:52:27 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.11.0

On 2023-05-22 02:07, Werner LEMBERG wrote:
(1) You have the font 'Noto Color Emoji' installed on your system (the
     new one, with scalable glyphs using the 'COLR' v1 format).  Say
     `fc-list | less` to find out where it is located.  This font
     format is not supported by GhostScript – such a font cannot be
     meaningfully embedded in a PS or PDF file.

(2) For some reason, the digits in the tagline string are taken from
     `Noto Color Emoji` instead of `C059-Roman`, which is used for
     everything else in the tagline (see the end of your
     `Non-Musical.ps` file).

I think item (1) happens because 'Noto Color Emoji' is set up as a
fallback font on your OS.

Regarding (2) I'm not sure where exactly the problem lies (i.e.,
whether it is a LilyPond or a Pango issue).  However, if you use the
current LilyPond developer version, this should be fixed: LilyPond and
Pango no longer use glyph names but glyph indices for communication.

BTW: Have you checked whether the Cairo backend works for you?

lilypond -dbackend=cairo ...

Perhaps we should disable color fonts similarly to variation fonts, at
least for now (and later on for the PS backend only).  Such a change
could be backported to the 2.24 series.

I had tried a copy of the test file with tagline =#f in a \header block, but that crashed.

Following your suggestion, Werner, I tried the test file with the cairo back end, and it worked as expected.

I then deleted the Noto Color Emoji font (synaptic also deleted texlive fonts extra links), and retried the test file. Again, it worked as expected.

I believe, as my old Latin teacher would say, rem acu tetigisti!

My heartfelt thanks to you and especially Jean for your help and patience.


reply via email to

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