How to Produce an EbookProducing an Ebook
Making an e-Book, one by one
These tutorials will take you through the process of creating a standard ebook from scratch. If you are an expert manufacturer, it can only take an ebook design for review in one or two hours (depending on the ebook's level of detail, of course). See the README.md for installation directions for the few interdependencies that the utilities use.
To produce the best place to search for publisher is Project Gutenberg. Especially, there could be a better rendering that has fewer files to download because it was created later, or there could be a better HTML mark-up for it. The Gutenberg 20,000 mile under the sea is a good example of this phenomena.
Most of the downloads are an old German language that is widely criticised as flapdash and imprecise. This less populair one is a new, contemporary interpretation devoted to the general population. As a rule, Gutenberg provides both an HTML as well as an eBook edition. An occasional user might think that the HTML file is created from the epoxyBub file, or vice versa; but for some reasons the HTML and epoxy files often differ in important respects, where the HTML file usually uses less pointless CSV files and contains variables that the epoxy file is often not there.
Choose either the HTML or epoxy edition as the start point, but make sure you choose the one that seems to be the most precise. When you look for it on Gutenberg, you will find that there are two releases; the most favorite is a bad option to produce because the transcriptionist has the page numbers cmack in the center of the text!
Less trendy is a better option to produce because it is a cleanly transcribed. While you are producing your work, you will want to compare it with the real page-scan. Frequently, the scan contains formats that are lacking in the original transcript. Any of these resources allow you to sort the results by release date, so make sure you dial 1922 and sooner to make sure they are publicly available in the US.
When you can't find a scan of your textbook from the above mentioned resources and you use a Gutenberg transcript as your resource there is a good possibility that PGDP (Project Gutenberg's affiliate that does the real transcriptions) has a copy of the used scan in their archive.
A single expub is just a pile of data located in a certain directory tree, then all grouped. This means that it is as simple to edit an epoxy document as it is to edit a series of text documents within a specific directory tree and create a single copy of the archive from it. It is not possible to organize your data arbitrarily, although the epoxy default requires certain data in certain places.
So, if you have selected a work you want to produce, build the base epoxy framework in a working folder. Of course, you can give the create-draft utility the ebook project address, and it will try to get the ebook in ./src/epub/text/body. Here, you will find a set of meta data for you: XML and prefill:
Since Project Gutenberg e-books are created in different ways by different individuals, create-draft has to make some assumptions and it might advise wrongly. Well, now that we have the framework, we load Gutenberg's HTML for Jekyll directly into the text/folder and call it body.xhtml. Well, now that we have the code, we need to make some very extensive cleanups before we do our first commit:
Delete the headers and everything, incl. the Gutenberg text and the work titles, up to the beginning of the real publication. Delete rootline text and mark-up after the end of the part. When you used the --gutenberg-ebook-url checkbox with the create-draft utility, it may have already removed the licence for you and contained some Gutenberg meta data.
Now, our original files look something like this: Well, now that we've cleaned out all the garbage at the beginning and end of the files, we're good to go for our first commits. Use the following init log to ensure compatibility with the remainder of our ebooks: init -A init command-m "Initial commit" The download contains the whole work.
While Jekyll is a brief work, for longer works it quickly becomes inconvenient to have the whole text in one work. Next is to divide the files in logic places; this usually means with every up-wrap. In the case of works that contain their sections in large "parts", the parts subdivision should also be a separate one.
We use the splitter program to divide the work, Split-File will take a separate filename and break it into a new one every tim it hits the mark-up tags have the