[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: |
Werner LEMBERG |
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 20:08:24 +0000 (UTC) |
> 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?
Indeed. To do so it would be helpful to check the output of `fc-list`
(ideally with proper patterns to make the result more similar to
LilyPond's output). Nathan, since you sit at the 'source' of the
problem, please also send a report to the FontConfig people if your
time allows it.
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues
Werner
- 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, 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 <=
- 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