![]() The format is better, and you avoid all the trouble of creating e-books. If you are not using a Kindle device, but a Kindle app on Kindle Fire, Amazon Fire, Android, iOS, etc, use a Universalis app directly on your device instead of creating e-books to read on it.This will work only with an actual Kindle device. Follow the links you will find in this page. Create an e-book using your own computer, plug your Kindle into your computer and transfer the file to it. You can avoid the Personal Documents service altogether.If you have sent your e-book by email to your address, try using Amazon’s “ Send to Kindle” service instead: this lets you send a file straight to their website, or install a program on your computer to send it for you.What to do about thisĪmazon offer no support at all for their Personal Documents service, so there is no way for us to report this bug to them. This is therefore a problem with Amazon’s systems. The identical document sent to Amazon at different times will sometimes work and sometimes fail.We have tried standard ePub verification software, and we have tried loading the document into Amazon’s own Kindle Previewer 3 program. All tests indicate that there is nothing wrong with the document that was sent.The "sent by you" time is never the time at which the document was sent, but always 1 hour 15 minutes after it. None of these reasons apply to the document that was sent. This message is followed by a list of reasons why a document might not be suitable. The following document, sent by you at 04:24 AM on Wed, GMT, could not be delivered to the address you specified: * Universalis-202252.epub There was a problem with the document(s) you sent to Kindle Sometimes nothing at all happens for precisely 1 hour 15 minutes and then Amazon send you the following email: Sometimes the system works and you get the e-book on your Kindle in about 20 minutes.They are using a different, industry standard format for the Personal Documents you send them (or we send them on your behalf).Kill the zombie processes (in the terminal or restarting your computer), and things should work now.As part of their continuing policy of customer experience improvement, Amazon have changed the way their Personal Documents service works. If you still run into issues it could be that a java process or a previous Kindle Previewer process is still running in the background and preventing the changes from taking effect. Then replace the two occurrences of java -d32 with $" .Main Go to Finder → Applications → Kindle Previewer.app, right click the file, Show package contents → Contents → MacOS → Launcher, right click the file, Open with → other, choose TextEdit or your favorite text editor.įirst add the following line below #!/bin/sh: export JAVA_HOME="/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home" The Launcher file is located in /Applications/Kindle Previewer.app/Contents/MacOS/Launcher. Open the Launcher shell script with a text editor Here is what worked for me, extracted from the Amazon forums.Ģ. There are a few resources online that pointed in the right direction but didn’t fully solve the problem for me. Fixing Amazon’s Kindle Previewer in El Capitanįor some reason getting Amazon’s Kindle Previewer to work on El Capitan is not an easy task.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |