[eggheadbooks1]

The SVG wrapper I included was, as I said, from some years ago. And yes, 800x1200 is no longer the norm. The code was just by way of example of the SVG wrapper that Apple did not and, as far as I know, continues not to, read. Which is why I did not use it with this latest project.

SVG-wrapped images have never required the image to be in its own HTML file. I produced my image-heavy manuals between 2009 and 2012 using the SVG wrapper and the images were interspersed throughout the text. There is no need, or indeed desire, for images to have a page break before them in many cases.

The "height=90%" attribute caused the image to display at 90% of the screen. However, if 90% of the screen was larger than, in the above example, 1200 pixels, the SVG wrapper's max height and width attributes prevented small images from being resized in larger screens. Instead of displaying at 90%, the image would display at 1200 pixels, whatever percentage of the screen that was.

When the first-generation larger screens appeared but many people did not have images of sufficient size to accommodate these new larger screens, the SVG wrapper prevented unsightly uprezzing. The SVG wrapper also prevented image distortion on the new rotating screens, and thus became a staple of ebook coding.

However, the programming of latest-generation devices with regard to image handling has become in a sense the new DRM -- it's a way to force publishers to produce retailer-specific files and therefore force consumers into brand "loyalty."

Which is why we are stuck here with this stupid Apple problem and so far no solution.