Quote:
Originally Posted by RbnJrg
Exactly 
Kkeyboard supports .kf8/.azw3 so the only devices with .kf7 format are Kindle 1, Kindle 2 and Kindle DX but as Kindle 1 doesn't support tables, we can forget to write something for it. And as the DX model is more modern and with a better size, I'd prefer to write the code for it. But of course, is only my opinion and Klaus can do what he want. |
OMG, I really am getting old--I meant the original KK. LOL, which was KF7, of course, back in them thar olden days.
Quote:
Originally Posted by RbnJrg
Hmmm, I'm not sure. I don't remember well but with images inside a table things are different. In those cases I think the images could see partially. Maybe Hitch can give you a better answer, more accurate, because I really don't remember well how was the behaviour of an image inside a table cell when the width of the original picture was wider than the screen.
|
Ruben is right. Inside a table is a whole other kettle of fish. The K1 original doesn't support tables AT ALL; the K2 poorly. When you are inside a table on K2 and go to the next page, all the table formatting is 100% lost, and you have a jumbled mess.
I hate to say this, but I would strongly consider using hidden and mqs to deal with this. Stack your images in a vertical stack, for the KF7s. I mean...what you have now MIGHT work, for the images, for most, albeit not all, KF7 devices, but the captions--maybe.
Y'know...presumably, you've already coded it. Right? And you're testing it on KP 2.94? I've found that KP2.94 is reasonably accurate in DX mode for the KF7s. If you think it works there...then try it. It's quite a bit of work to change all your tables to hidden and rework everything (although, obviously, you can regex a lot of it), so if the 2.94 DX preview looks reasonably good to you...meh, it's probably safe enough. It won't work on the original Kindle or the K2 (reliably), but who knows how many of those are still in circulation?
Hitch