View Single Post
Old 02-02-2015, 07:11 PM   #9
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
Quote:
Originally Posted by JSWolf View Post
A 200px map is going to be unreadable on high resolution eInk screen. Especially if it's meant to be displayed full screen.

The problem is too many eBooks use images that are just too small. But what can be done about it? If you make the images high enough resolution, and you don't want them to be full screen, they'll be a bit too large on a non-high resolution eInk screen. What code can be used so it works on a regular Reader, a high resolutions screen, and an ultra-high resolution screen?
The latest CSS has tries to fix this problem by defining a CSS pixel (see our wiki page on CSS pixel.

A CSS pixel is defined as the size of a pixel on a 96 dpi screen (typical computer monitor). When CSS encounters an explicit px being used in a page it interprets the px not as an absolute vale but rather as a scaled value. Thus an image marked to be 96 pixels wide should be 1 inch wide on the screen. Older devices not not support this but is is coming in HTML5 and ePub3.

Dale

Last edited by DaleDe; 02-02-2015 at 07:14 PM.
DaleDe is offline   Reply With Quote