Starter template for a scientific book written in LaTeX with build-scripts for producing PDF, HTML, ePub, and Mobi eBook formats. A detailed description and walkthrough of these scripts can be found in this blog post: https://minireference.com/blog/generating-epub-from-latex/

Technologies uses:

• softcover the best build system for eBooks ever built
• TexSoup for parsing latex source into AST (used for source linting and formatting only)
• Fabric automation library in Python (think Makefile but written in Python)
• Docker for running processing on a remote machine (so my laptop doesn't melt)

# 1. install Ruby v2.6.3 so we don't have to use system-ruby
rvm install ruby-2.6.3
rvm use ruby-2.6.3

# 2. install softcover from source
git clone [email protected]:minireference/softcover.git
cd softcover
bundle install
bundle exec rake install

cd ..

# 2. install polytexnic from source (to overwrite the one installed in previous step)
git clone [email protected]:minireference/polytexnic.git
cd polytexnic
bundle install
bundle exec rake install

# make sure we're running the Ruby version that has softcover and polytexnic installed
rvm use ruby-2.6.3

softcover check   # check that all requirements are installed
sofcover build    # builds HTML, ePub, mobi, and PDF

Assuming docker installed on your machine you can built the image using:

docker build -t softcover-docker .

Then build html book from this project, by mounting the current directory under the /book directory inside the container:

docker run -v $PWD:/book softcover-docker sc build:html

To start the softcover live-updating server, run the command

docker run -v $PWD:/book -p 4000:4000 softcover-docker sc server

virtualenv -p python3.6 venv
source venv/bin/activate
pip install -r requirements.txt

Edit the constants at the top of fabfile.py to specify access credentials to a machine that has docker installed.

Build the docker image that contains softcover:

fab dbuildimage

Build the ePub format:

fab dbuild:epub

Before we can the softcover framework to build the ePub and mobi formats for our book, we must first extract the source code and perform some preprocessing steps to make sure the .tex source is in the format expected by Softcover.

You can automatically generate a draft book manifest file using the command:

fab extractmanifest:"/Users/ivan/Projects/Minireference/MATHPHYSbook/noBSguideMath.tex"

The book manifest config/manifest.yml format has the following structure:

---
sourcedir: "/Users/ivan/Projects/Minireference/MATHPHYSbook"
frontmatter:
  chapters:
    - title: Concept maps
      label: concept_maps
      sourcefiles:
        - "00_frontmatter/concept_map.tex"
    - title: Preface
      label: sec:preface
      sourcefiles:
        - 00.preface.tex
    - title: Introduction
      label: sec:introduction
      sourcefiles:
        - "00.introduction.tex"
mainmatter:
  chapters:
    - title: Numbers, variables, and equations
      label: chapter:equations
      sourcefiles:
        - 01_math/01.solving_equations.tex
        - 01_math/02.numbers.tex
        - ...
    - title: Algebra
      label: chapter:algebra
      sourcefiles:
        - 01_math/05.basic_rules_of_algebra.tex
        - 01_math/06.solving_quadratic_equations.tex
        - ...
backmatter:
includes:     # .tex files included in one of the sourcefiles
graphics:     # the contents of all includegraphics commands (prefer png)
  - figures/math/circle-centered-at-h-k.png
  - figures/math/polar/empty_coordinate_system_polar.png
  - ...

This manifest provides all the info needed to extract the relevant source files, transform them into softcover-compatible LaTeX markup, and load them into the chapters/ directory, where they will be picked up by the softcover build step.

All three these steps can be performed using:

fab extract transform load

    sample-book.tex
    chapters/
        preface.tex
        chapter_01__intro.tex
        chapter_02__mainstuff.tex
        chapter_03__conclusion.tex
    images/
        cover.jpg           # book cover to be used for ePub and mobi builds
        cover.pdf           # book cover to be used for the PDF build
        figures/
            someimg.png
            anotherimg.jpeg

You can assume the "build process" is happening in the root of the git repository so you can use relative paths to figures, e.g. images/figures/someimg.png and they will be resolved correctly.

• config/book.yml: book metadata
• config/lang.yml: i18n strings
• config/manifest.yml: detailed list of source files that make up the book (external repo)
• config/preamble.tex: this file is only used to get the latex documentclass declaration. The actual documentclass declaration used for build:pdf is whatever is in sample-book.tex.
• latex_styles/softcover.sty: main LaTeX header file that defines the LaTeX macros and styles and includes the other config files below.
• latex_styles/custom.sty : define additional macros, e.g. \newcommand{\unitvec}[1]{\ensuremath{\hat #1}}. These macros will be available in all build pipelines.
• latex_styles/custom_pdf.sty: same as the above but used only for LaTeX build pipeline

• html build directory for the HTML format.
  • html/images is a symlink to the images/ directory in the project root.
• epub build directory for the epub format
• ebooks output directory for .pdf, .epub, and .mobi formats
• 99anssol directory where exercises answers and solutions are collected to be printed in the Answers and Solutions appendix. Only relevant when \setboolean{SOLSINTHEBACK}{true}.
• log very detailed logging output you'll want to check when things break

• Exercise = easy question with numbering contiguous throughout chapter, e.g. E{chapter}.{ecounter}.
• Problem = harder end-of-chapter problem, labelled P{chapter}.{pcounter}.

• each exercise section starts an {exercises}{chNUM} where chNUM is some filename (e.g. ch2)
• each exercise environment contains
  • question text
  • one or more {hint} environments
  • an {eanswer} environment (optional)
  • an {esolution} environment (optional)

• each problems section starts an {problems}{CHNUM} where CHNUM is some filename (e.g. ch2)
• each problem environment contains
  • question text
  • one or more {hint} environments
  • an {answer} environment (optional)
  • an {solution} environment (optional)

• improve sanity checks at each step
  • one sourcefile cannot appear in two places (ERROR instead of warn?)
  • after load, cannot be includegraphics with .pdf paths
  • includes only once
• fix remaining issues to make sure ebook-check pass
• test adding optipng to build pipeline to see if .epub size reduced