Conversion result from ePub to KF8 different than MOBI

CarlosL · 07-21-2012, 01:36 AM

Hello!

I'm having trouble achieving the same result with exporting ePub to Amazon (Kindle Touch) formats (MOBI and KF8) using Calibre. If I export to MOBI, the result is something very similar to Amazon's own style for eBook, but if I use KF8 at least line height is not the same as with MOBI.

MOBI version (good):

KF8 version (bad):

(Screenshots from Kindle Previewer in Kindle Touch Mode)

I tried with line height settings with no luck.

Any suggestion will be appreciated!

kovidgoyal · 07-21-2012, 01:38 AM

The Kindle Touch overrides line height. You cannot control it in KF8. The line height that the user will see depends on the line height setting they have on their Touch.

CarlosL · 07-21-2012, 11:45 AM

Thanks for your answer!

That's really bad, even selecting the lowest setting for line height in Kindle Touch leaves too much space! Is there any known workaround for this?

kovidgoyal · 07-21-2012, 11:46 AM

Not that I know of.

CarlosL · 07-21-2012, 12:03 PM

Thanks again!

Uh, no native support for EPUB and KF8 with issues, it really sucks!

Seems I'll have to use MOBI then, at least until Amazon releases a fix for this, since Kindle Fire doesn't seem to have this problem.

JSWolf · 07-21-2012, 11:08 PM

What I don't get is this... Amazon released firmware 5.1 with this line height bug and they didn't bother to fix it and went ahead and did it again for firmware 4.1. That's just not good planning.

07-21-2012, 01:36 AM	#1
CarlosL Junior Member Posts: 4 Karma: 10 Join Date: Jul 2012 Device: Kindle Touch	Conversion result from ePub to KF8 different than MOBI Hello! I'm having trouble achieving the same result with exporting ePub to Amazon (Kindle Touch) formats (MOBI and KF8) using Calibre. If I export to MOBI, the result is something very similar to Amazon's own style for eBook, but if I use KF8 at least line height is not the same as with MOBI. MOBI version (good): KF8 version (bad): (Screenshots from Kindle Previewer in Kindle Touch Mode) I tried with line height settings with no luck. Any suggestion will be appreciated!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Texte aus dem Bestand von Wikisource als E-Book (EPUB, Mobi teilweise KF8)	readx	E-Books	3	06-08-2012 10:58 AM
Content KF8 only or combined KF8/Mobi	JSWolf	Amazon Kindle	9	06-03-2012 10:11 PM
PDF to Mobi/Epub: How to Achieve Better Result With Mobipocket Creator	sinan	Workshop	1	02-09-2012 06:45 AM
EPUB to MOBI - result is outrageous	sebdea	Conversion	2	05-25-2011 02:03 PM
.epub to .mobi after conversion	illustrata	Conversion	9	05-10-2011 07:09 AM

07-21-2012, 01:38 AM	#2
kovidgoyal creator of calibre Posts: 44,697 Karma: 24967300 Join Date: Oct 2006 Location: Mumbai, India Device: Various	The Kindle Touch overrides line height. You cannot control it in KF8. The line height that the user will see depends on the line height setting they have on their Touch.

07-21-2012, 11:45 AM	#3
CarlosL Junior Member Posts: 4 Karma: 10 Join Date: Jul 2012 Device: Kindle Touch	Thanks for your answer! That's really bad, even selecting the lowest setting for line height in Kindle Touch leaves too much space! Is there any known workaround for this?

07-21-2012, 11:46 AM	#4
kovidgoyal creator of calibre Posts: 44,697 Karma: 24967300 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Not that I know of.

07-21-2012, 12:03 PM	#5
CarlosL Junior Member Posts: 4 Karma: 10 Join Date: Jul 2012 Device: Kindle Touch	Thanks again! Uh, no native support for EPUB and KF8 with issues, it really sucks! Seems I'll have to use MOBI then, at least until Amazon releases a fix for this, since Kindle Fire doesn't seem to have this problem.

07-21-2012, 11:08 PM	#6
JSWolf Resident Curmudgeon Posts: 77,148 Karma: 138591138 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	What I don't get is this... Amazon released firmware 5.1 with this line height bug and they didn't bother to fix it and went ahead and did it again for firmware 4.1. That's just not good planning.

Advert

Advert