View Single Post
Old 10-11-2023, 01:05 PM   #1705
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,376
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by kiwidude View Post
Therein lies the weakness in the simplistic approach of the ADE algorithm - inlined Base64 images result in enormous html file sizes which is what ADE calculates page estimates based on. And also why I don't use it personally myself - because unless you are in the habit of opening every file to inspect whether it has been edited this way (rather than external image files via links) you would never know if it is a genuinely big book or from this flaw in approach.
I've only found Base64 encoded images in 2 ePubs in the wild. For both, I converted them back to image files. In both cases, the issues became very noticeable just from the number of pages reported. The sample ePub I attached was generated during a discussion @davidfor and I had quite a while back about some claims that Base64 encoded images rendered faster though I did modify the posted file to leave only the Base64 encoded image pages.
DNSB is offline   Reply With Quote