View Single Post
Old 07-24-2016, 05:10 PM   #6
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by 93terp View Post
In reading a 3 part article about various ways to send books to a Kindle (www.teleread.com), a reader posted a comment about the advantages of using Calibre's Save To Disk feature over using Send To Device. It seemed to make sense to me, and one of the main advantages noted is that using Save To Disk results in less space being taken up on the Kindle.
Says who, and why?

By default, Save-to-Disk performs the same metadata updates performed during Send-to-Device, and other than that, it is the same original file...

Why on earth would there be any difference between the two, except of course that Send-to-Device is device-aware and can select specific formats, use device-specific plugboards, optionally calculate Kindle APNX files, integrate with the Kobo database, etc.

If anything, Save-to-Disk requires more space, because by default it also saves the metadata.opf and cover.jpg (and creates extra folder inodes).
eschwartz is offline   Reply With Quote