Quote:
Originally Posted by slowsmile
@jhowell...
I couldn't find the original link to the HDV definitions I used, but I did find the Amazon Kindle Publishing Guidelines, which has been updated for Enhanced Typsetting at this link. Refer to Image Guidelines - 9.4.2 Image Size and Quality Standards. There is a table that defines recommended percentage size to image size which is the one you want.
When I did an output comparison test between images(containing text) produced in a normal KPF file(images complied with HDV standard) versus an epub where the images were stored at their actual screen size in pixels(smaller images), the images and text in the KPF file were much sharper and less blurry than the smaller sized images used in the epub. You will also get the latter effect if you just use my AddKindleMediaQueries plugin in Sigil which was originally designed to dual format images for KF8 and mobi7 only(not KFX). |
But, William:
These are the same exact image sizes that they've been specifiying since...2017, if memory serves. They updated 9.4.2 in 2017.2, clarifying the "minimum quality standards for images in reflowable" books. At that time, they added the grid, and they used the divisions, full-page, 3/4, 1/2, 1/4 and "small." Right?
So...in two years, going on 3, these have been the same image-size standards, and so far, nobody's hair is on fire. That means that companies like mine have been blithely carrying on, toodling along, doing the SOSO coding--percentages for KF8, hard pixels for KF7, all this time and..
(I know I shouldn't say this, 'cuz, soon as I do...)
We've been using these images sizes, utterly coincidentally, for at least...4, going on 5 years. We have a handout for our customers, that we've been giving out forever, that tells them to make sure that they give us images that meet those same sizes--again, it's coincidental, in that it's not based on the Guidelines, but of course, we can all do the same math, in terms of, a 4" wide device x 300ppi = 1200 pixels, etc.
I guess why I'm struggling here is, didn't you
just say that if we use your plugin, we get the sharper and less blurry effect? Our coding at BNB is the same as what you do, effectively--separate MQs for KF8/7, hidden, yadda, with the pixel counts in one, the % in the other.
Did I misread what you wrote? Did you mistype? Does using your plugin address this and give us
SHARPER, or not?
I swear, I'm
not arguing. I'm trying to get some clarity here (YSWIDT?) on this topic. If using YOUR plugin, or similar coding, works, then...???
Is there some penalty, like, your book doesn't pass KFX HDV intake, or, that I'm not understanding? Does this affect KC, maybe, and not ePUBs, or...?
Is there anyone here (yoo-hoo,
Tex, you little madman maniac) that has time to make a test ePUB or two for this?
Hitch