MobileRead Forums - View Single Post

Insalata · 11-07-2011, 03:21 PM

I've removed the incompatible font, and realised that the reason the checker thought my font files weren't where they were supposed to be is that I stuck just the .css file online to get a link to submit for checking - so that's not a real problem.

So the errors that are left are all: "Property font-family doesn't exist in CSS level 2.1 but exists in [css1, css2, css3]"

It now seems that the Didot fonts are displaying properly in Adobe and Sony Readers, but not the AppleGothic one, which I was only using for one character that I liked as a section separator.

Thanks for your help.

The problem seemed to be with the font naming - picking up the info from FontBook and editing the css sheet in Sigil fixed it. I'm not sure if that's because the fonts I picked were awkward, or if it's a general problem.

11-07-2011, 03:21 PM	#53
Insalata Zealot Posts: 100 Karma: 2092 Join Date: Sep 2011 Location: UK Device: Kobo Sage, iPad	I've removed the incompatible font, and realised that the reason the checker thought my font files weren't where they were supposed to be is that I stuck just the .css file online to get a link to submit for checking - so that's not a real problem. So the errors that are left are all: "Property font-family doesn't exist in CSS level 2.1 but exists in [css1, css2, css3]" It now seems that the Didot fonts are displaying properly in Adobe and Sony Readers, but not the AppleGothic one, which I was only using for one character that I liked as a section separator. Thanks for your help. The problem seemed to be with the font naming - picking up the info from FontBook and editing the css sheet in Sigil fixed it. I'm not sure if that's because the fonts I picked were awkward, or if it's a general problem. Last edited by Insalata; 11-09-2011 at 04:19 AM.