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

> Thanks for making the merge request. Unfortunately, it didn’t fix
> the issue, although it really seems like it should have.

Thanks for the testing it and the detailed analysis.  I've changed the
status of the Merge Request to 'draft'.

> I’m starting to think this may be a bug in Guile.

Can you make your example code generic and report it to the Guile
people?

> When I use a conversion strategy of 'substitute, the conversion
> works as expected (with a � where the encoding issue occurs).  When
> I use the default strategy ('error, presumably), LilyPond outputs:
> [...]

How shall we proceed?


    Werner