View Single Post
Old 10-20-2020, 01:00 PM   #42
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,902
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by davidfor View Post
The calibre viewer will open kepubs. But, it will just treat them as an epub. Which they are. The difference is on the Kobo devices were kepubs use a different renderer than epubs. And most of the differences are down to the renderer.

I'm pretty sure that the question is about what happens on the device. And I don't believe it is possible, to get multiple columns for a kepub. If I remember correctly, that is implemented by the RMSDK, not the renderer used for kepubs.
Strictly speaking, if you add "columns: x;" to the CSS, you will get x number of columns. That would apply to all orientations though unlike RMSDK where it will automagically go to 2 columns (or 3 columns for the Aura One/Forma) when the number of characters on a line exceeds the limits.
DNSB is offline   Reply With Quote