Not exact matches
With the exception
of eBooks published in pdf format, all
eBooks are essentially specially
packaged files written in HTML, the HyperText Mark - up Language with which websites are made.
Your self - publishing
package includes the formatting
of the interior
of your book, design
of your book cover,
eBook conversion, and the submission
of your final book
files to your printer and
eBook distributor, such as IngramSpark, CreateSpace, and Amazon KDP.
Nick Moran
of The Millions had interesting prospective, mentioning «The emissions and e-waste for e-Readers could be stretched even further if I went down the resource rabbit hole to factor in: electricity needed at the Amazon and Apple data centers; communication infrastructure needed to transmit digital
files across vast distances; the incessant need to recharge or replace the batteries
of eReaders; the resources needed to recycle a digital device (compared to how easy it is to pulp or recycle a book); the
packaging and physical mailing
of digital devices; the need to replace a device when it breaks (instead
of replacing a book when it's lost); the fact that every reader
of eBooks requires his or her own eReading device (whereas print books can be loaned out as needed from a library); the fact that most digital devices are manufactured abroad and therefore transported across oceans.
For the print and
ebook package, we will supply you with
packaged InDesign
files of your book cover and interior, print - ready PDFs set up as per your printer's specs, and the ePub
files.
Hi Alice, My main reasons for doing it myself are: * You only pay 1 middleman i.e. Amazon — if you go through someone else you pay them as well as Amazon / other retailers * Ease
of updates and they are also free — some
of these
ebook publishers will charge you to update It's really easy to do your own
files now, use Scrivener or another
package.
The content.opf
file is the most important part
of the EPUB
package, because it defines the structure
of the
eBook and the metadata.
Current
ebook design presumes that all the contents
of a work are loaded into a single
file package, downloadable to a reading system that might be a smartphone, tablet, or dedicated e-reader.
Assume the industry successfully establishes an XHTML - based reflowable document format based on the evolution
of OEB, with an associated single -
file container
package with pluggable DRM, then I see no strong raison d'etre for Mobi, BBeB, or any
of the other OEB - derivative
eBook formats to hang around forever.