View Single Post
Old 03-03-2017, 09:19 AM   #5
fbrzvnrnd
Fanatic
fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.
 
Posts: 559
Karma: 400004
Join Date: Feb 2009
Device: ONYX M96
Actually I do not use images > 150k. You can use images bigger than 150k, but I suggest to test the speed in rendering and memory usage of e-ink device, especially on older e-ink device. If a chapter has got many big images, it could be very slow to load and sometimes it can crash an ereader if it uses too much memory.

The SVG is a XML markup language to draw vectors. It is wonderful and full of things, like links, animation and "zoom". Some of this things are supported by e-reader, most not. You can also use it to "embed" bitmap, but it is only a thing you can do with it. Actually I use div and img to handle png or jpeg images in ePub2, not svg.

vh is viewport. 100vh is all the viewport. 50vh is 50% of viewport. what is viewport? is the web-page a user view. what is viewport in ebooks? well, it depends. I see testing with javascript that some ebook application thinks viewport is everything is inside the application window (the toc for example), other application only the page, other all the side-by-side pages. but, as Tex2002ans said, this is CSS3, so: no ePub2. Maybe EPUB3 (EPUB3 uses only a subset of CSS3).

f.
fbrzvnrnd is offline   Reply With Quote