View Single Post
Old 10-07-2024, 08:37 PM   #4
Fitz Frobozz
Occasional Curator
Fitz Frobozz began at the beginning.
 
Fitz Frobozz's Avatar
 
Posts: 36
Karma: 10
Join Date: May 2024
Device: Kindle Scribe, BOOX Tablet Go 10.3
Quote:
Originally Posted by Turtle91 View Post
Ditto Karellen.

Just a couple quick comments about your example code… no particular order or priority.

I’m sure it’s just a typo, but you need to close out the </figure> after your </figcaption>.

Your css isn’t letting it pagebreak anywhere. Since these are just suggestions to the render (avoid if possible) it will break out at some point but you aren’t giving it anywhere you prefer to breakout, so it’ll just go wherever.

Since you are using ePub3, you may be able to use some of the more advanced layout options available with display:flex if you want to use text with a small graphic, or just use svg wrapper for a full page image.
Oh, nice catches, Dion. I forgot to consider allowing breaks somewhere and have added a page-break-after: auto; to the figure element (whose figcaption is OK in my actual ePub but obviously not here in the example — glad you spotted that, though). Back to testing!

Quote:
Originally Posted by Karellen View Post
I will use either, and depends on how decorative the title page is in the pbook.
If the title page is basic, I'll use text. If the title page is using decorative fonts, maybe a border and fluerons, I'll scan it and use the image.
I then wrap the image in svg tags. I don't have any issues with the image overflowing, or a second page being forced, no matter how big the image is.
You make some good points here, Karellen. The more I think about this and the more I sit with my "placeholder" image-based pages — whose design has some features I'd have had a harder time implementing otherwise — the more I'm reconsidering how temporary that solution actually is now. Plus I'm starting to come up with some additional aesthetics that wouldn't be easy/possible otherwise.
Fitz Frobozz is offline   Reply With Quote