Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 04-13-2014, 04:32 PM   #980
jgoguen
Generally Awesome Person
jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.
 
Posts: 1,100
Karma: 2191133
Join Date: Jan 2013
Location: /dev/kmem
Device: Kobo Clara HD, Kindle Oasis
Quote:
Originally Posted by cybmole View Post
so its not a "known issue" to you then ?

I have seen it with 3 out of 3 published books. meanwhile, someone else in another thread has selected a public domain book & sent 2 versions ( epub & kepup.epub) to their kobo reader device directly i.e. without calibre & without this plug in. They did not get this very small font effect. That outcome suggests that it is not just a "difference between renderers " thing. That test was done with a Kobo Glo thoguh,not the same device as my aura HD , if that's a factor

please see here https://www.mobileread.com/forums/sho...d.php?t=235018

I am unsure what test to try next: I do have a non standard font size key in my calibre preferences which is why I ask if the plug in looks there. ( I set that a while ago to change how small, large x-large values are changed in conversions but most books don't have those, so mostly the font size key is ignored i think ). Anyway the books I am testing with went through a calibre epub to epub conversion before they were ever sent to my Aura, as that is a standard workflow for me. Amongst other things it adds the no hyphenation property to book CSS for me.
The only other thing I do with books before sending to Kobo is to remove all explicit line-height, and font-family declarations from CSS so that all the on-device options are enabled. I have either no explicit font size for paragraph styles or I leave a simple 1em value in place if already present.

I guess the next obvious test is to fake up a one page test "book" with minimal CSS, e.g. via sigil, & send that both directly & via the plug-in ? to see how the font is then rendered.
- unless there's some way to bring one of the kepub.epub files back from the Aura onto my PC so that I can compare it's CSS with that of the original epub? I think they are buried inside the aura's database though ?

The CSS changes you're doing with calibre may or may not be part of the problem. Try a normal ePub, one you've never converted or edited, and put it on the device manually without using calibre. if it looks fine, send it as a KePub through calibre, but do not do any of your normal workflow - just add the book to calibre and send the book to your device. See what the fonts look like then.

KePub books are stored just like normal ePub books. The specific location is determined by your save template in the driver settings.
jgoguen is offline   Reply With Quote