[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: |
Jean Abou Samra |
Subject: |
Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info |
Date: |
Sun, 14 Jan 2024 00:15:59 +0100 |
User-agent: |
Evolution 3.50.3 (3.50.3-1.fc39) |
Le vendredi 12 janvier 2024 à 06:08 +0000, 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 that the intent of FcChar8* in Fontconfig is to represent
UTF-8 so this is probably worthy of a bug report to the Fontconfig people?
signature.asc
Description: This is a digitally signed message part
- 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 <=
- 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, 2024/01/13
- 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