Quote:
Originally Posted by Jellby
Since it is so annoying (and probably common) a mistake in books out there, I guess the Kobo firmware is ignoring these absolute sizes, so the font size slider works as expected and fewer users complain.
|
I haven't tested the issue yet (I'll do it ASAP) but if it is true (and I don't see any obvious mistake in JSWolf's code) it's clearly
ANOTHER BUG no matter how you look at it.
I'm ORDERING the renderer to put whatever font in 18 points, inches or whatever. Period. It must follow that order. Period. I don't think epub/HTML/CSS spec says this is optional, you can do whatever you want.
Maybe in the 99% of the cases it is a publishing error... But I can think of some situations where it isn't (example: you have your text mixed with images and you want an exact size relationship).
If Kobo considers it is
usually a bug they want to filter out, what they should have done is adding somewhere an option about "ignore absolute font sizes" or something like that so the user has full control over the device behaviour. I accept even that option being ON by default...
It's the same with widows and orphans, page-breaks or @page. You cannot just ignore these settings because of whatever reason (even if you hate widows and orphans working...) while you say you are epub2/3 compatible...
[Joke mode]
What is the next decision? That if the user tries to open "Fifty shades of Grey" the eReader opens "Romeo and Juliet" instead because it considers that the first one is rubbish?
[/Joke mode]
Nevertheless I suppose this issue would be like what I posted
here about absolute measures being FUBAR in ACCESS while testing
Jellby's test book:
Quote:
|
cm absolute measure unit is FUBAR in both systems (at least in my H2O) but is much more FUBAR in ACCESS (5 cm rendered as 1.8 cm) than in RMSDK (5 cm rendered as 4.4 cm).
|