The thorny issue that `fontconfig` handles is mapping from a high-level specification of a font (e.g., family, weight, slant) — that is, how a user would typically specify a font — to an actual font file on disk.
The shortcoming with font filenames is that they don't reliably tell you anything about the font inside. So `fontconfig` digs out metadata from the file itself (IIUC) and uses this to guess which font file best suits your wishes. (Also, Racket ships with `fontconfig`, so it’s guaranteed to be available.) Most of `fontland` is esoteric nonsense, but for the benefit of future list spelunkers, here's how I used `fontconfig` (badly, perhaps) to solve this problem: https://github.com/mbutterick/fontland/blob/master/fontland/font-path.rkt > On Apr 1, 2020, at 8:14 PM, David Storrs <david.sto...@gmail.com> wrote: > > I knocked together a very minimal pure-Racket library for this so you > don't have to FFI. It won't give you all the bells and whistles, but > it should be a good starting point. > > https://pkgd.racket-lang.org/pkgn/package/font-finder > > Docs: https://github.com/dstorrs/font-finder/blob/master/README.md > > Newly arrived on a package server near you. > > ...where I note there is a newly-created package named 'fontland' that > was put up by Matthew and probably does all this and more. Doh. > > Well, hopefully this helps a little bit. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/4D36EF85-1278-42CF-AEAF-86C8822FF064%40mbtype.com.
