Quote:
Originally Posted by Tex2002ans
That works, depending on the book. Or you can leave as is.
I think most people who read ebooks are used to it.
Similar situation with captions being split from the images. There's no way to reliably keep image+caption together (especially on very small devices like a cellphone + large fonts), so you just try to code them as best as you can.
I discussed more details in the Kindle Previewer 3.40 link that jhowell provided.
In HTML, you just had simple left/right floats. (Think: sidebar.)
In Print, you also have access to top/bottom floats. (Think: large figure+caption that attaches itself to the top of the next page.)
There is newer CSS3 "Paged Media" that has been introduced which tries to rectify this problem. Not much really supports it yet, but parts are slowly being implemented (and will most likely work in future ebook formats).
This is just good book design/writing. It's extremely common, but not the best idea to write:
Code:
The cows are brown, as seen here:
[Image of Figure 1]
It's better to say:
Code:
The cows are brown, as seen in Figure 1.
because Figure 1 might not be IN THAT EXACT SPOT. It might fit right below that sentence, but it's usually nearby on the opposite left/right page. |
Tex:
Have you given
any thought to fallback coding? For the snapblock use for ET? Or do we simply assume that the fallback is, as per usual, that the images and captions simply lay where they fall? No pun intended...
Hitch