[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error wit
From: |
Nate Whetsell |
Subject: |
Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info |
Date: |
Sat, 13 Jan 2024 20:18:54 -0500 |
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 <jean@abou-samra.fr> wrote:
>
>> 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 >
> ?
- Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Nate Whetsell, 2024/01/07
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Werner LEMBERG, 2024/01/09
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Nate Whetsell, 2024/01/09
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Werner LEMBERG, 2024/01/12
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Nate Whetsell, 2024/01/12
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Jean Abou Samra, 2024/01/13
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Jean Abou Samra, 2024/01/13
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info,
Nate Whetsell <=
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Werner LEMBERG, 2024/01/14
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Werner LEMBERG, 2024/01/14
- Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info, Jean Abou Samra, 2024/01/13