View Single Post
Old 04-02-2021, 08:16 AM   #12
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,467
Karma: 107078855
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
The basic issue I have is that if you use Embed fonts on the GUI the font file names have spaces, which Check in Editor objects to. The GUI option adds the font file URL in the page.css, but if you use Check in the Editor (or manually) to remove the spaces then some fonts don't work on the Kobo.

If you use Embed fonts in the Editor, then they are embedded with font file names without spaces. They are all added to a new fonts.css file. The HTML files are updated automatically to include this. In this case Check finds no issues. It seems to work 100% if you embed at the GUI and then delete all the font files and then after fonts.css is created you delete all the font entries in page.css, it then only has the viewport margins (5 by default. Using zero is abysmal in some apps. Negative is only for personal use on a kindle)
The CSS names may still have spaces, but those are "quoted" so not a problem.
Quoth is offline   Reply With Quote