[Hitch]

OK, gang:

As William seems very worried about the plugin, on a real device, I've tested it. The code seems to work fine--it outputs perfectly good KF7/KF8 coding. To be honest, I confess that I don't understand why you think, William, that the book on a real device would perform worse than on the emulator--I thought that the idea was that the emulator was performing worse than the real device--but I'm here to tell you that it's performing fine, on both, and the KF7 images look exactly as expected.

Here are two screenshots, from the test file (ePUB) that you sent me, which I then built into a MOBI, both on KP 2.94 and KP 3.13; the mobi results were identical, so no point in double-posting those. The KP 2.94 is named "Screenshot 2681.gif" and the "Test_Williams...yadda.jpg" is the emulator. The Fire device image is also the emulator, but I tested this on my matching Fire device, as well, and it's accurate.

I included the one on the "Fire" emulator, for comparative purposes. As you can see, they are WILDLY different, so the DX emulator on the KP 2.94 is NOT, remotely, showing images at the KF8 coding.

The DX emulator and the real K2 show the image exactly the same.

I used, built and tested Tex's test ePUB, and your test ePUB, Wiliam, both, and I have not seen any evidence, whatsoever, that the KF7 emulator is buggy, vis-a-vis image display for the correct coding.

The plugin seems to work a treat.

Hope this helps. If you are still seeing images, William, that look to you as though they are displaying KF8 size, when they should be showing KF8, you should send me THAT MOBI, or post it here for the gang, so that I/we can look at it, and see what you're seeing. Maybe we can figure out what's what if we both/all look at it.

Hitch