[Trane]

Originally Posted by Tex2002ans

Yeah, my example code is pretty much what I settled on. My solution has to work across hundreds of books, not just one. I can then use the same exact code whether there is zero/one/three captions + multiple images + sentences/paragraphs of explanation! :P

Most of the time you will probably just have a single caption, so you could go with something very simplified [...] That initial example was out of one of the "harder" books. :P

Yes, very impressive!

Hey I thought you said you would never redo those images!

I wouldn't. That was one of the reasons I was considering print... to not have to mess with the images [by placing text in them]. I was just having a bad afternoon... I am very over this project and want it behind me, but am not the type to 'mess through the end' b/c of that. I was able to use Find/Replace to replace all the figcaption code with Turtle's code (I understood it easier ) and all the pics look great.

And that's the thing, sort of like with this page-break-avoid, we follow the standards and hope devices in the future get better (and they will). Let's say 10 years down the line, Reader XYZ will avoid breaking the page and fit the captions right below the image... and you will be glad you had the foresight to make it work. Long-term thinking is the best thinking!

Good point and I hope it's so, but it's at least as likely the current code methods for centering text under images will become legacy b/c there will be some new standard in 10yrs and the old code won't be honored anymore. But regardless, it's still better than embedding the text in the image. I was only resorting to that b/c nothing else was working for mobi (my project was coded with the figcaption method). Of course it REALLY helps to link the CSS to the Sigil file! If I had tested the methods in my working project I would have found they worked sooner. But I created a test epub and boo-boo'd.

Yeah, designing a book for print opened my eyes to a massive amount of little niggles that I never noticed before. Makes you see where ebook renderers still need a ton of advancements (like in Justification/Hyphenation/Microtypography).

Yeah, it always takes hardware time to catch up and become standardized, but I was surprised most by the fact there isn't existing, universal, standard e-book code for simple, basic things... like the subject of this thread and also floating images... which from what I understand mobi doesn't do. Hardware cannot become standardized until the code does. And Amazon threw a wrench in that cog in the very beginning by insisting on their own proprietary format, but they could still make it compatible with standard epub code... however, obviously they don't. (Reminds me of the browser wars of the late 90s.) Everybody wants to rule the world.. cue Tears For Fears!