Quote:
Originally Posted by bookman156
Of course it uses it in the same way, it's just that ebooks don't support the range of HTML that websites do. In any case the question was why the mobileread wiki was using the html tag in its CSS. The question remains.
|
An ebook uses HTML and CSS. But it's not a webpage. Forget browsers and webpages and "HTML" tag in CSS.
Ebook renderers are closer to how a browser prints on paper, but not the same as that either. You can set say A6 or some custom paper size on your printer, and on a decent OS & Browser (not iOS or Android) select Print Preview (without background image printing) after page setup to select the new paper size. A lot of web page stuff simply doesn't work on paper or print preview. No Animation, video or sound. Automatic headers and footers not in the web page. No sensible use of transparency. Many tables might break on your small paper size. Images might no be the same size relative to text as on the screen web page.
It wouldn't be hard to make a browser with a "book" (i.e. codex) mode instead of infinite scroll, that behaved much like either Print Preview or an epub app were "paper size" is set by browser window size.
I'd love it. I hate websites with a forever giant scroll. So 2300 years old!
The Wiki is wrong.