Quote:
Originally Posted by mattmc
I would say it certainly compares. My experience with a Kepub and their wack rendering engine is that it eviscerated my book. Normal page-break CSS doesn't even work: https://github.com/kobolabs/epub-spec/issues/18
To me, that's actually far worse than stripping out your embedded fonts. |
In terms of the user experience, yes, at least for now, but it is also a bug that they'll eventually fix, as opposed to modifying the content in a way that will make it be forever broken, which makes it less bad at least in the long term.
Incidentally, I find the spec linked from that page to be fascinating. What it tells me is that on iOS and Android, they used the native rendering engines (either WebKit or Blink, which is based on WebKit), but used something else on other platforms for some baffling reason. Whatever that "something else" is, it apparently isn't a fully functioning CSS layout engine. I'd imagine if I fed it my content on Windows in KePUB mode, it would keel over and die.
Or I could be wrong, and they might have used WebKit, but hacked together the pagination in some custom way rather than using it in paged media output mode like you'd use if you were printing. Hard to say which.