Windows shows some sort of other font interface when one navigates to windows/fonts. It doesn't try to look like a normal directory. The Windows user does not have direct access to a folder named "windows/fonts", or if she or he does, I don't know how to find it. If installing a font correctly in the operating system doesn't give Lilypond access to it, I think it's fair to say that Lilypond is broken when handling text fonts in Windows.
On Sat, Jan 15, 2022 at 7:34 PM Kevin Pye <kjpl...@pye.id.au> wrote: > While my knowledge of Windows is extremely limited, my experience is that > Windows lies to you. If you use Windows Explorer to navigate to > c:\windows\fonts you will see a lot of fonts installed. If instead you open > a command window, cd to the same directory and run "dir", you will get a > different list. Presumably Windows Explorer is showing you all fonts the > system knows about, even when they are not installed in c:\windows\fonts. > > If lilypond is looking at the fonts directory, it will see only those > fonts in that directory, and not those installed elsewhere in the system, > > On Sun, 16 Jan 2022, at 12:14, Michael Rivers wrote: > > I'm pretty sure text fonts on Windows are kaput. Some work, some don't. > The fonts I'd like to use show up as installed properly in Settings and > work in all other apps I've tried, but not Lilypond. I'm on Windows 11, but > I've also tried on Windows 10. > > >
