Quote:
Originally Posted by Sarmat89
The problem is that it is unrealistic to expect various software vendors to support all the features of CSS (even the simplest features like text-transform are often missing). Because they are superfluous for 90% of books here, the CSS styling should add to the book format, not define it.
For that purpose, the format should be built on a semantic basis. The only kind of span we can allow is for xml:lang attribute, for the correct hyphenation.
|
If it is so unrealistic, why do all of them manage it?
And the most that can be said about the nonconformant ones, is that they override the CSS with breaking changes.
Few people actually write their own rendering engine. They almost invariably embed wekbit.
Amazon wrote their own rendering engine. Adobe wrote their own engine. Kobo wrote their own engine.
Pretty much all the independents (e-ink or app-based) just use webkit, or Adobe RMSDK.
Which is why apps tend to support this stuff.
I
do expect Amazon and Kobo and Adobe to get this right. They are big enough to put in the effort. And... guess what?
P.S. Please keep being evasive...