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

[Nate Whetsell]

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


Done.

> How shall we proceed?


Because this issue occurs with a macOS system font, it it likely to impact most 
(possibly all) LilyPond users on macOS. Consequently, it may be necessary to 
revert commit c3f2dddaa2b16231bc2f786fba7421f03f7da7af. As an alternative, it 
may be possible to output the C string created for -dshow-available-fonts 
directly, without first converting it to a Scheme string, but I’m not familiar 
enough with the LilyPond code base to know if this is a possibility.

Best,
Nate

> On Jan 12, 2024, at 1:08 AM, Werner LEMBERG <wl@gnu.org> wrote:
> 
> 
>> 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