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

2024-01-13 Thread Nate Whetsell
I can confirm that replacing scm_write_line (ly_string2scm (str), port); with scm_c_write (port, str.c_str (), str.length ()); fixes the issue on my end. I’d be happy to make a merge request for this. > On Jan 13, 2024, at 6:19 PM, Jean Abou Samra wrote: > >> I don't have the time to check

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

2024-01-13 Thread Jean Abou Samra
> I don't have the time to check this but is there not a way to simply write > bytes to (current-error-port) in Guile? Like scm_c_write < https://www.gnu.org/software/guile/manual/html_node/Using-Ports-from-C.html > ? signature.asc Description: This is a digitally signed message part

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

2024-01-13 Thread Jean Abou Samra
Le vendredi 12 janvier 2024 à 06:08 +, Werner LEMBERG a écrit : > How shall we proceed? I don't have the time to check this but is there not a way to simply write bytes to (current-error-port) in Guile? IIRC, all Guile ports can be used in both binary and text ways. Also, I'm pretty sure

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

2024-01-13 Thread Jean Abou Samra
Le mardi 09 janvier 2024 à 12:43 -0500, Nate Whetsell a écrit : > I’m starting to think this may be a bug in Guile. Well, Guile's encoding handling is quite bug-ridden. signature.asc Description: This is a digitally signed message part