View Single Post
Old 02-08-2018, 04:56 PM   #99
sjfan
Addict
sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.sjfan ought to be getting tired of karma fortunes by now.
 
Posts: 281
Karma: 7724454
Join Date: Sep 2017
Location: Bethesda, MD, USA
Device: Kobo Aura H20, Kobo Clara HD
Quote:
Originally Posted by sherman View Post
Also note that a general use web browser like Firefox can not make any sort of assumptions about the content it handles. It must assume that a web developer will use floats everywhere, and they expect the browser to follow the CSS layout spec to the letter.

Therefore, implementing an algorithm like K&P, which may or may not be feasible to follow all the rules, would be opening up a huge can of worms that they probably don't want to deal with.

An ebook renderer I feel has a much narrower scope of the content it is expected to layout.
Yeah, hence my last observation in the first reply on the subject. You just need a way to detect whether there are problematic floats and degrade gracefully; that could be ugly or jarring on full-blown web pages, but for most epub purposes is probably sufficient.

Of course “just” doing that may be tricky in itself.
sjfan is offline   Reply With Quote