Bookshelf | Reports | Community | KDP Select

Home » Amazon KDP Support » Ask the Community » Formatting

Thread: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!


This question is answered.

Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 23 - Pages: 2 [ 1 2 | Next ] - Last Post: Dec 31, 2012 5:52 PM Last Post By: sbin59
jtbigtoad

Posts: 9,227
Registered: 08/01/10
WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 23, 2012 5:41 PM
 
Click to report abuse...   Click to reply to this thread Reply
WORD VERSUS. THE KDP BOOKSHELF CONVERSION
I'm putting this in the formatting forum, because that is really where it goes. A lot of times, I put these in the general questions forum so more people will see them. I have already responded to several threads that are basically having the same problem and I ran an experiment to see what was going on. Apparently the way Word.doc files are being treated has changed. (Also, did you know that there is a spellcheck?)

Lately, there have been a lot of complaints about problems uploading Word files to the KDP bookshelf this all started around the first part of December.

Suddenly, old files that work perfectly well last year or now falling apart when they are re-uploaded (with minor corrections) and republished.

Apparently, the KDP bookshelf has changed the conversion without telling anyone. This is unfortunate because it is caused quite a bit of distress for very many KDP bookshelf users.

I have found that the old Word standbys will still work.

I use styles in one style I have is for first-line indent of 0.38 inches.

I have another style that is used for non-indentation. It has a paragraph indent of 0.01 inches – that's 1/100th of an inch! Whenever you declare indentation the KDP bookshelf will not automatically indent and the 0.01 inch is too small of an indentation to take effect the result is non-indentation.
The other key factor in all of this is to use the "Webpage, Filtered" method of generating an HTML file.

If you are comfortable working in HTML you will certainly know that Word's HTML – even the filtered variety is terrible – but, it works!

Here is the recipe for webpage filtered (if your brand of Word does not have Webpage, Filtered, just use Webpage instead.) In order to do this, you employ the Save As method of saving.

From Word.doc => Word.htm (Webpage, Filtered)

1) Open the Word.doc and do a Save As Webpage, Filtered, But direct the Save into a separate, empty File Folder.

NOTE: This folder should be created ahead of time, placed in a convenient place, and given a distinct name that is easy to find.

2) Word will issue a dire warning just ignore it and click the YES button!

3) After the save as, your open Word.doc will become Word.htm

4) Close it

5) Find the empty file folder (now, if you look inside the file folder, it will have the Word.htm and a file of your images in it) send the entire file folder (Word.htm and Image folder) to a zipped file by right clicking it and selecting Send to ... Compressed (Zipped) File.

NOTE: This Zipped filefolder is what you upload to the KDP Bookshelf

The zipping ties the images to the Word.htm; otherwise, the Conversion engine will ignore them.

NOTE: If you do not have ==> ANY <== IMAGES AT ALL, You do not have to zip the Word.htm file

Here is a page on Mac stuff

https://kdp.amazon.com/self-publishing/help?topicId=200735140

they mentioned Webpage filtered, but I don't think Mac Word has this

but other than this here is the Mac zip formula

Save as Webpage on mac (I still like creating the seperate folder ahead of time!

the KDP HELP lsits this as how to "ZIP file on mac

Now, to create the ZIP folder necessary for uploading to KDP:

1. Click on your HTML file to select it and while holding Shift also Click on the Folder with your images. Both files will now be selected.
2. Now let go of shift and while holding down the Control (CTRL) key, click on the HTML file 3. This will bring up a menu with options, with the word "Open" at the top. From the list, choose "Compress 2 Items"
3. This will create a ZIP file on your desktop that is automatically called "Archive.zip"

If you wish to send the book to either of the @...Kindle.com addresses you need to take the zipped file folder and stick it inside of ANOTHER empty file folder and ZIP IT A SECOND TIME!

This creates a DOUBLE ZIPPED or ZIP/ZIP folder that you attach to the email to the conversion service.

(Its a KINDLE thing :) )

JT

;)

mrlasers

Posts: 1,633
Registered: 07/06/11
Re: WORD VERSUS. THE KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 23, 2012 7:07 PM   in response to: jtbigtoad in response to: jtbigtoad
Helpful
Click to report abuse...   Click to reply to this thread Reply
It seems like a fairly major revision was made to the KDP conversion process recently. The results of a few brief tests leave a lot to be desired. They're now making some fairly serious assumptions about the content that's coming into their system, which are a bit dangerous (to say the least) but will (in at least some areas) result in a better final product for many publishers. In some cases they've also introduced some pretty fundamental errors into the process that will result in hugely defective content.

The biggest assumption they seem to be making now is that the "Normal" style in a Word document (DOCX, I didn't test older formats) contains the standard text size and are replacing absolute point values with relative values in rem units, along with removing any reference to font family. It is somewhat dangerous to make an assumption like this about what a publisher intended, but given the severe defects involved when not making this assumption it's probably for the better. At the very least you shouldn't encounter the illegibly small text on eInk Kindles or "forced" font type, though you also can't specify any font face for any purpose when uploading in this format. I suppose it is a fair enough trade off since trying to control this in Word just resulted in defects before anyway.

A much bigger concern is that HTML formatted content is not being processed in the proper text format. This is going to result in many characters (most notably in my tests "curly" or "smart" quotes) being transformed into garbage characters. I don't know how they managed to go live with this defect, but it's an extremely huge mistake.

I'm sure there are lots of other issues (along with at least some improvements) to this new process that didn't appear in my tests, but the issues I did see are rather troubling. If you're uploading non-mobi content (including ePub or HTML) I would advise extreme care in proofing the converted book file before publication. Obviously this is a recommendation I would have made before this update anyway, but at least the shortcomings of the earlier conversion process were well understood.

You might also want to check previously uploaded content, even if you haven't made any changes to it, since Amazon's systems will from time to time reconvert content without any prompting on the part of the publisher.

--
MrLasers
eBook Formatting & Production
http://www.mrlasers.com
jtbigtoad

Posts: 9,227
Registered: 08/01/10
Re: WORD VERSUS. THE KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 24, 2012 3:09 AM   in response to: mrlasers in response to: mrlasers
 
Click to report abuse...   Click to reply to this thread Reply
It occurs to me that the individuals responsible for development over at Amazon have NEVER embraced the concept of BETA Testing!

I feel like I have worked pretty hard to develop an easy to use method of producing a good basic e-Book (Not so many bells and whistles, but at least a couple of cuts above the standard print books.

It disturbs me that the base-level author/publisher seems to be being pushed out of the process.

I guess it is a prime example of how much Amazon values we Peed' ons!

JT

;)
ticketyboofarm

Posts: 9
Registered: 09/24/11
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 24, 2012 9:42 AM   in response to: jtbigtoad in response to: jtbigtoad
Helpful
Click to report abuse...   Click to reply to this thread Reply
Thanks very much for posting this. I uploaded my book files twice and still my publisher logo wasn't showing up. Using your instructions, it's now ready to go. Thanks & Merry Christmas!
divorcedoctor

Posts: 5,539
Registered: 07/11/10
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 25, 2012 4:03 PM   in response to: jtbigtoad in response to: jtbigtoad
 
Click to report abuse...   Click to reply to this thread Reply
Suddenly, old files that work perfectly well last year or now falling apart when they are re-uploaded (with minor corrections) and republished.

Apparently, the KDP bookshelf has changed the conversion without telling anyone. This is unfortunate because it is caused quite a bit of distress for very many KDP bookshelf users.

bigtoad, it started in June 2012, at same time as our preferred zip-zip method stopped sending us exact proof files - it is all to do K7 coming under the influence of K8 as Mars lined up with CNN but I leave all the techno-babble to the Y2KProfessionals and simply tell it as it is.

Whenever you declare indentation the KDP bookshelf will not ***automatically*** indent and the...

and THAT was the first thing to go - NO MORE AUTO THINGOS

SO I updated all that in my book in Aug 2012, but seems most folk want to reinvent the wheel and discover themselves.

here is the book/blog

E-Book Format for Indie Authors - 2013 Ready US
E-Book Format for Indie Authors - 2013 Ready UK

Book Flippage
Book Blog
katieelle

Posts: 20
Registered: 02/16/12
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 26, 2012 5:18 AM   in response to: jtbigtoad in response to: jtbigtoad
 
Click to report abuse...   Click to reply to this thread Reply
If you upload html as above, your book will have problems with the PaperWhite and other KF8 eink models

The problem is that the new formats allow you define a font-face/font-family, which sounds good in theory, but in practice is a disaster. If you define a font that the device doesn't support, it will lock the font into Helvetica and not allow the user to change it.

Word also exports html with font sizes in PTs, which also causes problems with the PW and other KF8 models. You need to define the font in percent or EMs or REMs. Usually it comes out far too small but I've seen a couple that come out far too large.
cjeasyaspie

Posts: 2,358
Registered: 05/28/09
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 26, 2012 7:14 AM   in response to: jtbigtoad in response to: jtbigtoad
 
Click to report abuse...   Click to reply to this thread Reply
The ebook at the link below, Sherlock Holmes' A Scandal in Bohemia, which I converted to Kindle format using MS Word, and uploaded directly to KDP, disproves all these theories about what MS Word can or can’t do.

It’s a beautiful book, complete with the original color illustrations, and it displays perfectly on the K2 (the format Amazon now calls Mobi 7), the K3 (now called the Kindle Keyboard, which now displays Format 8), and the Fire (Format 8).

The change of font size works perfectly in the K2 and the K3, and, in addition, the change of typeface, regular, condensed, and san serif, works perfectly in the K3 (this feature was not yet available on the K2).

The more advanced features of the Kindle Fire... Font Style, Typeface, Line Spacing, Margins, and Color Mode, all work perfectly on the Kindle Fire.

It isn’t necessary to buy the book… just download the Sample to see all the above in action.

http://www.amazon.com/Scandal-Bohemia-Illustrated-Annotated-ebook/dp/B004QWZ91S/
divorcedoctor

Posts: 5,539
Registered: 07/11/10
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 26, 2012 3:43 PM   in response to: cjeasyaspie in response to: cjeasyaspie
 
Click to report abuse...   Click to reply to this thread Reply
The ebook at the link below, Sherlock Holmes' A Scandal in Bohemia, which I converted to Kindle format using MS Word, and uploaded directly to KDP, disproves all these theories about what MS Word can or can’t do.

and it gets better

if you uploaded it again (or simply tried as a draft), as of 2 weeks back Amazon fixed the "nesting problem" with chapters, ie goto Sherlock Holmes in your book from TOC and no bolding and no image unless you then go back a page.

up to 2 weeks ago you had to fix that in the html but now it just happens.

see my blog for details -

http://kindleforindies.blogspot.com.au/2012/12/amazon-listens-to-its-customers.html

but beware because the rules also changed in June 2012 (yours is 2011) re indent and para spacing so it will depend on how you did that 18 months ago

booknookbiz

Posts: 2,041
Registered: 03/04/10
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 26, 2012 11:56 PM   in response to: cjeasyaspie in response to: cjeasyaspie
 
Click to report abuse...   Click to reply to this thread Reply
CJ:

Not to be argumentative, but I wouldn't bet money that a) the images look right on the Fire HD, due to resolution size aspects (no pun intended with "aspect"), and b) that the Paperwhite has resolved all the text-size issues.

The problem with the font SIZE has never been with the Fire, or even with the K3, according to our testing here; it's been the Paperwhite. I thought that an update had been implemented for that hardware?

Lastly, I can state that unless something has changed in the last 3 days, when you use fallback styling, while the Paperwhite and the K3 are allegedly K8, they don't display K8 fallback. They don't display K7 fallback. In fact, they obey neither set of instructions. (Specifically, in our testing thus far, vis-a-vis image sizing, at the very least). As you don't use HTML, Ceej, you probably have not noticed this, but for anything but the most fundamental book, this will be an issue.

To the poster who said something about designating fonts that might not be supported by the device, and the resulting Helvetica--you can't embed fonts with Word. You can only embed fonts using HTML.

Hitch
We produce ebooks
Listed as an Amazon Professional Conversion Service: http://bit.ly/uFwMwb
An INScribe Preferred Conversion Partner
http://www.booknook.biz/
Follow me on Twitter: @BookNookBiz
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur."
  • Red Adair
divorcedoctor

Posts: 5,539
Registered: 07/11/10
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 27, 2012 12:59 AM   in response to: divorcedoctor in response to: divorcedoctor
 
Click to report abuse...   Click to reply to this thread Reply
if you uploaded it again (or simply tried as a draft), as of 2 weeks back Amazon fixed the "nesting problem" with chapters, ie goto Sherlock Holmes in your book from TOC and no bolding and no image unless you then go back a page.

up to 2 weeks ago you had to fix that in the html but now it just happens.

Pie Lady, I said that above referring to the Word/save as filtered html/zip upload method, not noticing that you said this book was uploaded directly as Word.

SO I went back and checked a recent book but this time did same as you and uploaded the nude Word file.

BINGO it all worked exactly the same INCLUDING the fix for the "nesting issue"

what this means is UNLESS there are images then no need to even save as html any more to "tidy it up a bit" as Amazon now does the tidy up.
cjeasyaspie

Posts: 2,358
Registered: 05/28/09
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 27, 2012 8:05 AM   in response to: booknookbiz in response to: booknookbiz
 
Click to report abuse...   Click to reply to this thread Reply
Hitch,

Yes... in regard to your comment about "the most fundamental book"... my expression is "plain vanilla"... that is what Word does very well. Anything more almost certainly requires the attention of a professional conversion service.

And, yes, in regard to the comment about designating fonts... it was the many incorrect comments about fonts and Word that prompted me to post this link.

About how "A Scandal in Bohemia" displays on the Fire: The text displays beautifully on my original Fire and the Fire HD 8.9", while the illustrations are small, but acceptable.

At the time this book was created, the Fire and other Format 8 devices had not been released, so there was no need... at least as far as I was aware... to format for them, but subsequent tests suggest that if I had inserted larger illustrations, they would have displayed larger on the Fire.

Remember the tests I did a while back... and you tested for me on your iPad? They were "large" photos inserted with Word... and, somehow, the Word software and/or the Kindle software, handled the re-sizing such that they displayed very nicely on everything from my Android cell phone to the Fire to the Fire HD 8.9", to your iPad.

I'd like to do additional tests... using your specs and your illustrations... to be tested on all our devices... if you (or someone you assign) can test on all your devices... can we do that?
cjeasyaspie

Posts: 2,358
Registered: 05/28/09
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 27, 2012 8:09 AM   in response to: divorcedoctor in response to: divorcedoctor
 
Click to report abuse...   Click to reply to this thread Reply
Thanks, DD!

Yes... it proves once again, what I've always said... "a perfectly-formatted (including indents and spacing) MS Word file results in a perfectly-formatted Kindle file".

I'm really glad you figured out that fix for the nesting issue... I had not noticed that... thanks for sharing!

But... in regard to "there is no longer any need save as HTML"... I think there is, but for a different reason from what you just stated about the "tidy up" (which is really good to hear!).

I used to think the same thing... that there is no need to go through the HTML step... but then I had a manuscript that was just full of all kinds of special symbols... then I found that some of those symbols will display in the Kindle file only if I went through the HTML step.

In addition to that... MS Word makes a perfectly beautiful "dropped cap"... but it will display in the Kindle ebook only if the file is put through the "save as web page filtered" step.
punchygonzales

Posts: 2,853
Registered: 11/26/11
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 27, 2012 8:16 AM   in response to: booknookbiz in response to: booknookbiz
 
Click to report abuse...   Click to reply to this thread Reply
"To the poster who said something about designating fonts that might not be supported by the device, and the resulting Helvetica--you can't embed fonts with Word. You can only embed fonts using HTML."

I don't think they meant embed by saying designate though.
booknookbiz

Posts: 2,041
Registered: 03/04/10
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 27, 2012 2:24 PM   in response to: punchygonzales in response to: punchygonzales
 
Click to report abuse...   Click to reply to this thread Reply
Punch:

No, but I think that that is what she wrongly meant. In other words, the poster believed that by choosing, say, "Trebuchet" in Word, that that would make Trebuchet work in the final file. That's not, of course, what happens. That was the point I was trying to make. Choosing a font in Word, that happens to be supported on the device, doesn't make that font the "publisher font" on a Kindle (of whatever type).

I think that is what she meant. I could be wrong.

@CJ:

The problem is, while on your book, the image sizes aren't crucial, in some titles--actually, many titles--the image size most certainly matters, which is a problem we're struggling with right now. In many self-help books, for example, the images are floating inside paragraphs, or, worse, have explanatory text. OR, my real headache right now--tables that are images, not tables. And it's a nightmare in PPwhite and K3.

And for DD: yeah, this is an issue for plain old "Word-->KDP" uploads, as well. The vastly different screen resolutions are a huge problem. If you use fallback coding, you can fix it for the Fire devices, and for the old e-inks (you have to put the image in twice, mind you)...but you can't fix it for the PPW or K3. They persist in enlarging the image to fill the screen. If you set the height and width, then they are unreadably small on the FireHD 8.9".

Hitch
We produce ebooks
Listed as an Amazon Professional Conversion Service: http://bit.ly/uFwMwb
An INScribe Preferred Conversion Partner
http://www.booknook.biz/
Follow me on Twitter: @BookNookBiz
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur."

  • Red Adair
punchygonzales

Posts: 2,853
Registered: 11/26/11
Re: WORD VERSUS. THE NEW (12/15) KDP BOOKSHELF CONVERSION ANSWERS HERE!
Posted: Dec 27, 2012 3:56 PM   in response to: booknookbiz in response to: booknookbiz
 
Click to report abuse...   Click to reply to this thread Reply
"the poster believed that by choosing, say, "Trebuchet" in Word, that that would make Trebuchet work in the final file. That's not, of course, what happens.

Well, actually, it kind of is. She didn't mention anything about outputting a Word file. Assuming that she meant outputting from Word as HTML (as I believe most people do), then she is correct.
Legend
Helpful Answer
Correct Answer

Point your RSS reader here for a feed of the latest messages in all forums