MobileRead Forums - View Single Post - How to make Kobo's Kepub renderer do its job?

doubleshuffle · 03-21-2016, 11:53 AM

I normally stay away from kepubs, mainly because I don't like the mandatory header and detest those silly reading stats.

But now I have been forced to tinker with the format a little bit because it doesn't fail in one little detail where Kobo's standard epub renderer does. But the kepub renderer fall short in so many other ways:

It ignores
- "text-decoration: none" for links and underlines them anyway,
- "text-align: center" and
- "page-break-before:always" are both blithely ignored as well.

All three of the above work perfectly fine on the standard epub renderer, as well as in ADE and both Sigil's and Calibre's previews. They fail in the kepub renderer, no matter if I just change the file extension or run the file through Calibre's epub > kepub conversion plugin.

I must be doing something wrong; can't believe the renderer is that bad...

03-21-2016, 11:53 AM	#1
doubleshuffle Unicycle Daredevil Posts: 13,944 Karma: 185432100 Join Date: Jan 2011 Location: Planet of the Pudding Brains Device: Aura HD (R.I.P. After six years the USB socket died.) tolino shine 3	How to make Kobo's Kepub renderer do its job? I normally stay away from kepubs, mainly because I don't like the mandatory header and detest those silly reading stats. But now I have been forced to tinker with the format a little bit because it doesn't fail in one little detail where Kobo's standard epub renderer does. But the kepub renderer fall short in so many other ways: It ignores - "text-decoration: none" for links and underlines them anyway, - "text-align: center" and - "page-break-before:always" are both blithely ignored as well. All three of the above work perfectly fine on the standard epub renderer, as well as in ADE and both Sigil's and Calibre's previews. They fail in the kepub renderer, no matter if I just change the file extension or run the file through Calibre's epub > kepub conversion plugin. I must be doing something wrong; can't believe the renderer is that bad...