Quote:
Originally Posted by roland1
Yes please. Coming from the web world and its ever-increasing code options, I just dove into this as though it was a website — and previews looked fine, so I just though —*meh, don't worry about it. Not so apparently.
So yeah, the more you guys can throw my way in terms of do's and don't's, the better it'll be for my ebooks, but also anyone searching for this kind of specific info (circa 2022).
|
I think the problem with REM is that it's relative, right? Based on the root font size--but this, this specific thing, rendering in the browser, means it's getting conflicting information--should it use the base font size of the browser's font settings, or the book?
The reason I think this is simple--I've seen Amazon's LITB affected by HTML coding that the author put into the DESCRIPTION field. The authors would put in italics, for example and NOT close the coding--so an opening italic tag and not a closing tag. The LookInside (LITB) rendered, sequentially, after the description--so the entire LookInside rendered in italics, until it encountered a closing tag.
For all we know, this environment is having the same issue and the rem tags are screwing with it. I don't use REM inside ebooks, anyway--and if you're going to ask me why, now, of course, I can't really remember. I seem to recall screwing with them years ago, when the Kindle Universe first came off of HTML 3.2 (in large part) and moved "up" to HTML 4.0, but I also vaguely recall that something went horribly wrong. I don't think it was the LITB, but damned if I can remember. Too many years.
Guys, Phillip, Dion,
anybody, remember why we're not all using REM? Or, hell, maybe I'm wrong?
Hitch