Advantage of KF8 w/Kindle Keyboard?

markpearl · 07-30-2012, 04:27 PM

I have a Kindle Keyboard with ver. 3.3 firmware -- latest one I know of.

Recently I've been using the Calibre plugin tweak test_mobi_output_type = 'both' when converting ePub files to Mobi. The results are mostly much larger mobi files -- nothing more.

I know that Amazon's been porting their newer books to KF8, having re-downloaded some of my older purchases and seeing the new format and fatter files. But for the conversion purposes I mentioned, can anyone tell me the advantage given my Kindle model?

Thanks.

susan_cassidy · 07-30-2012, 04:37 PM

The Kindle Keyboard does not support KF8. Only .azw and .mobi. There hasn't been a firmware update to support it, and probably won't be. I belive that when given a KF8 file, it just displays the .mobi part.

Dopedangel · 07-31-2012, 01:29 AM

Quote:

Originally Posted by markpearl

I have a Kindle Keyboard with ver. 3.3 firmware -- latest one I know of.

Recently I've been using the Calibre plugin tweak test_mobi_output_type = 'both' when converting ePub files to Mobi. The results are mostly much larger mobi files -- nothing more.

I know that Amazon's been porting their newer books to KF8, having re-downloaded some of my older purchases and seeing the new format and fatter files. But for the conversion purposes I mentioned, can anyone tell me the advantage given my Kindle model?

Thanks.

Mobi does not support all formatting styles etc that epub does so converting from that to mobi you loose some things. If you are deleting your epubs after you convert I think you would be better of keeping your current settings. Currently your reader does not support kf8 but you might upgrade.

JSWolf · 08-03-2012, 05:56 PM

All the combined KF8/Mobi does for you is take up more space on your Kindle. You only can read from the mobi part.

Suggestion is to generate just mobi & keep the ePub for correcting error and in case you someday get a Kindle that supports KF8 without the line height bug.

07-30-2012, 04:27 PM	#1
markpearl Enthusiast Posts: 43 Karma: 576732 Join Date: Jun 2011 Device: Kindle	Advantage of KF8 w/Kindle Keyboard? I have a Kindle Keyboard with ver. 3.3 firmware -- latest one I know of. Recently I've been using the Calibre plugin tweak test_mobi_output_type = 'both' when converting ePub files to Mobi. The results are mostly much larger mobi files -- nothing more. I know that Amazon's been porting their newer books to KF8, having re-downloaded some of my older purchases and seeing the new format and fatter files. But for the conversion purposes I mentioned, can anyone tell me the advantage given my Kindle model? Thanks.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Is the Kindle Keyboard (K3) ever going to get KF8 support?	apastuszak	Amazon Kindle	25	12-05-2012 02:18 PM
Content KF8 only or combined KF8/Mobi	JSWolf	Amazon Kindle	9	06-03-2012 09:11 PM
Free (Kindle/Nook) Create Competitive Advantage with Innovation [Business]	ATDrake	Deals and Resources (No Self-Promotion or Affiliate Links)	1	01-09-2012 08:45 PM
Your vote - keyboard or no keyboard on Kindle	mrzerga	Amazon Kindle	56	03-10-2011 07:22 PM
Kindle (And Ereaders) Advantage on the Subway	poohbear_nc	News	32	09-08-2009 08:37 AM

07-30-2012, 04:37 PM	#2
susan_cassidy Wizard Posts: 2,251 Karma: 3720310 Join Date: Jan 2009 Location: USA Device: Kindle, iPad (not used much for reading)	The Kindle Keyboard does not support KF8. Only .azw and .mobi. There hasn't been a firmware update to support it, and probably won't be. I belive that when given a KF8 file, it just displays the .mobi part.

08-03-2012, 05:56 PM	#4
JSWolf Resident Curmudgeon Posts: 79,123 Karma: 144284184 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	All the combined KF8/Mobi does for you is take up more space on your Kindle. You only can read from the mobi part. Suggestion is to generate just mobi & keep the ePub for correcting error and in case you someday get a Kindle that supports KF8 without the line height bug.