Using the same compile format to design for multiple mediums

Almost all of the built-ins would not be terribly relevant to eBooks, which is why we did not take the time to create CSS for them. For example, there would be little use in a “paperback” for ebook, or a double-spaced submission manuscript.

That said, I did not mean for my comment to suggest one should never try to create a format that works across different targets. If you are so inclined to do so, then have at it. You will probably want to keep a copy of a dummy project beside your main one though, so you can compare the stock Ebook settings when creating one from scratch.

In this case specifically, I recalled this being an issue and did some searching for it. Here is the original thread, with tips on how to correct the problem in formats created from scratch, or adapted from starting points other than “Ebook”.

To be clear the failure state here is unavoidable if you don’t set up styles correctly, but it should fail more gracefully than printing a double-title. That part is a known bug.