CF Fonts beta: examples of problems
Have been told the
One thing to note for any other user finding this: where a font has a multi-word name, it’s important to make sure your website feeds the necessary
general-discussions channel isn’t where to report this, so will try here. (Tag choices didn’t really apply.) Re the Cloudflare Fonts beta: I created a mini-site to test how CFF handles Google’s Latin-language variable serif and sans-serif fonts that have italic styles. The ones which CFF currently doesn’t process correctly are the following, with links provided as examples:- Brygada 1918 (https://cfftest.brycewray.com/cff003/)
- Noto Serif (https://cfftest.brycewray.com/cff009/)
- Source Serif 4 (https://cfftest.brycewray.com/cff014/)
- DM Sans (https://cfftest.brycewray.com/cff022/)
- Exo 2 (https://cfftest.brycewray.com/cff024/)
- Kumbh Sans (https://cfftest.brycewray.com/cff033/)
- Roboto Condensed (https://cfftest.brycewray.com/cff042/)
- Source Sans 3 (https://cfftest.brycewray.com/cff047/)
One thing to note for any other user finding this: where a font has a multi-word name, it’s important to make sure your website feeds the necessary
link with an unescaped + between the font name’s words (e.g., Noto+Sans+Display for the Noto Sans Display font). I got help with that in the Hugo Discourse (https://discourse.gohugo.io/t/how-to-unescape-plus-sign-in-url-re-cloudflare-fonts/46734) but, if you’re using a different web-building tool, make sure it’s not escaping the + as &43#; since that appears to complicate things for CF Fonts.