View Single Post
Old 08-14-2025, 07:17 PM   #44
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,075
Karma: 147983159
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by RbnJrg View Post
Thus, and following your reasoning, it's also not legal to use any of the workarounds for ADE, because it doesn't comply with the epub2 specifications. Using a WebKit property is, if you will, a workaround, which doesn't cause any problems for e-readers that don't understand the property. Because of the way these engines paginate an .xhtml file (they turn the entire page into columns), there's no other way to handle page breaks other than using -webkit-column-break-whatever.
And she the WebKit code is ignored, whatever it is you are trying to do won't work.

What ADE workarounds are not compliant with ePub2?
JSWolf is offline   Reply With Quote