Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info

> On macOS Ventura v13.6.3 (and almost certainly other versions), the
> string produced when using -dshow-available-fonts need not be
> encoded as UTF-8.

Thanks, should be fixed with this MR:

  https://gitlab.com/lilypond/lilypond/-/merge_requests/2231

Out of interest: Which font shows this behaviour?

I suggest you contact the FontConfig people and report the issue, too;
assuming that the font is valid it should be possible to convert the
non-UTF8 data to UTF8.


    Werner