[DNSB]

Originally Posted by Patricius

I've happened to read some books with some inline images (formulas, musical notations, special chars like āēīōū... etc, in jpg or bmp), and their sizes appear to be 'correct' on the calibre viewer.

However, when opened with the nickel viewer of my H2O, the images become tiny and unreadable in some cases. With the special chars I can regex it into corresponding ones, but not with formulas and musical notations. Is this a known problem? Is there a way to make it stretched like in calibre viewer? I'd be grateful if anyone comes up with some suggestions. Thanks!

p.s. I've tried the original epub and converted kepub, the image sizes look the same despite the super large font size with epub.

Very often, publishers specify the size of images in terms of pixels ( width: 355px;, height: 255px; ) or don't bother to specify any size which seems to default to the pixel size. A 600x800 image would fill the screen on a Kobo Touch but on the HD/H20 would fill about 60% of the screen width/height leaving a lot of blank space.

Specifying the dimensions in relative terms or using an SVG wrapper get around these issues. Replacing the width and height for example above with width: 59%;, height: auto; would have the image occupying the same amount of screen area on any device regardless of it's screen resolution.

The example used is from one ebook I recently read where all the image sizes were specified in pixels. The example I used was for the chapter title images was orignally:

.chaptitl {
    height: 225px;
    width: 355px
    }

which I changed to:

.chaptitl {
    height: auto;
    width: 59%;
    }

I calculate the percentages based on a 600x800 screen which seems to be the common value used by most publishers so 355/600 is ~59%. This looks a lot better than 355/1080 which used about 32% of the screen width when viewed on my Aura H2O.

As for the glyphs, my personal opinion is using bitmaps for glyphs should only be done when there is no other way to supply the glyph. Even embedding a subsetted font looks better and takes little extra effort. My personal preference is using either Charis SIL or Deja Vu which have decent glyph selections and look good on an eInk screen so I don't need to concern myself with whether macrons, breves, carons, etc. will or will not display.