View Single Post
Old 10-25-2014, 01:53 PM   #189
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by violent23 View Post
Some stock fonts do not display bold nor italics.
Firmware v3.11 does seem to have created a problem with Avenir Next (it was fine in v3.8). Amasis, Caecilia, Georgia, Gill Sans, Kobo Nickel, Malabar, OpenDyslexic all work correctly.

Quote:
Originally Posted by violent23 View Post
Widows and orphans have to be manually set through conversions, hacks on the device or editing each individual .ePubs css. Otherwise the default setting of the firmware will display .ePubs with pages where half the page has no text quite often.
Kobos make no attempt to override whatever widows/orphans are set in each epub's css. In the absence of any epub setting the css standard default of 2 is used, I believe. If you want to force a particular setting and you're a calibre user have you tried this option? A one-off task of creating a simple text file called kobo_extra.css on your Kobo hardly qualifies as hacking (IMHO). Having done it, all your epubs will have their widows/orphans set to exactly the values you've specified during the calibre send-to-device process with no effort from you required. No conversions, no individual editing. However, this wouldn't work if your epubs are DRM-infested.

Quote:
Originally Posted by violent23 View Post
The .ePub engine still ignores embedded fonts from the css.
Works OK for me in v3.11. Are you sure you remembered to select 'Document Default' from the font menu?

Quote:
Originally Posted by violent23 View Post
Annotations still have the problem with reopening .ePubs on the main memory messing up the percent read and the chapter the book is in.
You may well be right about this. I don't use annotations so I wouldn't know.
jackie_w is offline   Reply With Quote