Do I have to convert to kepub?

[Kamikuza]

Originally Posted by DNSB

Most of those spans and divs are added when converting from ePub to kepub. They are mostly used for locations for annotations and highlights. For non-Kobo devices, they are do-nothing code. Some people prefer to convert to ePub and then edit allowing calibre to convert the ePub on the fly when sending to the Kobo device.

So they basically aren't useful if you never annotate etc?

[Kamikuza]

Originally Posted by joblack

No, you can't zoom into images. It really sucks.

What about converting to kepub enables that?

[Kamikuza]

Originally Posted by JSWolf

If you want kerning, ligatures, and hyphenation, its not noticeably faster.

Is that why many emdash have a gap after them and before the next word, even though that's not in html?

eg. "this—not that" displayed as "this— not that"

I found that happened even with the kepub I converted... What about the kepub controls that?

[salamanderjuice]

Originally Posted by Kamikuza

What about converting to kepub enables that?

Nothing really. Kobos have two different renderers, one for kepubs and one for regular epubs. Only the kepub renderer allows zooming images. Converting to kepub just uses the kepub renderer correctly. You don't have to convert code to use the kepub renderer, renaming the file to *.kepub.epub is enough but without the extra code things like location won't be stored correctly.

[Apollyon202]

Originally Posted by salamanderjuice

Nothing really. Kobos have two different renderers, one for kepubs and one for regular epubs. Only the kepub renderer allows zooming images. Converting to kepub just uses the kepub renderer correctly. You don't have to convert code to use the kepub renderer, renaming the file to *.kepub.epub is enough but without the extra code things like location won't be stored correctly.

Wondering which of the two renderers consumes less battery overall, if...

[Kamikuza]

Originally Posted by salamanderjuice

Nothing really. Kobos have two different renderers, one for kepubs and one for regular epubs. Only the kepub renderer allows zooming images. Converting to kepub just uses the kepub renderer correctly. You don't have to convert code to use the kepub renderer, renaming the file to *.kepub.epub is enough but without the extra code things like location won't be stored correctly.

Thanks

So all the spans are location data, yeah?

[Quoth]

A larger font with bigger margins has more effect as the main power consumption, if frontlight & radios are off, is actual page turns or refreshes. There are less of these with a smaller font and small margins.

Obviously zooming uses more power. Otherwise for a static content, reflowable novel the power consumption to render is minor compared to actual display HW update.

[JSWolf]

Originally Posted by Kamikuza

Last time I tried KF8 it either didn't work at all or messed with my layout and css. I'm doing things differently now, I'll try it again.

I use HyphenateThis! with the epub to mobi conversion. It's an additional couple of steps though--and you have to clear it out of pages with SVG or it breaks AT LEAST the font control...

Calibre messes with me too, basically seems to rewrite my css completely and screws up layout, so I use Kindle Previewer to convert to mobi

Don't go anything > Mobi. Mobi is an obsolete and a very poor format. Go ePub > KF8 after you've edited the ePub as you want.

When I've edited ePub, I make sure the code is as simple as possible. Also, I check for errors using the calibre error checker and epubckeck in the editor. epubcheck is a plugin you'll need to install if you've not done so.

[DNSB]

Originally Posted by Kamikuza

Thanks

So all the spans are location data, yeah?

Pretty much yes.

[JSWolf]

Originally Posted by Kamikuza

So they basically aren't useful if you never annotate etc?

I'm not 100% sure, but it's possible the spans also help keep your reading position.

[JSWolf]

Originally Posted by Apollyon202

Wondering which of the two renderers consumes less battery overall, if...

It doesn't really make any noticeable difference.

[DNSB]

Originally Posted by Apollyon202

Wondering which of the two renderers consumes less battery overall, if...

In my limited testing, I did not notice a detectable difference in battery life between the two renderers.

[Kamikuza]

Originally Posted by JSWolf

Don't go anything > Mobi. Mobi is an obsolete and a very poor format. Go ePub > KF8 after you've edited the ePub as you want.

When I've edited ePub, I make sure the code is as simple as possible. Also, I check for errors using the calibre error checker and epubckeck in the editor. epubcheck is a plugin you'll need to install if you've not done so.

Yes I know that it's obsolete but it works very well for me--what I produce in Sigil is what it looks like on my Kindle. Almost perfectly. As I said, I'll try KF8 again...

Yeah Calibre goes mad adding div and span everywhere, makes the css file many times longer. I'm sure it's maximally compatible...but so long as it works on MY Kindle I'm happy with it... even if it's mobi :rofl

I know if it works... when it compiles I've only had one book not work and I haven't been able to figure out what was wrong with it... and it wasn't the mobi. Honest

[Kamikuza]

Originally Posted by DNSB

Pretty much yes.

How does it pick up the "Chapter Title" that gets displayed at the top of the screen?

Is there an app like Kindle Previewer so I can try and figure the kinks out...?

[JSWolf]

Originally Posted by Kamikuza

Yes I know that it's obsolete but it works very well for me--what I produce in Sigil is what it looks like on my Kindle. Almost perfectly. As I said, I'll try KF8 again...

Yeah Calibre goes mad adding div and span everywhere, makes the css file many times longer. I'm sure it's maximally compatible...but so long as it works on MY Kindle I'm happy with it... even if it's mobi :rofl

I know if it works... when it compiles I've only had one book not work and I haven't been able to figure out what was wrong with it... and it wasn't the mobi. Honest

That's wrong. The CSS does not have any divs and spans added to it. That's the HTML that has the spans added to it.

KF8 allows you to have your choice of font and to increase the weight if you want. Mobi is stuck with the so-so fonts Amazon supplies and Amazon prefers you use the really awful Bookerly.