While Amazon’s Digital Text Platform (DTP), which is Amazon’s interface for self-publishers and small presses to get their books into the Kindle Store, has been gradually improving, one thing that remains a major pain in the you-know-where is uploading documents created on a Mac.
As with many systems, Amazon’s DTP is designed for input from Microsoft Windows applications, and doesn’t like the way Mac apps typically encode text characters: DTP won’t accept documents encoded with Unicode, although it does now seem to take (or at least produce) documents with UTF-8. Without getting into a lot of technical mumbo-jumbo, those encodings map out character sets beyond the Windows-standard Latin-1 (Western) encoding and English/western European character sets (Unicode provides support for a wide range of international characters).
Where Mac users run into problems is that 1) DTP won’t accept the more typical Mac documents natively produced by Pages or TextEdit, and 2) if you’re preparing the print version of your document in Pages, you can’t output directly to HTML (which is a really silly oversight, methinks).
There are other programs, particularly InDesign, that many Mac users use to format their print versions; I can’t help you with those, because I only have Pages and TextEdit, but hopefully what I go over here will help.
So, let’s say that you have your book set up in Pages and it’s ready to go. Here’s what I did that seemed to work:
Step 1: Save it as an RTF file.
Step 2: Open the RTF file in TextEdit.
Step 3: In TextEdit do Save As -> HTML
You can then edit the HTML file as (or if) necessary in an editor like Taco. Once that’s done, take the HTML file and any image files it needs, zip them together – you must use a program that has a “Windows-friendly” zip option (like YemuZip) or DTP won’t accept it! – and then upload it to DTP.
I wish I could say that I could guarantee you that this will work for your document, but with the vagaries of DTP, I can’t. I know this worked for my novel In Her Name: Empire, and as long as you use an English or western European character set you should – I hope – be fine.
However, if you’re using another character set – let’s just take Chinese as one of many examples – it will not work. The Kindle is still very limited in what it can do compared to web applications. It looks like DTP has moved up from accepting only Latin-1 (Western) encoded documents to at least accepting UTF-8 encodings, but you may still run into trouble: if you try to upload your HTML and DTP comes back with a long unintelligible error that has “unicode” buried in it, chances are this is the problem.
Unfortunately, I don’t have any immediate solutions to that: my first recommendation would be for you to go back and make sure your HTML is Latin-1 (Windows) or UTF-8, not Unicode (these are all separate options for encoding, depending on your app).
Related Posts
- Amazon’s Digital Text Platform: Where’s Customer Support? Let me be up front about something: I like Amazon. I’ve been an Amazon customer for years, and have done my share to help boost their profits. But Amazon’s Digital Text Platform (or DTP), which is the mechanism for independent...
- Holdouts for Kindle and Print Book Discounts on Amazon: Mobipocket and Lightning Source We don’t know why Amazon has stopped discounting books published by independent authors and publishers, but it has. If you look in the Kindle Store or the greater Amazon bookstore, you’ll see that those nice red discount prices have disappeared...
- KindleFormatting.com – Good Info for Publishing on Amazon Kindle I just wanted to point out a good source of information on formatting your document for the Amazon Kindle: kindleformatting.com by Joshua Tallent. There is of course a lot of information and current discussion on the Amazon DTP forums, but...
- Mobipocket No Longer Accepting New Publishers If you’ve visited the Mobipocket site recently with the intention of setting up a new publisher account, you no doubt encountered this message on the publisher welcome page: Effective September 2009, we will no longer open new accounts for publishers...





















#1 by Michael H. on July 9th, 2009 - 8:17 pm
Hi Michael,
I’m ready to publish my ebook trilogy on Mobi and Amazon. With your book’s help I’ve gotten the files to format the way I want by using Creator and loading up to my Kindle.
Before I upload to DTP I was hoping to find out how to handle the Mobi files. There is the .prc file but what about the .opf and the subfolder of linked images? My book is 200,000 words with dozens of hyperlinks and about 30 images. (Should I use compression?)
To view on the Kindle I copy the whole Mobipocket folder over to my documents folder and it works fine. (BTW, I use bookmarks for internal links and for the TOC and it works fine with the toc guide in Creator.)
So, for DTP upload do I have to zip the .prc with the image folder? What about with Mobi deploy – does it grab the subfolder of images?
Thanks-
MH
#2 by Michael R. Hicks on July 9th, 2009 - 8:52 pm
Just upload the .PRC file – that’s all you’ve gotta do! Don’t worry about the other files: those are just part of the creation process. The final product – the .PRC file – is fully self-contained. You don’t even have to zip it for DTP – just upload the file, then check it out in the viewer. Note: the viewer is much better than it used to be, but is still only an approximation.
Happy publishing!
Mike
#3 by Michael H. on July 9th, 2009 - 9:01 pm
Muchas gracias!
MH