Quote:
Originally Posted by davidfor
I missed the word "size". It should have been "normalise the font size".
|
That makes sense.
Quote:
Originally Posted by davidfor
For the record, there is something out there that will build a book with body having a font size of something like 0.83333em, then wraps the text in a div with a font size of 1.2m, uses a paragraph for the heading setting that to 1.2, but wraps the actual text in two spans with different sizes. When I have multiplied it our, it usually works out to be about 1.6em for the headings. I simplify this rubbish but try to maintain the same relative sizes. So I think normalising is a reasonable word choice.
|
I've seen that kind of constructs often. The calibre book editor "live CSS" is quite handy to determine the resulting font size in those cases.
However, that will not aid against silly constructs. For example I recently encountered an ebook which had the following preamble:
Code:
<?xml version='1.0' encoding='utf-8'?>
<html xmlns="http://www.w3.org/1999/xhtml" lang="ca">
and then proceeded by prefixing every paragraph by:
Not to mention spanning <span> constructs
Oh well, this makes even some dry statistics ebook quite funny.