Backtracking a bit...since you're using D2D.
The original file MS Word doc/docx is likely the source of the "block_" type css formatting code. I test exported an epub from D2D and it didn't have any of this particular code in it (it has other basic css styling).
See comments here on "block_":
MR post
The D2D help info clarifies some other key points you are asking about
:
D2D help page
As per D2D website (this applies only to Word/doc/docx/odt importation into D2D):
Quote:
|
"Font Face and Family: Unfortunately, you can’t change either the font face or the font family. All ePubs generated by Draft2Digital will appear in the system default Serif font for any given device."
|
Per D2D website about imported pre-designed epubs:
Quote:
|
"ePub files will more or less stay ‘as is’, format-wise, but you can include our automated end matter if you choose."
|
Thus if you import an epub directly into D2D they will supposedly NOT change any of the CSS, you get an end result as you want (custom font-face). That would explain why you see other marketed ebooks on D2D keep their specialized font styling.
Several choices you'll want to make:
1. continue and finish building epub with D2D template / styling and anticipate it's sometimes odd variable end results and use it as is [not ideal].
2. revise/refine your doc/docx file styles further, then import again into D2D [still not ideal].
3. rebuild/redesign the epub in other software such as Calibre etc, then import it into D2D as an entirely pre-designed epub (set to your exact CSS code expectations + font choices). Note: basic epub creation in Calibre/Jutoh can be done without needing to know coding (though its certainly helpful).
So, there is no need to jump into the 'page-break-after' discussion while you are using the D2D software + template. Ideally, try epub creation via other software besides D2D.
Most persons at MR utilize some kind of controllable software (either freeware like Calibre, or paid software [like jutoh/etc] - to cut their epubs into a final quality state).