lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Figured bass bug in 2.23.82?


From: Werner LEMBERG
Subject: Re: Figured bass bug in 2.23.82?
Date: Tue, 13 Dec 2022 05:47:29 +0000 (UTC)

>> What about adding
>>
>> ```
>> <dir>.../lilypond/XX.YY.ZZ/fonts/otf</dir>
>> ```
>>
>> at the top of `00-lilypond-fonts.conf`?  According to the
>> maintainer of FontConfig, first directory gets served first, and
>> the `00-*` file is read before anything else.
>
> I already tried this and it didn't work for me, but I don't know why.

OK.  Next try: The FontConfig maintainer suggests the following:

| If you want to pick up a font first where is available on certain
| font paths adding through FcConfigAppFontAddDir, you may want to use
| FcFontSetMatch and/or FcFontSetList instead of
| FcFontMatch/FcFontList with FcConfigGetFonts(config,
| FcSetApplication) and then fallback to FcSetSystem as needed,
| because FcFontMatch/FcFontList is always going through FcSetSystem
| and then FcSetApplication.

This might explain why LilyPond's font location isn't found first.

Another idea is to add patterns to the FontConfig setup files that
excludes all instances of the LilyPond fonts not being in the intended
font location.


    Werner



reply via email to

[Prev in Thread] Current Thread [Next in Thread]