Looking for Kindle Previewer < 3.49 installer

[Quoth]

Originally Posted by DNSB

Seeing as Amazon does not support epub on their ereaders or apps, I find it humourous that they recommend that format for creating/editing ebooks.

So to answer your question, both.

They don't support docx either on ereaders or kindle app. They have very different kindles to support.
Hence best upload is epub2 and second best upload for kdp is docx.

Publishing on paper ideally uses a print ready PDF. Amazon's recent idea that you can do paper edition from a source meant for ebooks is madness. They used to want PDF for that, that exactly matched paper size.

[Hitch]

Originally Posted by slonopotamus

I mean this is what Kindle Previewer 3.51 says if I try to open KF8 file with it:


This is the file itself: https://github.com/slonopotamus/dyck...mple-book.mobi

Yes, and they've been popping up warnings about using files created by unsupported programs, in unsupported formats, for some time now.

There is a DIFFERENCE between a "dual mobi" created by Kindlegen, via KG through the CL, or through Previewer, and the "dual mobi" format (AZW) that's created by Calibre. They are not the same thing--in Amazon's eyes.

If you want to publish a proper file at Amazon, today, just upload a bloody ePUB. Getting an older version of Kindlegen won't help you. By 6/28, MOBI files will no longer be accepted, no matter how they are made. So, trying to find a version of KindlePreviewer that won't pop up the warning is...counterproductive. I can't think of a great analogy for that now, but the reality is, you have to embrace what Amazon will accept, going forward, not try to shoehorn in an older format with which you cannot really accomplish anything, publishing-wise.

(Can't wait to see what Smashwords is planning to do, as they use the Calibre API, AFAIK....)

Hitch

[jhowell]

Originally Posted by slonopotamus

This is the file itself: https://github.com/slonopotamus/dyck...mple-book.mobi

That file was produced using Amazon's kindlegen despite the message from Kindle Previewer. It fails to open because it was created using the "-dont_append_source" option which results in a file stripped of data needed for conversion to KFX (Enhanced Typesetting).

[Hitch]

Originally Posted by jhowell

That file was produced using Amazon's kindlegen despite the message from Kindle Previewer. It fails to open because it was created using the "-dont_append_source" option which results in a file stripped of data needed for conversion to KFX (Enhanced Typesetting).

See? This is why jhowell is my hero.

(Nonetheless....the rest of what I said is still accurate. Don't try to find an older Previewer.)

Hitch

[Quoth]

Originally Posted by Hitch

If you want to publish a proper file at Amazon, today, just upload a bloody ePUB. Getting an older version of Kindlegen won't help you. By 6/28, MOBI files will no longer be accepted, no matter how they are made.

...

(Can't wait to see what Smashwords is planning to do, as they use the Calibre API, AFAIK....)

Smashwords have two well known retailers they don't supply:
1) Amazon
2) Google (PlayStore PlayBooks).

What Amazon accepts as KDP upload is irrelevant to Smashwords.

They have some prehistoric conversion process that only uses MS-DOC and the results are not great. You can upload epub direct and/or mobi for Kindle, then whatever isn't uploaded is provided via their ms doc input conversion.

Unlike Amazon, Smashwords doesn't know what sort of Kindle you have. Amazon create at least three Kindle versions from the uploaded epub2 or docx. They ask which it's for if you have more than one Kindle. Kindle apps count as different kindle models.

The Calibre created Dual Mobi from epub2 does KF7 on really old Kindles, choice of KF7 or KF8 on some (Publisher option gives KF8) and on later ones KF8 only with the usual Amazon font fall backs (vary per kindle) unless the user selects Publisher which does give the same appearance as an epub2 ereader using the embedded fonts.

I use DXG, Kindle Keyboard 3, Paperwhite 3 and Kindle Android to test if we do a new paragraph style. In such a case we might not trust the preview file offered by Amazon after epub2 upload, but test purchase in UK and USA on two different kindles.
I also test epub2 on Aldiko (4.3" phone), Lithium (6" phone, 7" & 10" tablets), Sony PRS-350, Kobo Libra and on Koreader on an 8" eink.

Calibre viewer just to see TOC, links, format. It works perfectly with ebooks that are actually broken on an ereader.

We make sure changing margins, line spacing and font works as well as all embedded fonts are correct on the Libra. If it's broken there, it's broken everywhere except maybe the Calibre Viewer.

So we upload epub2 (same one) to Google, Amazon and Smashwords.
We upload dual-mobi made from that epub to Smashwords for Kindle.
We upload an MS doc also to Smashwords.

You don't get samples created unless you let Smashwords do everything from an ms doc. Which is poor!
So we are now adding sample PDF, epub2, dual-mobi and audio to our web site. People can see online a sample or download a sample from Amazon even if they have only epub ereader. We have no DRM.

So anyway, what Amazon accepts as KDP upload is irrelevant to Smashwords.

A difference with our own samples:
We end the full text at a suitable point.
The full TOC/NCX (Index) works as we leave a sentence or a paragraph at the start of every chapter.

[slonopotamus]

Originally Posted by Hitch

Yes, and they've been popping up warnings about using files created by unsupported programs, in unsupported formats, for some time now.

There is a DIFFERENCE between a "dual mobi" created by Kindlegen, via KG through the CL, or through Previewer, and the "dual mobi" format (AZW) that's created by Calibre. They are not the same thing--in Amazon's eyes.

That file was created by official kindlegen app, Calibre was not involved in any way.

Originally Posted by Hitch

If you want to publish a proper file at Amazon, today, just upload a bloody ePUB.

I do not want to publish to Amazon. I just want to view an existing file.

Originally Posted by jhowell

That file was produced using Amazon's kindlegen despite the message from Kindle Previewer. It fails to open because it was created using the "-dont_append_source" option which results in a file stripped of data needed for conversion to KFX (Enhanced Typesetting).

If you run kindlegen without "-dont_append_source", then original EPUB is saved into mobi file (together with KF6/8). And modern Kindle Previewer uses that original EPUB data for preview (unlike ebook reading app/device that would use KF8 data). So, previewing files without "-dont_append_source" is cheating because you see not what you actually want to see.

And I don't want to convert the file to KFX, I just want to preview what is already present in file.

[Quoth]

Originally Posted by slonopotamus

I do not want to publish to Amazon. I just want to view an existing file.

Then use cross platform Calibre Viewer. It works standalone from Calibre.

[jhowell]

Originally Posted by slonopotamus

And I don't want to convert the file to KFX, I just want to preview what is already present in file.

For the best preview of MOBI and KF8 files I recommend using an even older Previewer 2.x version. That software predates KFX and emulates various older Kindle devices. It will render either part of a Master MOBI depending on the device selected.

[JSWolf]

Use Calibre with the KindleUnpack plugin and split the file into KF8/Mobi and try just the KF8 part and see what happens.

[Hitch]

Originally Posted by Quoth

Smashwords have two well known retailers they don't supply:
1) Amazon
2) Google (PlayStore PlayBooks).

What Amazon accepts as KDP upload is irrelevant to Smashwords.

Quoth, dear: it's not irrelvant to the people who BUY Kindle formats from SW, now is it, if they have become accustomed to ET (Enhanced Typesetting) from Amazon. Right?

If the only practical way for a Calibre-mobi to also have hyphenation and ET is by added plugins, then the reader will not have the same experience as s/he would with an Amazon-produced file. That's my point.

Hitch

[Quoth]

Originally Posted by Hitch

Quoth, dear: it's not irrelvant to the people who BUY Kindle formats from SW, now is it, if they have become accustomed to ET (Enhanced Typesetting) from Amazon. Right?

If the only practical way for a Calibre-mobi to also have hyphenation and ET is by added plugins, then the reader will not have the same experience as s/he would with an Amazon-produced file. That's my point.

Hitch

Only Amazon can properly supply KFX.

Actually most people won't notice the difference. Amazon could update the KF8 renderer in the ereaders and apps. But KFX is really about DRM.
IMO as an epub2 is often used to generate KFX, the KF8 files could be rendered identically.

Smashwords don't know what sort of kindle you have, and for some it's not the model, but firmware level. Amazon does know, so can deliver KF7, KF8 or KFX. Actually they have a few other format too.

There is no sensible way for Smashwords or anyone else to do KFX other than by offering TWO Kindle download options, a dual KF7-KF8 and a KF8. That would be confusing as most people have no idea what Kindle formats their ereader or app does.
The dual Mobi will work on anything that does KFX and look nearly as good.

Also as Smashwords doesn't even make as good Mobi or epub from the default doc upload as people can from a GOOD docx (which is why they offer Direct upload for mobi & epub), I can't see them supporting KFX.

KFX and kepub are both nasty formats with small visual enhancements to distract from the fact that they are about DRM. Any KF8 renderer could easily be updated for the Enhanced Typesetting. It's the SAME source ebooks!
The Kobos could have an epub renderer that adds the features of kepub, except kepub actually gets some CSS wrong!

KFX is an example of the Big Publishers being obsessed by DRM and letting Amazon call the shots and a symptom of lack of regulation of big USA corporations.

[Hitch]

Originally Posted by Quoth

Only Amazon can properly supply KFX.

Actually most people won't notice the difference. Amazon could update the KF8 renderer in the ereaders and apps. But KFX is really about DRM.
IMO as an epub2 is often used to generate KFX, the KF8 files could be rendered identically.

Smashwords don't know what sort of kindle you have, and for some it's not the model, but firmware level. Amazon does know, so can deliver KF7, KF8 or KFX. Actually they have a few other format too.

There is no sensible way for Smashwords or anyone else to do KFX other than by offering TWO Kindle download options, a dual KF7-KF8 and a KF8. That would be confusing as most people have no idea what Kindle formats their ereader or app does.
The dual Mobi will work on anything that does KFX and look nearly as good.

Also as Smashwords doesn't even make as good Mobi or epub from the default doc upload as people can from a GOOD docx (which is why they offer Direct upload for mobi & epub), I can't see them supporting KFX.

KFX and kepub are both nasty formats with small visual enhancements to distract from the fact that they are about DRM. Any KF8 renderer could easily be updated for the Enhanced Typesetting. It's the SAME source ebooks!
The Kobos could have an epub renderer that adds the features of kepub, except kepub actually gets some CSS wrong!

KFX is an example of the Big Publishers being obsessed by DRM and letting Amazon call the shots and a symptom of lack of regulation of big USA corporations.

Yes, dear, but my point really was....when ET first showed up, I confess to being a bit dismissive. Right? "meh, so what, stop inconveniencing me, Amazon, with all this drivel about tables forcing ET to not work, yadda."

BUT....I realized, after a very short period of time, that when I was then reading some PD stuff, near-direct from Gutenberg, that I really MISSED ET. (ET, Phone home!). I found it distracting to read the gappy, rivered, no-hyphens, etc. stuff. I suffered through one Philo Vance, and then promptly gave up and produced them again, for myself, using this, that and the hyphenation plugin over at Calibre. (Yes. yes, yes, I touched Calibre!)

It was very noticeable to me. And I don't mean in my professional life. I mean in my "as a reader" life. The place where I turn off my editorial, proofreading, bookmaker-brain and just try to enjoy. And it was vexatious to me. I couldn't ignore that this particular set of PD books was simply not "as nice" to read as (gasp), the post-ET eBooks.

{shrug}

That's it. That's all I'm saying. It's hard to ignore, once you see it. I do not concur with your opinion that most won't notice it.

I agree with what you say--there's no good way for SW to emulate what Amazon has done nad I agree that KFX is, definitely, absolutely, surely about DRM, more than layout--but nonetheless, layout matters.

Hitch

[JSWolf]

If I do read a KF8, I add soft hyphens to it. I also use ChareInk as my font of choice so the line-height is not so wide. And I use negative margins to lessen the overly wide L/R margins. I've also noticed that a lot of KF8 have a 7% paragraph indent which I fix to 1.2em. I also remove any paragraph spacing.

But with KFX, ChreInk does not work to reduce the line height. So KFX is not as good to read. So I think KFX is about control as well as DRM. Amazon wants to control your reading. And now it seems that Amazon is making some eBook KFX only.

[Quoth]

Originally Posted by Hitch

That's it. That's all I'm saying. It's hard to ignore, once you see it. I do not concur with your opinion that most won't notice it.

I agree with what you say--there's no good way for SW to emulate what Amazon has done nad I agree that KFX is, definitely, absolutely, surely about DRM, more than layout--but nonetheless, layout matters.

I now only use my kindles to test. I read any Amazon books now on Kobo Libra (native epub), or the Likebook Mars (with koreader). Both render better than a PW3 with KF8.

I agree layout matters and it's ONLY about DRM. The change needed to Amazon firmware of KF8 rendering is trivial. Even the Kindle Keyboard 3 could render EXISTING files on it better.