Colin,
>> <snipped>All this comes about as I'm thinking of getting back to
>> some documentation work, and wanted to compile docs locally. I'll
>> still keep that goal in mind.
>>
>> If you can still reproduce the problem after this cleaning, could
>> you run
>>
>> ```
>> FC_DEBUG=2025 build/out/bin/lilypond --verbose --ps test_file.ly >
>> fclog.log 2> lilylog.log
>> ```
>>
>> and send the three resulting files, `test_file.ps`, `fclog.log` and
>> `lilylog.log`?
>
> The requested files are attached as an archive, as two of them are
> rather large.
(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.
Werner
