Pretty eBooks

Is there a way to make ebooks like this in scrivener? Not in columns, this is a just a two page view :slight_smile:

Right now I don’t even get the special font for the chapter title to show …


Adding an image, choosing a characteristic, colored font, Adding an Epigraph and using a Drop Cap are all possible in Scrivener. I wrote a whole Chapter about Chapter openings.
The magic is located at the Title Options tab in de Formatting pane of the Compile Format Designer you can conjure up Double-clicking a Format title in the Compile Overview window.
Use the Prefix and Suffix tab and the Title prefix and Title suffix areas to insert these docorative elements in your Chapter openings.

Have fun!

1 Like

You are talking to an idiot when it comes to scrivener :smiley: Prefix and Suffix - I only know this words when it comes to words … ‘un’ for example like in do and undo. The example I showed I made in CSS for another program.
I will manage, I am sure. Going to look for the mentioned Chapter about Chapters. But for now: I read somewhere, scrivener does not embed the fonts? So when putting the eBook into amazon, it will not work?

Well, there’s this process-step called post-compile, which helps you circumvent issues and bugs in the current version. With a little patience you may use the next update, hopefully these issues will be corrected.

Look for Sigil or Calibre. If you’re familiair with CSS, you will appreciatie these e-book editors. But these kind of Chapter openings are possible in Scrivener.

Inclusion of fonts works the same as on the web. You can supply a font, but remember e-book readers can always choose one build in their e-reader, and might even be upset if you change it for them. :wink:

And while there are other e-book editing tools that will embed fonts for you, Scrivener does not by L&L’s choice – font embedding can rapidly get into weird legal territory because of whether your license to use a given font includes the legal right to redistribute it. L&L errs on the the side of caution that prevents their users (and by extension the company) from becoming the targets of lawsuits by merely using L&L software. Users who want to do this have to knowingly take an active step to embed fonts, thus taking on the legal risk for themselves.

Calibre doesn’t produce good quality - sometimes the epubs won’t get validated when uploading them. So I would use Jutoh, if in need.

You mean fontface? But where do I put it?

How yould the producer of the software be made responsible? I do find that a bit strange …
And if you buy your fonts as one does there is no need for taking a risk.

combined with

doesn’t make sense: How could Calibre be responsible for the e-books you create? The creator is the one responsible for the quality of the output, not the software.

Calibre and Sigil are free. Just saying…

Hi AntoniDol,

Sorry for butting in. :innocent:

In the quoted text above, I believe Michou was reacting to Devinganger’s post, which stated that the Scrivener compiler doesn’t allow embedding of fonts in ebooks because L&L doesn’t want to assume any liability, direct or indirect, for font licensing. This is also my understanding, based on posts by L&L support staff. So Michou’s “responsibility” question was focused on the font licensing issue, not the quality issue.

At least that’s what I think is going on here. I’ll show myself out the door now. :sunglasses:


Adobe probably spends more on lawyers than L&L’s annual revenue. We don’t want to argue with Adobe’s lawyers about whether or not we are responsible for misuse of Adobe fonts by our users. If you want to embed fonts in your eBook, plenty of other tools will be happy to help you.

In the CSS, of course:

/* Fonts */
@font-face {
font-family: “Roboto Slab Regular”;
src: url(“…/Fonts/RobotoSlab-Regular.ttf”);

/* Default paragraph formatting */
p {
font-family: “Roboto Slab Regular”, sans-serif;

Many legal jurisdictions permit the filing of civil lawsuits in which the side with more money and lawyers can essentially wear down or bankrupt the other party after extended litigation, regardless of the actual legal merits of their case. By not giving the user any controls in which to embed a font, L&L sidesteps the whole issue of whether they are taking reasonable enough care to ensure that the user is embedding a font to which they have a proper license.

Users who wish to do so, and have the technical knowledge to do so, can easily do so with another tool that is more general purpose and thus can avoid the same type of legal attack – because the user very clearly has to take specific actions in which to violate font owners’ copyright and licensing.

1 Like

This is not quite the same thing being discussed. Embedding a font means literally including the font file(s) as part of the ebook archive so that the reading device has access to the font, not just saying “use this font if you have it already available.”

See Embedding Fonts in your eBooks – KWL Helpdesk ( for an example.

For this to work, you’ll have to copy actual font files into a Fonts folder in your e-book, of course. That would be the actual “embedding”. :slightly_smiling_face:

I was trying to answer the OP’s question:

I’m not a lawyer, so this question is probably stupid, but: What happens if the user embeds other unlicensed content? Say images. Or even text. :thinking:

1 Like

That is exactly what I meant :slight_smile:

1 Like

I am not a lawyer either, but that sort of content-related infringement is directly traceable to the user: any functional word processor will allow it. Likewise if you were to simply copy and paste the font files into your document (which wouldn’t work). But embedding fonts requires more active participation by the software.

1 Like

In theory someone could file a lawsuit over such a thing. In practice, it would be recognized as a frivolous lawsuit and that part would be thrown out of court. The reason why fonts have been treated differently is because they are licensed IP; you have to take a specific action Toni stall them and use them to begin with, and those uses are governed by a license agreement that dictates what the user can and cannot do with them. (Even many freely available fonts are licensed with a “no redistribution” clause.)

And, of course, there are companies who develop and sell fonts that have deep pockets and aggressive legal teams who have a history of filing lawsuits to protect their IP.

If someone wants to embed a font in a Scrivener-produced ebook, nothing is stopping them from cracking it open and making the necessary mods. But L&L has chosen to not put this functionality into the product and completely sidestep the possibility of getting dragged into a lawsuit.