Due to Celiagg using Windows font rendering, the selection of fonts needs to work a bit differently on Windows.
With FreeType, a celiagg.Font gets passed the path to the font file being loaded (along with a face index if it's a font collection). But with Windows, the first argument of celiagg.Font is a face name that gets passed to CreateFont.
To work around this, all we need to do is use kiva.Font.findfontname() on Windows and continue using kiva.Font.findfont() on other platforms.
Due to Celiagg using Windows font rendering, the selection of fonts needs to work a bit differently on Windows.
With FreeType, a
celiagg.Fontgets passed the path to the font file being loaded (along with a face index if it's a font collection). But with Windows, the first argument ofceliagg.Fontis a face name that gets passed toCreateFont.To work around this, all we need to do is use
kiva.Font.findfontname()on Windows and continue usingkiva.Font.findfont()on other platforms.