Le Ven 25 octobre 2013 13:00, Richard Hughes a écrit : > On 25 October 2013 11:52, Akira TAGOH <tagoh@xxxxxxxxxx> wrote: >> Well, I have a plan to have a family class in the cache. it will be able >> to generate the summary like the above automatically with it I believe. >> That feature isn't yet merged into master because it requires bumping >> the cache version. > > Right. I need the font metadata before the font is installed; I'm > currently using fontTools for this. > >> Why don't you simply pick it up from the package description? it should >> has enough wording and having separate metadata looks duplicate to me >> though. > > Yes, I'll probably fall back to this. The big problem is the way some > fonts are split, and I want the description to be of the parent font, > and not the monospace version for example. Monospace *is* a different font family. The CSS and Microsoft-defined boundaries of a font family are anything that differs from another factor that width, weight and slope. Please try to follow the specs split and not invent yet another font classification, it's already hard enough with all the legacy baggage out there. https://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-components-postattachments/00-02-24-90-36/WPF-Font-Selection-Model.pdf Regards, -- Nicolas Mailhot _______________________________________________ fonts mailing list fonts@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/fonts http://fonts.fedoraproject.org/
