Quote:
Originally Posted by robertosaenz
Thank you for your answer, Quoth. About that, I have equations rendered as inline-block images, which I size to 1em in height, so they embed correctly in the paragraph.
|
It will fail when the reader (user) resizes the content as that only changes the font, as Hitch explained.
Images embedded in a line of text won't work. Text needs to be in prior and next paragraphs. Anchor images as character each in own paragraph, unless small, then several can be on one line.
Quote:
Originally Posted by robertosaenz
The original size of these images is a little larger than the size indicated in the style sheet. What would happen to those images in the conversion from epub to kindle (in the case of old devices)? Would they stay as still images in their original size?
|
Depends how you have defined them. The Kindle screens are 150 dpi (9.7″) or 167dpi (6″) for old devices. Later devices are 300 dpi for all size of screen. Absolute pixels and % behave differently. Before the Kindle Basic 2022 the Kindle 5 and Basic models (After Paperwhite) used the newer format but used a 6" 167 dpi screen. Later the KK3 and all later models except the DXG (really an upgraded DX that was before KK3) got FW updates to at least azw3. Much later models got also KFX.
If a Kindle has a Publisher option on Theme or Aa menu, then it can do azw3 (KF8, which is like epub2), otherwise it only does old mobi (KF7), the original 2007 Kindle format based on HTML3 with only inline styles and no separate CSS files or embedded fonts. KFX is more about delivery and encryption, maybe since PW2? It renders a bit differently to azw3 and different internals, but nothing that Amazon couldn't have updated azw3 to do as an option.
The eink isn't well suited for text books as the formats were designed for novels with some illustrations dropped in. Thus images never resize with resized text and are either absolute pixels or a % of width or height (never both, the other property must be set to auto).
Images embedded in text behave badly. Text flow with images is very non-portable code.
Hitch has great experience at this. I now avoid ebooks that need images like yours. Actual maths like LaTex or svg etc would be great but there is almost no support for it (especially none on Kindles).
So options are an App for iOS/Android/Fire or a fixed layout /PDF (almost no eink, needs 8″ or bigger screen).