Author Topic: Amazon now "prefers" epub files to mobi files (Read 3555 times) Tweet

Triceratops · « **on:** October 05, 2020, 07:10:43 am »

In short: Amazon now doesn't want mobi files, they want epub files. So if you use Vellum, you need to go into your settings and change the output (for Amazon) to "epub for Kindle." If you don't see that setting, you need to update your Vellum.

There's not much consistency on Amazon's side, so far. Some people claim they are uploading mobi files just fine. Others are reporting they are encountering difficulties.

But, Amazon now says "We recommend submitting EPUB files for publishing reflowable content. MOBI is not recommended for reflowable content. Kindle Previewer is the best way to validate your EPUB content before publishing. We no longer recommend sideloading eBooks to devices for testing. Sideloading does not provide an accurate preview of Enhanced Typesetting features."
https://kdp.amazon.com/en_US/help/topic/G79CTKR8BX79E96L

If you open a mobi file in Kindle Previewer, you'll probably see this warning.

But to be clear, Amazon still supports the mobi format. They just don't recommend it: "We support books in MOBI and EPUB format that meet the specifications outlined in the Kindle Publishing Guidelines. If your MOBI file contains reflowable content (i.e. text-heavy books), we recommend you upload an EPUB file instead. Before uploading, we recommend validating the file with Kindle Previewer." [bolding in original]
https://kdp.amazon.com/en_US/help/topic/G200634390

The Vellum folks say you should not upload a generic epub file. Your links in the ebook will be wrong, and the Look Inside won't look right. You should upload the Vellum-outputted "epub for Kindle" file.

Vellum explains more in a recent blog post.
https://blog.vellum.pub/2020/09/amazon-would-prefer-an-epub-file

If you distribute ARCs via BookFunnel, give BookFunnel the "epub for Kindle" file and BookFunnel will convert it to the proper mobi for Kindle readers.

* Edit: expanded post title for clarity.

KBoards.com

Kathy Dee · « **Reply #1 on:** October 05, 2020, 08:28:07 am »

Interesting. I have been using EPUB for a while now, produced by converting from Word, using Calibre. Have had no problems at all.

Decon · « **Reply #2 on:** October 05, 2020, 08:58:25 am »

The title of this post is misleading though correct if you normally upload. Mobi.

Their preferred files are Word Files, or those produced via kindle create.

"Supported eBook Formats
You can upload and convert your eBook manuscript file from several supported formats. For the best results, we recommend a Microsoft Word DOC/DOCX or a KPF file created with Kindle Create. As you prepare your eBook, consider whether your content should have a fixed or reflowable format."

This makes sense seeing as how their conversion software was originally coded with Word as the go to software for the majority of authors at the time, especially as literary agents required files in Word format.

https://kdp.amazon.com/en_US/help/topic/G200634390

Triceratops · « **Reply #3 on:** October 05, 2020, 09:55:34 am »

Quote from: Decon on October 05, 2020, 08:58:25 am

The title of this post is misleading though correct if you normally upload. Mobi.

Their preferred files are Word Files, or those produced via kindle create.

"Supported eBook Formats
You can upload and convert your eBook manuscript file from several supported formats. For the best results, we recommend a Microsoft Word DOC/DOCX or a KPF file created with Kindle Create. As you prepare your eBook, consider whether your content should have a fixed or reflowable format."

This makes sense seeing as how their conversion software was originally coded with Word as the go to software for the majority of authors at the time, especially as literary agents required files in Word format.

https://kdp.amazon.com/en_US/help/topic/G200634390

Fair point about the post title. I edited it.

There's nothing wrong with uploading a Word file to Amazon. But if you distribute ARCs, such as via BookFunnel, you'll need to convert the Word file somehow. For folks who use Vellum it's good info to know.

Triceratops · « **Reply #4 on:** October 05, 2020, 10:01:34 am »

Quote from: Kathy Dee on October 05, 2020, 08:28:07 am

Interesting. I have been using EPUB for a while now, produced by converting from Word, using Calibre. Have had no problems at all.

Can you check the sales page of one of your books? Does the typesetting of the Look Inside sample appear okay? Just curious!

Kathy Dee · « **Reply #5 on:** October 06, 2020, 02:20:56 am »

Quote from: Triceratops on October 05, 2020, 10:01:34 am

Can you check the sales page of one of your books? Does the typesetting of the Look Inside sample appear okay? Just curious!

I have somewhere >30 books up there and I do check the 'look inside' from time to time. What I will say is that I have noticed some variability in the formatting of certain books, specifically with regard to line spacing, which I have never before thought about. It is not enough for me to worry about, but perhaps it may be due to the differences between a generic EPUB and the kind of specialised EPUB that can be output by Vellum.

Decon · « **Reply #6 on:** October 06, 2020, 02:47:56 am »

I'm wondering if it's to do with problems on occasion with the look inside also if you upload a mobi. I've always understood that the look inside uses a different conversion to that of the ebook to set up from whatever doc you've uploaded. I'm not technical, but isn't the look inside html as it is on a web page?

I've always uploaded a Word doc, but with regards to arcs, I've never had a problem converting to mobi using calibre and I've done many for both me and my clients who I format e-books for. The only difference between an Amazon conversion and one through calibre or any other outside software is that because the book is not bought from amazon, it only shows a generic cover in the kindle device library, so I usually add a cover to the file for arcs.

Triceratops · « **Reply #7 on:** October 06, 2020, 06:09:53 am »

Quote from: Kathy Dee on October 06, 2020, 02:20:56 am

I have somewhere >30 books up there and I do check the 'look inside' from time to time. What I will say is that I have noticed some variability in the formatting of certain books, specifically with regard to line spacing, which I have never before thought about. It is not enough for me to worry about, but perhaps it may be due to the differences between a generic EPUB and the kind of specialised EPUB that can be output by Vellum.

Hate to push the imposition, but could you purchase a copy of your most-recent upload and check the links? The Vellum blog says that amazon-store-specific links (as opposed to universal links) in generic epub uploads will "likely" be "wrong." If you use universal links, never mind.

C. Gockel · « **Reply #8 on:** October 06, 2020, 06:56:25 am »

I just uploaded a Vellum created MOBI file without any problems.

Triceratops · « **Reply #9 on:** October 06, 2020, 07:24:36 am »

Quote from: C. Gockel on October 06, 2020, 06:56:25 am

I just uploaded a Vellum created MOBI file without any problems.

Right, Amazon still supports mobi. Amazon however does not recommend mobi. They recommend uploading an epub instead.

My understanding is that this is related to Enhanced Typesetting. Line spacing, fonts, justification etc. may be off in mobi.

You can try checking your file on a latest-os-updated Kindle that uses Enhanced Typesetting. Or Kindle Previewer, but you'll probably get the error message in the Previewer.

I'd be curious to see if you discern any differences in the typesetting.

Kindle readers with Enhanced Typesetting:

Enhanced Typesetting is supported on the following devices and applications:

Kindle E-readers 6th generation and newer
Fire tablets 3rd generation and newer
Kindle for iOS v4.9 or newer (iOS Versions: iOS 7, iOS 8 and iOS 9)
Kindle for Android v4.18.0 or newer (Android Versions: Jelly Bean, KitKat, Lollipop, and Marshmallow)
Most of our customers read on devices that support Enhanced Typesetting. Customers who use older devices receive a KF8 version of the title.

To find out the generation of your Kindle E-reader or Fire tablet:

Which Kindle E-reader do I have? https://www.amazon.com/gp/help/customer/display.html/?nodeId=201263790
Which Fire Tablet do I have? https://www.amazon.com/gp/help/customer/display.html/?nodeId=201263780

If your device doesn't support Enhanced Typesetting features and your book's source content was uploaded in EPUB, MOBI, or HTML formats, you can use Kindle Previewer 3 to preview how your book will look before you publish. https://kdp.amazon.com/en_US/help/topic/G202131170

https://kdp.amazon.com/en_US/help/topic/G202087570

* Edit: Enhanced Typesetting stuff.

Gessert Books · « **Reply #10 on:** October 06, 2020, 07:38:14 am »

Quote from: Decon on October 06, 2020, 02:47:56 am

I'm wondering if it's to do with problems on occasion with the look inside also if you upload a mobi. I've always understood that the look inside uses a different conversion to that of the ebook to set up from whatever doc you've uploaded. I'm not technical, but isn't the look inside html as it is on a web page?

I've always uploaded a Word doc, but with regards to arcs, I've never had a problem converting to mobi using calibre and I've done many for both me and my clients who I format e-books for. The only difference between an Amazon conversion and one through calibre or any other outside software is that because the book is not bought from amazon, it only shows a generic cover in the kindle device library, so I usually add a cover to the file for arcs.

There are actually a number of differences between a calibre-created mobi and one generated using Amazon's tools. A couple of those differences may have played a part in the new language around epub here. Calibre mobi files are not dual-mobi files, so a buyer will not necessarily receive a version optimized for their device. They also don't support enhanced typesetting. So this new wording helps discourage use of non-standard publishing tools like that. As for more standard ones like kindlegen, I imagine it benefits Amazon to be able to continually retool the final conversion on the backend without worrying about what version we happen to be running locally.

Doglover · « **Reply #11 on:** October 06, 2020, 08:48:34 am »

Quote from: Kathy Dee on October 05, 2020, 08:28:07 am

Interesting. I have been using EPUB for a while now, produced by converting from Word, using Calibre. Have had no problems at all.

I just upload the Word file .docx

Rick Gualtieri · « **Reply #12 on:** October 06, 2020, 01:51:37 pm »

I won't lose any sleep if I don't have to create mobi files ever again. I switched to KPF for most of my books a while back.

That said, it would be nice if they updated the kindle software and apps to allow sideloading by those other formats, that way we could definitely leave mobi behind.

Kathy Dee · « **Reply #13 on:** October 07, 2020, 03:54:40 am »

Quote from: Doglover on October 06, 2020, 08:48:34 am

I just upload the Word file .docx

I started doing this when I was wide, just out of convenience. But I noticed the EPUB produced better - more consistent - results with formatting. So I have stuck with it, and have found no reason to change yet. However, at some stage, I think I should investigate the new version of Kindle Create.

Kathy Dee · « **Reply #14 on:** October 07, 2020, 03:59:56 am »

Quote from: Triceratops on October 06, 2020, 06:09:53 am

Hate to push the imposition, but could you purchase a copy of your most-recent upload and check the links? The Vellum blog says that amazon-store-specific links (as opposed to universal links) in generic epub uploads will "likely" be "wrong." If you use universal links, never mind.

As it happens, I accidentally purchased one of my books a few days ago. I was just checking stuff and accidentally clicked the 'one click' purchase button inside one of those hover boxes. Anyway, I have just checked it in my Kindle reader, and the links work fine. In this particular book they happen to be amzn.to links, which is unusual for me - I usually use Books2read. Hope this helps a bit.

TromboneAl · « **Reply #15 on:** October 07, 2020, 11:07:44 am »

I'm minutes from uploading a new book.

I use Scrivener to create my ePubs and MOBIs. Anyone know if I can expect any problems/differences if I upload the Scrivener-produced ePub?

>I won't lose any sleep if I don't have to create mobi files ever again.

I'd love to have everyone switch to ePub. I had multiple standards (slotted, Phillips head, square drive, star drive, aargh!).

Triceratops · « **Reply #16 on:** October 07, 2020, 11:40:47 am »

Quote from: Kathy Dee on October 07, 2020, 03:59:56 am

As it happens, I accidentally purchased one of my books a few days ago. I was just checking stuff and accidentally clicked the 'one click' purchase button inside one of those hover boxes. Anyway, I have just checked it in my Kindle reader, and the links work fine. In this particular book they happen to be amzn.to links, which is unusual for me - I usually use Books2read. Hope this helps a bit.

Very informative, thanks!

Triceratops · « **Reply #17 on:** October 07, 2020, 11:45:59 am »

Quote from: TromboneAl on October 07, 2020, 11:07:44 am

I'm minutes from uploading a new book.

I use Scrivener to create my ePubs and MOBIs. Anyone know if I can expect any problems/differences if I upload the Scrivener-produced ePub?

>I won't lose any sleep if I don't have to create mobi files ever again.

I'd love to have everyone switch to ePub. I had multiple standards (slotted, Phillips head, square drive, star drive, aargh!).

You can check it in Kindle Previewer 3. ~~You'll most likely get the error message re epub files. But if KP3 allows you to keep going after you click OK,~~ you should be able to see how the spacing, images, tables, kerning, drop caps etc look. Also if your links work right.

https://www.amazon.com/gp/feature.html?docId=1003018611

* Edit: my error.

alhawke · « **Reply #18 on:** October 07, 2020, 12:25:38 pm »

All this sounds more convenient to me. One file for all retailers is better, imo.

I have uploaded books as Epubs onto Amazon a couple months ago. I've also uploaded mobi for others. At the moment, I don't think it makes any difference on Amazon. I always just do a quick run-through with their previewer before publishing.

Sounds like they just might get rid of the mobi option completely in the future.

Mip7 · « **Reply #19 on:** October 07, 2020, 12:56:20 pm »

I also use Calibre and usually make both -- but I have noticed problems with the ePub files sometimes, and less often with the mobis, so I like being able to swap them if needed. Swapping the upload file type has a 100% success record with me so far fixing undesirable display issues (and I've done that maybe a half-dozen times)

AaronShep · « **Reply #20 on:** October 07, 2020, 04:29:30 pm »

They've been preferring EPUB for years, because that's what the Kindle format is now based on. All non-KDP publishers are expected to supply EPUB only. If you're only noticing the preference now, it's because they're just getting pushier about it.

Triceratops · « **Reply #21 on:** October 08, 2020, 05:14:52 am »

Quote from: AaronShep on October 07, 2020, 04:29:30 pm

They've been preferring EPUB for years, because that's what the Kindle format is now based on. All non-KDP publishers are expected to supply EPUB only. If you're only noticing the preference now, it's because they're just getting pushier about it.

I don't think most people knew or cared about Amazon's preference before, because it didn't seem to really matter. But now things seem to be changing. A mobi file triggers a big warning pop-up in Kindle Previewer. That's new.

More to the point, if Vellum is right, and a generic epub file is a no-no, that's also news.

https://blog.vellum.pub/2020/09/amazon-would-prefer-an-epub-file/

So Vellum seems to be saying that a generic epub file generated by Scrivener, Calibre, Sigil, etc, will be wrong. Vellum seems to be saying that a Kindle.epub file generated by Vellum is now the only way to go, for Amazon.

https://help.vellum.pub/generating/kindle-ebook-format/

I guess the question is, why?

Gessert Books · « **Reply #22 on:** October 08, 2020, 06:32:55 am »

No, there is nothing wrong with a generic (lowercase g) epub made using any of those tools. Vellum uses "Generic" (capital G) to describe a Vellum-specific output file that is platform-agnostic, they aren't using it to describe epub files made using other tools.

Kathy Dee · « **Reply #23 on:** October 08, 2020, 08:07:00 am »

Quote from: Gessert Books on October 08, 2020, 06:32:55 am

No, there is nothing wrong with a generic (lowercase g) epub made using any of those tools. Vellum uses "Generic" (capital G) to describe a Vellum-specific output file that is platform-agnostic, they aren't using it to describe epub files made using other tools.

Aha!

That clears it up.

Thanks

Triceratops · « **Reply #24 on:** October 08, 2020, 08:15:55 am »

Quote from: Gessert Books on October 08, 2020, 06:32:55 am

No, there is nothing wrong with a generic (lowercase g) epub made using any of those tools. Vellum uses "Generic" (capital G) to describe a Vellum-specific output file that is platform-agnostic, they aren't using it to describe epub files made using other tools.

Thank you!

But, how is the upper-G Generic epub from Vellum different from the epub generated by the others? And how is the Vellum Kindle.epub version the same; or is it?

I'll head over to the Vellum thread and see if I can get the Vellum guy to chime in, too.

KBoards.com

Gessert Books · « **Reply #25 on:** October 08, 2020, 08:39:41 am »

Quote from: Triceratops on October 08, 2020, 08:15:55 am

Thank you!

But, how is the upper-G Generic epub from Vellum different from the epub generated by the others? And how is the Vellum Kindle.epub version the same; or is it?

I'll head over to the Vellum thread and see if I can get the Vellum guy to chime in, too.

That would be the best place to ask and I'll watch there too. My best guess is that some Kindle and Look Inside friendly CSS/ media queries will be absent, and the store link thing is because most storefronts require you to link back only to themselves. I believe capital G Generic keeps it flexible by prompting you to link to your website instead.

Triceratops · « **Reply #26 on:** October 08, 2020, 08:46:56 am »

Quote from: Gessert Books on October 08, 2020, 08:39:41 am

That would be the best place to ask and I'll watch there too. My best guess is that some Kindle and Look Inside friendly CSS/ media queries will be absent, and the store link thing is because most storefronts require you to link back only to themselves. I believe capital G Generic keeps it flexible by prompting you to link to your website instead.

Thank you again!

AaronShep · « **Reply #27 on:** October 08, 2020, 09:19:25 am »

Quote from: Triceratops on October 08, 2020, 05:14:52 am

I don't think most people knew or cared about Amazon's preference before, because it didn't seem to really matter. But now things seem to be changing. A mobi file triggers a big warning pop-up in Kindle Previewer. That's new.

More to the point, if Vellum is right, and a generic epub file is a no-no, that's also news.

https://blog.vellum.pub/2020/09/amazon-would-prefer-an-epub-file/

So Vellum seems to be saying that a generic epub file generated by Scrivener, Calibre, Sigil, etc, will be wrong. Vellum seems to be saying that a Kindle.epub file generated by Vellum is now the only way to go, for Amazon.

https://help.vellum.pub/generating/kindle-ebook-format/

I guess the question is, why?

Maybe most people haven't cared, but KDP has been translating their MOBI files to EPUB as an intermediate step for quite some time. So, it has long been optimal to supply EPUB directly, even if not required. In fact, that has to be how Vellum handles it internally -- creating the EPUB then using Amazon's kindlegen to translate to MOBI if you ask for it, just as Kindle Previewer would do. Then Amazon would convert back to EPUB for further changes!

And it's nothing new that each major platform -- KDP, Apple, Kobo, B&N -- can benefit from tweaks to layout and coding. Vellum is just offering to do that for KDP, while also offering generic EPUB that will work well enough anywhere. I've been doing that kind of customization WITHOUT Vellum, just by testing my ebooks on different platforms and adjusting my HTML before converting to EPUB in calibre. It's great that Vellum saves you the trouble, and it's not easy to do yourself, but there's nothing in it that's exclusive to Vellum.

This all started with Amazon's introduction of Kindle Format 9, which abandoned MOBI and moved to EPUB. I can't even remember how long ago that was.

Brad West · « **Reply #28 on:** October 08, 2020, 01:42:16 pm »

Quote from: Triceratops on October 08, 2020, 08:15:55 am

Thank you!

But, how is the upper-G Generic epub from Vellum different from the epub generated by the others? And how is the Vellum Kindle.epub version the same; or is it?

Hello from Vellum. We should start by stating that this post was originally on the Vellum Blog and intended for users of Vellum. If you're not using Vellum, you may be interested to know about this change regarding MOBI, but we don't at all mean to suggest that you should stop using Word files, etc.

After seeing these changes at KDP and in Kindle Previewer, we wanted to make sure our users knew how to change Vellum to output an EPUB file for Kindle instead of the MOBI file it generates by default. That option is in Preferences, as seen above, and switching to EPUB will save a conversion step in Vellum and avoid warnings in Kindle Previewer.

We also wanted to remind users to always upload Vellum's Kindle-specific output to Amazon, and not an output file intended for another store. Vellum offers a generation option called "Generic EPUB" that is intended for aggregators like Draft2Digital. Though that file can be used with several different stores, it can cause problems at Amazon, as it lacks all of the Kindle-specific changes necessary for dealing with Amazon features like Look Inside, Kindle Cloud reader, etc. Also, with Vellum's Store Link feature, links to Amazon will only be included in the Kindle edition.

Again, though, this advice is intended for Vellum users. If you're creating an EPUB file by some other means, or you're uploading a Word file, feel free to keep doing what you're doing.

Hope that clarifies things.

WRPursche · « **Reply #29 on:** October 08, 2020, 05:40:56 pm »

My kindlegen produced MOBI files look fine in the previewers (v3 and the older 2.94, which I find more accurate), on devices, and in the Look Inside. They also have Enhanced Typesetting enabled.

Triceratops · « **Reply #30 on:** October 09, 2020, 03:29:16 am »

Quote from: Brad West on October 08, 2020, 01:42:16 pm

Hello from Vellum. We should start by stating that this post was originally on the Vellum Blog and intended for users of Vellum. If you're not using Vellum, you may be interested to know about this change regarding MOBI, but we don't at all mean to suggest that you should stop using Word files, etc.

After seeing these changes at KDP and in Kindle Previewer, we wanted to make sure our users knew how to change Vellum to output an EPUB file for Kindle instead of the MOBI file it generates by default. That option is in Preferences, as seen above, and switching to EPUB will save a conversion step in Vellum and avoid warnings in Kindle Previewer.

We also wanted to remind users to always upload Vellum's Kindle-specific output to Amazon, and not an output file intended for another store. Vellum offers a generation option called "Generic EPUB" that is intended for aggregators like Draft2Digital. Though that file can be used with several different stores, it can cause problems at Amazon, as it lacks all of the Kindle-specific changes necessary for dealing with Amazon features like Look Inside, Kindle Cloud reader, etc. Also, with Vellum's Store Link feature, links to Amazon will only be included in the Kindle edition.

Again, though, this advice is intended for Vellum users. If you're creating an EPUB file by some other means, or you're uploading a Word file, feel free to keep doing what you're doing.

Hope that clarifies things.

Hi Brad, thanks for your prompt and courteous explanation.

I hear what you're saying that the advisory on Vellum's site was intended for Vellum users. But since Vellum has a dedicated thread on Writer's Cafe, and indie authors after all comprise both the customers and potential customers of Vellum, it seems legit to ask for clarification of the epub features here.

I also understand that uploading a Word file is fine. My question concerns epub files only.

Respectfully, I'm a little confused. This concerns typesetting, as opposed to links. Vellum's blog advisory states that there are clear differences between how Vellum generates its Kindle epub and its Generic epub. These differences result in variations with how epub files appear in Amazon's Look Inside and Kindle Cloud Reader. So, Vellum's Kindle epub contains a special code or codes that set its typesetting apart from Vellum's Generic epub. It sounds like you're confirming this in your kind response above.

On the other hand, it sounds like you're also saying that uploading an epub generated from a common non-Vellum program like Scrivener, Calibre, Sigil, etc is a-ok.

Do you see how that's a bit puzzling?

My questions are, what exactly are Vellum's Kindle-specific changes in the Kindle epub, and how great of a difference does it make with how files appear in Look Inside and Kindle Cloud Reader? Does the difference depend upon if the user has unique elements like tables or drop caps? Or do the differences manifest across the board?

Not trying to dig into Vellum's proprietary secrets, and feel free to tell me to buzz off. I'm just wondering if for Amazon, Vellum has, or might have, a secret sauce that makes its epubs look better in Look Inside and Kindle Cloud Reader, for a non-techie operator like me anyway.

unkownwriter · « **Reply #31 on:** October 11, 2020, 03:50:48 am »

Quote

So this new wording helps discourage use of non-standard publishing tools like that.

Amazon has been encouraging people to use their own tools, like Kindle Create for a while. This thing about preferring epub is probably due to that format working better with KC than Word or any other way of getting a file into the program. I wonder if they have a new thing coming for creating files?

Anyway, I've not seen Amazon "pushing" epub before, not until threads like this one started. I've not gotten an email nor seen any notices on the KDP forum about it, either. It might be in the trial stage, prior to any news being officially announced, as Amazon is prone to do.

I don't know if I'll begin using epub, or continue to upload mobi files from Scrivener. I guess I'll just have to see how things go.

Gessert Books · « **Reply #32 on:** October 11, 2020, 07:38:02 am »

Quote from: unkownwriter on October 11, 2020, 03:50:48 am

Amazon has been encouraging people to use their own tools, like Kindle Create for a while. This thing about preferring epub is probably due to that format working better with KC than Word or any other way of getting a file into the program. I wonder if they have a new thing coming for creating files?

Anyway, I've not seen Amazon "pushing" epub before, not until threads like this one started. I've not gotten an email nor seen any notices on the KDP forum about it, either. It might be in the trial stage, prior to any news being officially announced, as Amazon is prone to do.

I don't know if I'll begin using epub, or continue to upload mobi files from Scrivener. I guess I'll just have to see how things go.

If you are generating mobi files from scriv, you are basically already using epub. Scrivener generates mobi files from epub behind the scenes via kindlegen. So there is no real benefit to using mobi there.

Triceratops · « **Reply #33 on:** October 11, 2020, 09:22:30 am »

Quote from: Gessert Books on October 11, 2020, 07:38:02 am

If you are generating mobi files from scriv, you are basically already using epub. Scrivener generates mobi files from epub behind the scenes via kindlegen. So there is no real benefit to using mobi there.

Not trying to stir the pot (more), but viz Kindlegen or lack thereof, there's a caution on the Jutoh site re using Calibre to generate mobi files for Amazon?

And also, if Amazon's no longer supporting Kindlegen (which I presume since Zon is no longer offering Kindlegen downloads), but Scrivener uses Kindlegen, does anybody know if Scrivener has now pivoted to using Kindle Previewer 3 for generating its files for Amazon, like Jutoh does?

How do I install Kindlegen and Kindle Previewer?

As of August 2020, Amazon is no longer making a separate distribution of Kindlegen available for download. Instead, Jutoh can use the Kindlegen that comes with Kindle Previewer 3. Unfortunately, it also means that Linux users are not supported: but you can use Kindle-optimized Epub files instead, and they can be uploaded to KDP instead of .mobi files.

...

Why are .mobi files larger than Epub files?

Mobipocket files generated by Kindlegen (as opposed to Calibre) also incorporate the original source files, so that Amazon has the option to later recompile the ebook with newer software. However, the customer is likely to be sent a smaller file from the Kindle store.

Note also that Amazon recommends Kindlegen for the creation of Mobipocket (Kindle) files. Using an unapproved Kindle file compiler, such as Calibre, may produce poor results or cause ebooks to be rejected from the Kindle store. [my bolding]
http://www.jutoh.com/faq.html

* Edit: added Scrivener question.

Gessert Books · « **Reply #34 on:** October 11, 2020, 09:31:45 am »

Yes, calibre has basically always done nonstandard things for mobi afaik, which I don't say as a criticism of the software at all. It was not made with production and publishing in mind, but rather for personal library management, and I use it myself for that.

AaronShep · « **Reply #35 on:** October 11, 2020, 11:37:34 am »

Quote from: Triceratops on October 11, 2020, 09:22:30 am

Not trying to stir the pot (more), but viz Kindlegen or lack thereof, there's a caution on the Jutoh site re using Calibre to generate mobi files for Amazon?

And also, if Amazon's no longer supporting Kindlegen (which I presume since Zon is no longer offering Kindlegen downloads), but Scrivener uses Kindlegen, does anybody know if Scrivener has now pivoted to using Kindle Previewer 3 for generating its files for Amazon, like Jutoh does?

You wouldn't use calibre to generate MOBI for Amazon. You would use it to generate EPUB for Amazon. That's what I now do all the time, converting from clean HTML to EPUB 2 format. Just watch calibre's export options, and verify with an EPUB checker such as epubcheck.

Amazon is very much supporting kindlegen, they're just not distributing it SEPARATELY. Previewer itself uses kindlegen, that's why it's installed as part of Previewer. But there's no point converting to MOBI, because Amazon just reconverts after upload. The only reason I use Previewer is to test conversion of my EPUB file before uploading EPUB to Amazon.

Triceratops · « **Reply #36 on:** October 12, 2020, 08:46:42 am »

Looks like Zon will be further tightening upload requirements ("more checks") on October 27.

On the face, this is to support Kindle Enhanced Typesetting.

Coming October 2020: File Ingestion Requirement

As part of our ongoing efforts to improve the digital reading experience for our customers, we wanted to share with you that starting October 27, 2020 we will be updating eBook file conversion requirements for large tables and include more checks to ensure eBook manuscripts are formatted correctly. This will allow more books to support Enhanced Typesetting -- our advanced typographical and layout features that offer customers a better reading experience. Most books already publish with Enhanced Typesetting support and customers have come to expect this experience with every title.

- For titles already available on Kindle, no action is needed. Your eBooks will continue to be available to customers as they are today.

- For new or resubmitted titles, if you submit a file and it does not meet the new requirements, the actions to fix will now be available for you on your KDP Bookshelf after you upload your manuscript and cover. You may also use Kindle Previewer (KPR) version 3.39 or higher to review your files prior to publication. View the Conversion Log (found in the View Menu in KPR) to find steps to fix any errors related to enhanced typesetting.
https://www.kdpcommunity.com/s/article/Coming-October-2020-File-Ingestion-Requirement

Gessert Books · « **Reply #37 on:** October 12, 2020, 10:27:46 am »

This makes some sense in that if they want to push ET it seems normal that they'd prefer epub, so that they can run the conversion themselves. Of note too that large tables are known for breaking ET, which is likely why they're mentioned here.

Brad West · « **Reply #38 on:** October 12, 2020, 01:12:49 pm »

Quote from: Triceratops on October 09, 2020, 03:29:16 am

My questions are, what exactly are Vellum's Kindle-specific changes in the Kindle epub, and how great of a difference does it make with how files appear in Look Inside and Kindle Cloud Reader? Does the difference depend upon if the user has unique elements like tables or drop caps? Or do the differences manifest across the board?

Vellum's Kindle-specific output contains a number of workarounds for potential issues on the Kindle platform. One of these issues is that, as Amazon converts your file to the multiple formats used throughout its system, it will create a file in their older 'mobi7' format. This particular format is very old and extremely limited. It is primarily intended for older devices (i.e. the original Kindle), but it can still (sometimes) be used in Look Inside and in Kindle Cloud Reader.

There can be a number of issues with this translation to mobi7, especially for ebooks that use a fair amount of CSS for style and use modern CSS constructs like combinators. A selection of CSS that scales down the font size in a Copyright page, for example, may be incorrectly translated to scale the font size for the entire book.

To avoid these issues, Vellum wraps any CSS that may be mis-translated into a special media query that tells Amazon to ignore the style when converting to mobi7. These are non-standard, Amazon-specific media queries, however. They wouldn't make sense to see on any other platform, and wrapping style in this manner can cause issues on platforms that don't properly handle media queries (like Nook). For that reason, Vellum only uses these media queries in its Kindle-specific output, and not in output for other stores or in its "Generic EPUB" output intended for aggregators like Draft2Digital. And that's why you may have issues if you upload Vellum's Generic EPUB output to Amazon.

For Vellum users, the key bit is to always upload Vellum's Kindle-specific file to Amazon, and not its Generic EPUB output. That advice is not new, but given Amazon's new requests for EPUB files, we felt we needed to remind our users to make use of Vellum's Kindle Ebook Format controls rather than upload a file intended for another store.

If you're not using Vellum, then the advice of using Kindle-specific output vs Generic EPUB doesn't really apply. But if you're writing your own CSS, and encountering problems when your file is converted to mobi7, you may want to look into Amazon's proprietary media queries. More about those media queries can be found in their Kindle Publishing Guidelines. But nothing here is really affected by this change in preference for EPUB files over MOBI. As AaronShep mentions above, Amazon's been working from EPUB files for some time now.

Hope that helps.

Triceratops · « **Reply #39 on:** October 12, 2020, 01:42:29 pm »

Quote from: Brad West on October 12, 2020, 01:12:49 pm

Hope that helps.

Yes indeed. Thanks Brad!

Triceratops · « **Reply #40 on:** October 12, 2020, 02:10:01 pm »

Quote from: Gessert Books on October 12, 2020, 10:27:46 am

This makes some sense in that if they want to push ET it seems normal that they'd prefer epub, so that they can run the conversion themselves. Of note too that large tables are known for breaking ET, which is likely why they're mentioned here.

The change coming on October 27 sounds to me like Amazon is saying Starting Oct 27, if you try uploading a file that contains formatting that is disallowed in Enhanced Typesetting, such as any HTML/CSS crap, you can expect a big fat error message with a convenient auto-log entry that you can peruse to discover the uber-techy reason your file got rejected. Maybe Amazon might offer an option to upload a file without enabling Enhanced Typesetting; but then of course you risk your ebook looking like the second-class cousin with the bad haircut.

At this point I'm wondering, skeptically, why Amazon are pushing Enhanced Typesetting so hard. For uploading ebook files, Amazon has changed a bunch of stuff within the last 30 days. It appears all directed toward compliance with Enhanced Typesetting. ET is not so bad, it has better rendering and better typesetting, and it's reflowable.

That would be fine, except for two things. To my knowledge Enhanced Typesetting runs only on the new KFX format. KFX replaces the older AZW and AZW3 (KF8) file formats. The AZW and AZW3 (KF8) formats run on older Kindles. The KFX format runs on the new Kindles.

And KFX has DRM encryption. Which I believe is built-in, whether the publisher (us) wants the ebook DRM-free, or not? Please correct me if I'm wrong.

Amazon has not updated Kindlegen in at least seven years; it's been stalled on version 2.9 forever. Plus, Amazon no longer offers Kindlegen as a standalone download. Third-party ebook formatting programs like Jutoh and Vellum have to use the Kindlegen inside Kindle Previewer.

Conversely, Amazon's Kindle Create has been getting updates and Amazon recently has been herding self-publishers to use it:

With the latest release of Kindle Create, you can now upload your Kindle Create file to KDP as both an eBook and paperback of any trim size, creating both digital and print versions of your book simultaneously!
Routine but challenging paperback tasks like margins, page numbers, left/right side page layouts, widow/orphan treatment, and table of contents creation are also handled automatically.
Ready to publish your next book? Or ready to publish one of your eBooks in paperback? Download the latest version of Kindle Create today and get started.
https://the-digital-reader.com/2020/09/29/kindle-create-now-outputs-pod-book-files/

Call me a conspiracy theorist, but it seems possible that Amazon's using the better rendering etc of the Enhanced Typesetting features (which really are not that much better than AZW3, imo) as a sales-pitch pretext to funnel publishers into abandoning the old KF8 format for the new KFX format. With KFX Amazon has much more control. KFX is not as open a format as KF8. And KFX has DRM encryption.

Which I suppose would mean that formatting's going to get more complicated, for everybody.

AaronShep · « **Reply #41 on:** October 12, 2020, 03:55:26 pm »

Quote from: Triceratops on October 12, 2020, 02:10:01 pm

At this point I'm wondering, skeptically, why Amazon are pushing Enhanced Typesetting so hard.

I think the question should instead be, "Why has Amazon waited so many years before forcing authors to abandon an inferior and outdated format?" This was only a grace period, and I'm amazed it has gone on this long. If you were dealing with Apple, the forced switch would have happened long ago.

By the way, if kindlegen has not been updated, it's because it's only a conversion engine, and it doesn't need to change unless there's a change in Kindle format. The front end, Previewer, is frequently updated. And apps, I believe, are not using the kindlegen "in" Previewer. Kindlegen is installed at the same time but separately, and Previewer and all other apps use that.

And I don't think formatting has to get any more complicated. In fact, I purposely format my ebooks so simply that they'll look great on even the oldest devices -- the MOBI7 that Brad mentioned -- while still being eligible for Enhanced Typesetting. In fact, I'd say that accommodating old formats is what's complicated, not dealing with new ones.

Gessert Books · « **Reply #42 on:** October 12, 2020, 07:06:05 pm »

Quote from: Triceratops on October 12, 2020, 02:10:01 pm

Call me a conspiracy theorist, but it seems possible that Amazon's using the better rendering etc of the Enhanced Typesetting features (which really are not that much better than AZW3, imo) as a sales-pitch pretext to funnel publishers into abandoning the old KF8 format for the new KFX format. With KFX Amazon has much more control. KFX is not as open a format as KF8. And KFX has DRM encryption.

Which I suppose would mean that formatting's going to get more complicated, for everybody.

Amazon's never obsoleted a kindle device as far as I know, but they'd really have to if they wanted to force the latest format. And they may at some point, but there really are a ton of older devices out there. Who knows what they're thinking, but I'm guessing it's moreso that they want to make sure new titles at least support ET, partly since they brag about it so much, and partly because even basic stuff like hyphenation and justification options land under that umbrella.

FWIW Amazon has some of the most lenient specs I've seen and it's sort of nice to see some shift there, though I don't much like ET-compliance becoming sort of like a validation spec. Would have much rather they'd found a way to tie Enhanced Typesetting to a successful epubcheck pass or something.

Triceratops · « **Reply #43 on:** October 14, 2020, 08:34:18 am »

Quote from: Gessert Books on October 12, 2020, 07:06:05 pm

Amazon's never obsoleted a kindle device as far as I know, but they'd really have to if they wanted to force the latest format.

To my knowledge, older Kindles up to around 2012/2013 can process Extended Typesetting/KFX files, albeit the hardware screen resolutions may not do the higher-res ET justice. But new Kindles will not run the older AZW and AZW3 (KF8) file formats.

And that of course offers Zon the excuse to force the change, for uploading new ebooks. "Well the old AZW and AZW3 (KF8) file formats won't work on the new Kindles, so of course we have to mandate Extended Typesetting/KFX." So to me it seems there's file format flexibility going backward, just not forward.

Quote from: Gessert Books on October 12, 2020, 07:06:05 pm

FWIW Amazon has some of the most lenient specs I've seen and it's sort of nice to see some shift there, though I don't much like ET-compliance becoming sort of like a validation spec. Would have much rather they'd found a way to tie Enhanced Typesetting to a successful epubcheck pass or something.

Agreed. But it appears to me that Zon wants tighter control over its ebook files going forward. Unless I'm mistaken, the compliance hurdles will only get higher.

KF8 was basically Webkit, which itself was basically an open-source browser, AFAIK. OTOH, KFX is in-house proprietary. With DRM encryption.

Control, control, control...

Triceratops · « **Reply #44 on:** October 14, 2020, 08:36:41 am »

Pursuant to the October 27 deadline -- when publishers self- and otherwise will no longer be permitted to upload an ebook file without correcting Enhanced Typesetting "errors" -- those folks who want to know in advance just how their epub and mobi files will fare under the new regime, can try the following.

- Download Kindle Previewer, whose version today is 3.46. Note: this latest version runs only on Windows 8.1 and above (64-bit Intel/AMD), and Intel macOSX 10.13 (High Sierra) and above.
https://www.amazon.com/gp/feature.html/ref=amb_link_5?&docId=1000765261

- See if your file fails Enhanced Typesetting. First, import your eBook into Kindle Previewer. If your eBook supports Enhanced Typesetting, the Enhanced Typesetting label is displayed in the Preview and Navigation Options pane.
https://kdp.amazon.com/en_US/help/topic/G202087570

- If the file fails Enhanced Typesetting, check the conversion log. Amazon added KP's conversion log feature around March 2020.

The error message(s) you see in the conversion log may be identical to any error messages you might encounter on and after October 27.

Triceratops · « **Reply #45 on:** October 14, 2020, 07:22:59 pm »

Last night, new language was inserted into KDP's "Update Your Book Details" verbiage.

Details you can't edit after publishing

There are certain book details you won't be able to change after publishing. Which details you can change also depends on whether you published an eBook or a paperback. Regardless of format, if you significantly change your book, it's considered a new edition and should be published as a new book.

eBook

You won't be able to change:

Digital Rights Management (DRM)

Publication date: The Kindle Store automatically enters the date you first published your book through KDP

Title and/or Author name: If you make changes to your main title and/or author name after publication, your eBook will be considered as a new book, you will need to upload a new submission.

To improve the shopping and reading experience for customers, if you significantly change your book title or author name when submitting it as a new book, you're required to include the following disclaimer at the top of the description field: "Previously published as [book title] by [author name]." Significant changes to both book title and author name aren't allowed.

Note: Your publication date isn't the same as your release date. You can change your release date if you want to make new books available for pre-order in Kindle Stores worldwide.
[bolding mine]
https://kdp.amazon.com/en_US/help/topic/G200736410?fbclid=IwAR2SfAb0RZdBOcgyzbjsFekFHM9u0meIvGSP9uxJ_oxB0hg1JniipZHkYT0

The new don't-ask-to-change DRM is almost certainly cause and/or consequence of the new KFX ebook file format.

Weird is the don't-ask-to-change title and/or author name. That's new. Perhaps the KFX file format embeds them in the file metadata and Amazon can't or won't change it following upload? Anybody know?

AaronShep · « **Reply #46 on:** October 14, 2020, 08:15:44 pm »

Quote from: Triceratops on October 14, 2020, 07:22:59 pm

The new don't-ask-to-change DRM is almost certainly cause and/or consequence of the new KFX ebook file format.

Weird is the don't-ask-to-change title and/or author name. That's new. Perhaps the KFX file format embeds them in the file metadata and Amazon can't or won't change it following upload? Anybody know?

This is the oddest discussion. All these things being attributed to a format that is already several years old. The ONLY thing related to this format that has changed is that Amazon wants everyone to use it, because it's BETTER. Here is a list of the advantages:

https://kdp.amazon.com/en_US/help/topic/G202087570

You have NEVER been able to get rid of DRM once you've applied it. If you can't change DRM at all now, it just means you can't ADD it later.

Forbidding title and author is simply a way of avoiding confusion among customers. OF COURSE, they could allow changes if they wanted. They've been allowing them up till now in ALL formats.

Amazon is CONSTANTLY tightening its guidelines and requirements to try to improve things. There is no conspiracy, there is no new format, and everything is in plain siight.

Northern pen · « **Reply #47 on:** October 14, 2020, 09:18:02 pm »

Wait, does this mean people still waste time making mobi and epub files??? That is so 5 years ago.

Unless you're using Vellum or some fancy software that makes books so pretty you spontaneously have multiple orgasms from the experience of reading such a beautiful book, just load the word file.

Triceratops · « **Reply #48 on:** October 15, 2020, 06:13:35 am »

Quote from: AaronShep on October 14, 2020, 08:15:44 pm

This is the oddest discussion. All these things being attributed to a format that is already several years old. The ONLY thing related to this format that has changed is that Amazon wants everyone to use it, because it's BETTER. Here is a list of the advantages:

https://kdp.amazon.com/en_US/help/topic/G202087570

You have NEVER been able to get rid of DRM once you've applied it. If you can't change DRM at all now, it just means you can't ADD it later.

Forbidding title and author is simply a way of avoiding confusion among customers. OF COURSE, they could allow changes if they wanted. They've been allowing them up till now in ALL formats.

Amazon is CONSTANTLY tightening its guidelines and requirements to try to improve things. There is no conspiracy, there is no new format, and everything is in plain siight.

Actually, Amazon does have a new ebook file format, like I said: it's called KFX. No one said anything about a conspiracy. Why are you typing all caps so often? In net etiquette that comes off as shouting.

AaronShep · « **Reply #49 on:** October 15, 2020, 08:39:11 am »

Quote from: Triceratops on October 15, 2020, 06:13:35 am

Actually, Amazon does have a new ebook file format, like I said: it's called KFX. No one said anything about a conspiracy. Why are you typing all caps so often? In net etiquette that comes off as shouting.

I was analyzing and writing about this "new" KFX format and Enhanced Typesetting on my blog in December 2015. It's five years old. Over the next year, most Kindle books were converted to KFX and Enhanced Typesetting, and it's been that way ever since.

Frankly, given the advantages of Enhanced Typesetting, I'm shocked there are still KDP authors who are submitting incompatible files. I'm also shocked that Amazon has let them do it for this long.

KBoards.com

Triceratops · « **Reply #50 on:** October 15, 2020, 09:23:09 am »

Quote from: AaronShep on October 15, 2020, 08:39:11 am

I was analyzing and writing about this "new" KFX format and Enhanced Typesetting on my blog in December 2015. It's five years old. Over the next year, most Kindle books were converted to KFX and Enhanced Typesetting, and it's been that way ever since.

Frankly, given the advantages of Enhanced Typesetting, I'm shocked there are still KDP authors who are submitting incompatible files. I'm also shocked that Amazon has let them do it for this long.

I'm sure you're very knowledgeable, but KFX is newer than the previous AZW and AZW3 (KF8) file formats. Correct? You had said that there was no new format.

We've been over this. Previously, nobody outside of techie world cared about KFX ebook format, because Amazon did not force compliance with the format. It was not an upload requirement. Starting Oct 27, it will be; KFX will be Amazon's ebook validation standard. Thus, HTML and CSS coding in epub files will register as "errors" in the intake, and Amazon won't accept the ebook file unless Amazon also offers (maybe) a workaround. Will they? We shall see. To me KFX validation seems like a problem because, just for openers, Vellum's Kindle epub uses HTML and CSS coding, as mentioned upthread.

Not sure here what your ongoing points are, other than your opinion that my interest in and concern for Amazon's new upload changes is overblown. If that's your opinion, fine. Me, I am indeed concerned, for the reasons that I've already said. If you'd like to offer counterarguments, feel free to include some evidence or citations. It helps the discussion.

Shane Lochlann Black · « **Reply #51 on:** October 15, 2020, 10:34:17 am »

Quote

Thus, HTML and CSS coding in epub files will register as "errors" in the intake, and Amazon won't accept the ebook file unless Amazon also offers (maybe) a workaround.

You can't make an ePUB without HTML and CSS. They are part of the standard along with XML. If they register as errors, then you can't upload an ePUB at all.

Triceratops · « **Reply #52 on:** October 15, 2020, 11:38:32 am »

Quote from: Shane Lochlann Black on October 15, 2020, 10:34:17 am

You can't make an ePUB without HTML and CSS. They are part of the standard along with XML. If they register as errors, then you can't upload an ePUB at all.

You're right. I wasn't clear. Sorry.

What I meant to say was, in Amazon's conversion process when the epub file is converted into a KFX file, Amazon takes the HTML and CSS formatting instructions for the ebook that are inside the epub file and in effect translates them into KFX formatting language. That's my understanding, anyway. So formatting structures that are okay in KF8 files probably won't be accepted into KFX, because KFX's stricter Enhanced ~~Formatting~~ Typesetting gets tricky.

Again, that's my understanding. I hope I'm wrong.

*Edit: typo.

AaronShep · « **Reply #53 on:** October 15, 2020, 11:43:55 am »

Quote from: Triceratops on October 15, 2020, 09:23:09 am

I'm sure you're very knowledgeable, but KFX is newer than the previous AZW and AZW3 (KF8) file formats. Correct? You had said that there was no new format.

We've been over this. Previously, nobody outside of techie world cared about KFX ebook format, because Amazon did not force compliance with the format. It was not an upload requirement. Starting Oct 27, it will be; KFX will be Amazon's ebook validation standard. Thus, HTML and CSS coding in epub files will register as "errors" in the intake, and Amazon won't accept the ebook file unless Amazon also offers (maybe) a workaround. Will they? We shall see. To me KFX validation seems like a problem because, just for openers, Vellum's Kindle epub uses HTML and CSS coding, as mentioned upthread.

Not sure here what your ongoing points are, other than your opinion that my interest in and concern for Amazon's new upload changes is overblown. If that's your opinion, fine. Me, I am indeed concerned, for the reasons that I've already said. If you'd like to offer counterarguments, feel free to include some evidence or citations. It helps the discussion.

You might start by just looking at some Kindle book pages. I think you'll find very few that do not already have Enhanced Typesetting, meaning they are KFX. Certainly most or all EPUB books will automatically work. And certainly anything from Vellum will work. Amazon is just trying to round up the very few stragglers.

The reason it has not been an issue for non-techies is because it has been taken care of for most authors without their thinking about it -- as, for instance, in Vellum. As Shane said, EPUB is not much more than HTML and CSS. Using those is in itself no problem. The people at Vellum are very, very smart, and I assure you, they took care of any compatibility problems long ago.

Triceratops · « **Reply #54 on:** October 15, 2020, 11:57:44 am »

Quote from: AaronShep on October 15, 2020, 11:43:55 am

The reason it has not been an issue for non-techies is because it has been taken care of for most authors without their thinking about it -- as, for instance, in Vellum. As Shane said, EPUB is not much more than HTML and CSS. Using those is in itself no problem. The people at Vellum are very, very smart, and I assure you, they took care of any compatibility problems long ago.

What? We're not having a referendum on competence. Of course Vellum is great. That's not the issue. The issue is Amazon's unknowns. Right now Amazon has enacted a lot of changes in the past 30 days.

Look, if you really want to offer some empirical evidence that everything is cool, why don't you run ten or so of your ebook files through the latest version of Kindle Previewer, like I laid out upthread, and report back if Enhanced Typesetting fails, or not. And if any files fail, then what were the error messages in the KP conversion log?

AaronShep · « **Reply #55 on:** October 15, 2020, 02:35:31 pm »

Quote from: Triceratops on October 15, 2020, 11:57:44 am

What? We're not having a referendum on competence. Of course Vellum is great. That's not the issue. The issue is Amazon's unknowns. Right now Amazon has enacted a lot of changes in the past 30 days.

Look, if you really want to offer some empirical evidence that everything is cool, why don't you run ten or so of your ebook files through the latest version of Kindle Previewer, like I laid out upthread, and report back if Enhanced Typesetting fails, or not. And if any files fail, then what were the error messages in the KP conversion log?

It might help allay your fears if you download the Kindle Publishing Guidelines and study them. Your concerns seem to be entirely based on misunderstanding and speculation, and that might clear things up, or at least give you direction for further research.

Triceratops · « **Reply #56 on:** October 15, 2020, 06:02:05 pm »

Quote from: AaronShep on October 15, 2020, 02:35:31 pm

It might help allay your fears if you download the Kindle Publishing Guidelines and study them. Your concerns seem to be entirely based on misunderstanding and speculation, and that might clear things up, or at least give you direction for further research.

From your response, I presume that your copy of Kindle Previewer diagnosed not one Enhanced Typesetting fail on any one of your ebook files? Files that, since you represent yourself as an ebook coding expert, you no doubt created yourself?

Congratulations.

Now if you'll excuse me, I'll be getting back to the thread.

Becca Mills · « **Reply #57 on:** October 17, 2020, 10:34:57 am »

KBoards.com