View Single Post
Old 09-03-2010, 05:30 AM   #16
pdurrant
The Grand Mouse 高貴的老鼠
pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.
 
pdurrant's Avatar
 
Posts: 73,590
Karma: 315126578
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Oasis
Quote:
Originally Posted by pdurrant View Post
The only consistent font size option is to use <big> and <small> tag directly in the XHTML.
I have now found that one of the reasons I'm having such trouble with font size is that Amazon have messed up the Mobipocket rendering engine!

Kindlegen converts CSS font sizing into the <font> tag with the size attribute. It correctly converts things like percentages to relative sizes , e.g. +2. Unfortunately, the Kindle rendering engine incorrectly renders these relative sizes, always rendering them relative to the base font size chosen by the user, not the current font size of the text.

Mobipocket Reader does render them correctly.

Oh dear. And Kindle for Mac and Kindle for PC also render them 'correctly', just not the same as an actual Kindle! The Kindle Previewer does render them like a Kindle.

Bloody Amazon! It's impossible to make books in Kindle format that look right on Kindle for Mac and Kindle for Pc and on actual Kindles! I haven't had a chance yet to test Kindle for iPod/iPhone. I wonder which code base that was taken from. Bah!
pdurrant is offline   Reply With Quote