page-break...:avoid / captions

[Oxford-eBooks]

Does anyone know anything new about the possibility of being able to use page-break-after:avoid on the Kindle? (Not the fire or touch).

I thought I'd give this a go again to havecaptions stay with images now that Amzon have 'fixed' the table problem where cells don't wrap across pages.

I thought for a moment that it was working, but seems not.
Are we doomed to never be able to keep captions with images without baking the text into the image?

[susan_cassidy]

.mobi does not support css attributes, only simple HTML.

ETA: some tools interpret some css into simple HTML for you.

[Oxford-eBooks]

Originally Posted by susan_cassidy

.mobi does not support css attributes, only simple HTML.

ETA: some tools interpret some css into simple HTML for you.

The Kindle guidelines say that

page-break-after:always;

should be used for page-breaks, so I was hoping that they'd taken the time to also suport

:..avoid

http://kindlegen.s3.amazonaws.com/Am...Guidelines.pdf

[DiapDealer]

The only way to always, 100% of the time, ensure that captions stay with their images is to make the caption part of the image.

Even if you could get all devices to support page-break-after: avoid ... the value is still "avoid"... not "never."

[susan_cassidy]

page-break-after:always; can be converted into a real page-break, avoid cannot.

[Oxford-eBooks]

Originally Posted by susan_cassidy

page-break-after:always; can be converted into a real page-break, avoid cannot.

Looks like that's true.

Both

<div style="page-break-before:always;"></div>

and

<mbp:pagebreak/>

have the same effect on the Kindle 3 device and on Kindle Previewer.
It looks like Kindle Previewer doesn't have the 3.5 update in it yet as the K3 previewer isn't showing embedded fonts. So I guess that kind of points to the CSS being intercepted and recoded as a <mbp:pagebreak/> because it even works on the DX previewer.

Anyhoo... back on topic, I'm just going to have to use fall-back methods to TRY to ensure that captions stay with the images.
I've got a nice robust method now that's working on all devices for the book I'm currently working on - it's got LOADS of images and captions.
The publisher didn't want baked-in captions as the font wouldn't match the body text. I was right to avoid that too because it looks like Amazon have updated the font in 3.5 and who knows what they'll do in the future.
Baked-in also kills the read-aloud (doesn't look like it reads the ALT or TITLE or CAPTION text either), and also no good for those that need a larger font due to sight problems.

[Oxford-eBooks]

... turning off smilies might have helped in that last post! lol.