#SEND TO KINDLE APP FREE#
And there's still no way to add an author name in the email process, so that's out for me.For over three years now, Amazon has offered Kindle users free cloud storage for their ebooks. Otherwise I'd not be bale to search anything by author on the website. But I guess I'll still have to add the author name manually, and only send one book at a time via Send to Kindle. I think another poster in another thread had also noticed this: correct on device, wrong in cloud. Result: correct author on the device, but the cloud still shows email address as the author. I also tried emailing a book to that same device. I then sent just a single book via Send to Kindle, with the author line blank: same result: correct on the device, wrong in the cloud. But the books appeared in the cloud (Manage Your Kindle Content page) incorrectly, still with my own name as the author of each book! All five downloaded to my Kindle Oasis with the correct author name - that's an improvement from last week.
#SEND TO KINDLE APP WINDOWS#
I used the Send to Kindle app on Windows and batch/bulk sent all five at once, leaving the "author" line blank. Tonight Oct 4 I tried uploading five books to my Amazon account. Now over a week later I'm seeing it partially fixed. I did report this to Amazon in detail via chat. So I doubt there is anything wrong with the metadata itself, given the various sources of the files." Some were already in DRM-free mobi format from other sources. Which means if you want the author to be correct on the Kindles and in the cloud storage, you can't use email at all because there's no way to add an author name other than via the metadata in the file itself, which the Kindle document service is not currently able to read. The author comes out on the device as the email address you used to send the files. The same is happening with sending personal docs or books via email. You'd need to send things one at a time and add the author name manually. "Of course, this means you can NEVER send multiple books anymore via "Send to Kindle" app because it won't pick up all the individual author names from the metadata. if you put the author in the author line, then it works correctly, and the author name shows up where it belongs on your devices. (and though the author name is included after the hyphen in the title line, only the title is transferred to the devices and the cloud - it doesn't show in the title itself, it's just ignored) However. BUT in the last few weeks, unless you put the author name in the actual "author" line of the app, the service uses MY OWN name as author, and my name is listed in the author column in the cloud and on all devices. The sending service reads the author from the title line. You can leave the actual author line blank. If you select a book and right click to use Send to Kindle on PC, in the Title line the author shows after the title, separated by a hyphen: "Book ABC - John Doe". "Whether using the Send to Kindle app or email, the service does not seem to be reading the author info from the metadata. Where that ends up, who knows? Perhaps others have noticed this issue? The chat person said she would file a report to tech on my behalf. The detailed message below to Amazon via "chat". I don't know how clear the following is, but I sent So if you want an author name, you cannot presently use email! But you can't add an author name at all if sending a file to your Kindle via email. So you can effectively only upload one book/doc at a time.
#SEND TO KINDLE APP SOFTWARE#
Whether using the "Send to Kindle" app or sending by email, the software doesn't retrieve the author name from the metadata as displayed in the filename and so the "author" shown in Kindle will only be your own name or your email address, not the book's real author! You can, of course, manually type in an author name in the "Send to Kindle" app (on computer or mobile device) for just a single book (but not for multiple/batch uploads). I checked myself and can confirm that everything is working as it should for me also. Several people reported the "fix" late in December.
As of about 3 months later this issue described below has been fixed.
0 kommentar(er)
