> On 10 Apr 2023, at 19:02, Jean Abou Samra <j...@abou-samra.fr> wrote: > > SNIP >
> Could you send the contents of the > /Users/michaelhendry/.config/fontconfig/fonts.conf file? It's in a hidden > folder (.config, which starts with a dot), so you will likely have to toggle > something to show hidden files/directories in the Finder. A Google search > suggests "Command Shift Dot". After doing that, you should see ".config" in > your home folder and find "fontconfig" then "fonts.conf" inside it. Send that > file. > > LilyPond uses a library called Fontconfig in order to find fonts on the > system. Fontconfig supports configuration files. Apparently yours is > corrupted, or maybe only valid with a recent version of Fontconfig that > LilyPond 2.24 doesn't have. It would be interesting to test the development > release 2.25.4, by the way. > Thanks, Jean, This is what’s in ~.config/fontconfig/fonts.conf: <?xml version="1.0" encoding="utf-8"?> <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <dir prefix="/System/Library/Fonts"/> </fontconfig> >> The lead-sheets deliver the same “Fontconfig…” error messages, but also >> include the following warnings: >> >> interpreting music... >> warning: cannot find property type-check for `markFormatter' >> (translation-type?). perhaps a typing error? >> warning: skipping assignment >> > You should always (yes, always) run convert-ly before trying old scores on > new versions. > > It will automatically fix the syntax of your file to be compatible with the > new version of LilyPond. > > Developers (like me) put awful amounts of efforts into making it work well. > It's a pity not to use that. > > In Frescobaldi, that's in Tools > Update with convert-ly. > I’ve tried that on these old files, but it doesn’t resolve the problem. Regards, Michael
